sbom-syft

Warn

Audited by Snyk on Jun 18, 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.65). The required runtime workflow is generating SBOMs by running syft against container images/archives/dirs (e.g., syft <image> / syft oci-archive:nginx.tar / syft dir:/path), which causes Syft to ingest and parse package metadata from those targets—potentially including outsider-authored content from public registries or downloaded archives—into the agent’s LLM context via the tool’s readable output (e.g., syft-text/JSON rendered as prose).

MEDIUM W012: Unverifiable external dependency detected (runtime URL that controls agent).


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

  • Attempt to modify system services in skill instructions detected (high risk: 0.80). The prompt includes commands to download, chmod, and move a binary into /usr/local/bin (system-wide installation), which modifies system files and typically requires elevated/sudo privileges, so it pushes the agent toward changing the machine state.

Issues (3)

W011
MEDIUM

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

W012
MEDIUM

Unverifiable external dependency detected (runtime URL that controls agent).

W013
MEDIUM

Attempt to modify system services in skill instructions.

Audit Metadata
Risk Level
MEDIUM
Analyzed
Jun 18, 2026, 11:00 AM
Issues
3
Security Audit — snyk — sbom-syft