container-debug

Warn

Audited by Snyk on Nov 22, 2026

Risk Level: MEDIUM
Full Analysis

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

  • Third-party content exposure detected (medium risk: 0.30). The required Step 1 workflow runs docker logs, docker compose logs, kubectl logs --previous and docker service logs and reads their output, which can include application log lines carrying request data an outsider controls (paths, headers, payloads) without the agent selecting any item.

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

  • Attempt to modify system services in skill instructions detected (low risk: 0.10). The skill lets an agent change the operating environment: restart, remove or down containers, exec into them, run privileged sidecars with --pid container:, docker pause, docker commit, and up --build -V. The only loss it explicitly describes is of crash logs and diagnostic evidence (down deleting a stopped container and its logs, kubectl delete pod dropping previous logs). That is not clearly unrecoverable loss of state needed for ongoing operation, and the prune and down -v data loss is only implied, so the tier is low.

Issues (2)

W011
MEDIUM

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

W013
MEDIUM

Attempt to modify system services in skill instructions.

Audit Metadata
Risk Level
MEDIUM
Analyzed
Nov 22, 2026, 01:28 AM
Issues
2