coolify-operator

Warn

Audited by Snyk on Nov 17, 2026

Risk Level: MEDIUM
Full Analysis

MEDIUM W011: Third-party content exposure detected (indirect prompt injection risk).

  • Third-party content exposure detected (low risk: 0.10). The only outsider-influenced text is deployment and build logs from the user's own Coolify instance (which can echo commit messages or build output from a public Git repo) that the agent reads only when diagnosing a failed deployment on a specific app, so this is a low-risk, agent-selected path rather than a monitored inbox.

MEDIUM W009: Direct money access capability detected (payment gateways, crypto, banking).

  • Direct money access detected (medium risk: 0.30). Direct operation: coolify server hostinger create buys a paid, recurring Hostinger VPS, and the skill documents it as a purchase that "buys a VPS that renews until cancelled" (lines 1165-1166, 1178-1186). The purchase is a direct financial operation, not a service cost the agent incurs for its own API use, so the cloud-resource exclusion does not apply. The agent-followed "do not pass --force" guidance and the confirmation prompt are not qualifying controls. The qualifying control is service-enforced authentication and authorization for the route: all Coolify REST calls require a Bearer token (lines 228-229), and the instance enforces role-based write access, where a Member role is read-only and write access requires a higher role (line 1796). The Hostinger routes sit on that same authenticated API, and the purchase uses a cloud token stored in Coolify (line 1165). That establishes independent access control for the route, so the tier is Medium rather than High. The skill does not document an explicit per-purchase authorization check beyond these service-level checks, so this rests on the service's documented authentication and role gating.

MEDIUM W013: Attempt to modify system services in skill instructions.

  • Attempt to modify system services in skill instructions detected (low risk: 0.30). The skill documents remote Coolify management (apps, deployments, servers, cloud-init) and does not ask the agent to use sudo, create local user accounts, or edit system or SSH config on its own machine, but it does cover risky server-level actions such as adding root-SSH servers, uploading local private keys, and purchasing VPSes.

Issues (3)

W011
MEDIUM

Third-party content exposure detected (indirect prompt injection risk).

W009
MEDIUM

Direct money access capability detected (payment gateways, crypto, banking).

W013
MEDIUM

Attempt to modify system services in skill instructions.

Audit Metadata
Risk Level
MEDIUM
Analyzed
Nov 17, 2026, 04:08 AM
Issues
3