T08 · Insecure Dependencies
- Location
requirements.txt:1- Finding
Excessive and Unverified Third-Party Dependency Set
- Content
View full analysis
- Remediation
View remediation
Security audit
Security checks for vulnerabilities and agentic risk
The skill content is a normal Sichuan food R&D guide, but it ships an unexplained large Python dependency file that does not fit a Markdown-only skill.
Review before installing. The instructional content appears benign, but do not run or install artifact/requirements.txt unless the publisher explains why these packages are needed, minimizes them, and provides a reviewed lock file with hashes. Food-safety and regulatory advice should also be checked against the user's actual jurisdiction and qualified professionals for production use.
requirements.txt:1Excessive and Unverified Third-Party Dependency Set
The requirements file pins Authlib to a version flagged with multiple severe advisories, including JWT/JWE verification and cryptographic oracle issues. In an agent stack that may rely on OAuth, tokens, or identity federation, this can enable authentication bypass, token forgery, or cryptographic attacks if the vulnerable code paths are used.
GitPython is pinned to a version with multiple critical advisories including command injection and unsafe option forwarding. In agent systems that may inspect repositories, load code, or interact with Git metadata, these flaws can permit arbitrary command execution or malicious repository-triggered behavior.
langchain-core has multiple critical advisories including SSRF, template injection, and incomplete prompt/template validation. Because this project appears to be an agent skill that likely processes untrusted prompts and URLs, these flaws are particularly dangerous and can lead to internal network access, prompt abuse, or arbitrary file/data exposure.
Click is pinned to a version reported as vulnerable to command injection. If this skill or its supporting tooling exposes CLI wrappers, passes untrusted input into Click-based commands, or uses administrative scripts in deployment pipelines, exploitation could lead to arbitrary command execution.
Cryptography 3.4.8 is very old and carries multiple advisories, including Bleichenbacher-style timing/oracle risks and bundled OpenSSL concerns. Because this stack includes OAuth, JWT, HTTPS, and agent integrations, weak cryptographic behavior can undermine confidentiality, integrity, and trust boundaries.
httplib2 is flagged for decompression bomb denial-of-service via unbounded compressed responses. If the skill fetches remote content, an attacker-controlled endpoint could exhaust memory or CPU and disrupt service availability.
The pinned idna version is reported vulnerable to specially crafted IDNA inputs. In a networked agent environment, malformed internationalized hostnames can lead to parsing inconsistencies, policy bypass, or destination validation errors in URL handling.
langchain-openai is pinned to a version with published high-severity advisories. Given its role at the boundary between untrusted prompts and model/tool execution, flaws here can amplify prompt-injection, request-routing, or data exposure risks in the agent runtime.
langgraph is reported vulnerable by published advisories and is central to orchestration/state management for agent workflows. Vulnerabilities in orchestration layers can expose checkpoints, alter control flow, or enable unsafe execution paths when handling attacker-controlled conversation state.
langgraph-checkpoint handles agent state persistence and is flagged with multiple high-severity advisories. In an agent system, checkpoint flaws can leak prior conversations, enable tampering with execution state, or permit deserialization/storage abuse.
langgraph-sdk is a client/control plane component with reported vulnerabilities. If used to interact with remote orchestration services, weaknesses here can compromise control channels, expose metadata, or allow unsafe request handling.
langsmith is flagged by several advisories and often handles tracing, telemetry, prompts, and run metadata. In an LLM agent environment, vulnerable observability components can leak sensitive prompts, secrets, or execution traces and may become an attack surface for data exfiltration.
oauthlib 3.2.0 has known high-severity advisories affecting OAuth handling. Since this dependency is directly tied to authorization flows, exploitation can lead to token leakage, improper redirect/validation behavior, or authentication bypass depending on usage.
orjson is pinned to a version with a published high-severity advisory. Serialization libraries sit on critical trust boundaries, and a flaw here may enable denial of service, parsing inconsistencies, or memory-safety issues depending on the advisory and usage.
Pygments is reported vulnerable by current advisories. If the service renders or highlights attacker-controlled content, parser bugs can trigger denial of service or content-processing issues in downstream interfaces.
PyJWT is pinned to a version associated with multiple advisories. JWT libraries are security-critical; flaws can permit signature bypass, weak algorithm acceptance, claim validation failures, or token confusion attacks in authentication and service-to-service trust.
pytest is normally a development dependency, but pinning a vulnerable version still poses risk in CI pipelines, test environments, or if dev dependencies are bundled into runtime images. Exploitation is less likely in production request paths, but it remains a real supply-chain and tooling issue.
python-apt is flagged with high-severity advisories and interacts with package-management functions. If present in privileged environments, vulnerabilities here may expose package metadata, trust decisions, or local privilege-related attack surface.
requests is a core HTTP client and the pinned version carries high-severity advisories. In an agent that may fetch URLs, call APIs, or process user-supplied endpoints, HTTP client flaws can enable SSRF bypasses, header/request smuggling issues, or certificate/redirect handling weaknesses.
setuptools is flagged by published advisories and is part of the build/install trust chain. Vulnerabilities here can affect package installation, build hooks, or dependency resolution, creating supply-chain exposure especially in CI/CD or dynamic package operations.
Starlette is the web framework layer for request parsing, routing, middleware, and response handling; the pinned version has multiple high-severity advisories. Vulnerabilities here can directly affect internet-facing attack surface through request smuggling, denial of service, auth/session issues, or middleware bypass.
urllib3 underpins HTTP transport for many clients and is pinned to a version with several advisories. Transport-layer bugs can undermine TLS handling, redirect behavior, connection pooling, or request parsing across a large portion of the stack.
Package name closely resembles a popular package, suggesting possible typosquatting. Attackers publish malicious packages with similar names to trick developers into installing them.
wheel is part of the packaging toolchain and is reported vulnerable by current advisories. While usually not directly exposed at runtime, vulnerable build tooling can still enable supply-chain compromise during packaging, CI, or deployment workflows.
zipp 1.0.0 is extremely old and carries advisories; ZIP/archive handling bugs often lead to path traversal, denial of service, or parsing issues. If any package, plugin, or artifact processing uses this library transitively, archive-based attacks may become possible.
No suspicious patterns detected.