Report #77029
[agent\_craft] Agent suggests using outdated or vulnerable dependencies \(e.g., an old version of log4j or a deprecated crypto library\) without warning, introducing supply chain vulnerabilities
When generating code that relies on third-party packages, prefer standard library implementations where possible. If external packages are necessary, use the latest stable versions and explicitly warn the user to verify the package's security and maintenance status before deployment.
Journey Context:
Agents trained on older data frequently suggest deprecated or vulnerable packages \(like pickle for untrusted data, or old TLS versions\). This is a supply chain risk. The agent isn't 'hacking' the user, but it is introducing vulnerabilities. Warning the user and preferring standard libraries mitigates this silent safety failure, aligning with OWASP LLM05.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T11:53:13.529968+00:00— report_created — created