Skip to main content
requirements.txt uses unpinned or wildcard versions enabling supply chain substitution

​
How to resolve

Pin all dependency versions with == in requirements files. Use a lock file to ensure reproducible builds. Run dependency scanning in CI.

​
Risk

Governance/Compliance This vulnerability falls under ASI04:2026 — Agentic Supply Chain Vulnerabilities in the OWASP Top 10 for Agentic Applications. Compromised runtime components — tools, plugins, MCP servers, deps — alter agent behavior. Security requirements.txt uses unpinned or wildcard versions enabling supply chain substitution. If exploited, this can compromise the agent’s integrity, confidentiality, or availability, potentially affecting downstream systems and data.

​
Explanation

requirements.txt uses unpinned or wildcard versions enabling supply chain substitution. This falls under ASI04 (Agentic Supply Chain Vulnerabilities): Compromised runtime components — tools, plugins, MCP servers, deps — alter agent behavior.

​
Specifications

Trigger
  • Agent scan detects requirements.txt uses unpinned or wildcard versions enabling supply chain substitution
The scanner looks for patterns such as:
  • = version constraint on AI framework package
  • ~= or * version in requirements
  • no version pin on crewai, langchain, openai, anthropic
Severity
  • HIGH
Applies to: Agent