Skip to content

Back to the catalog

Demystifying Transitive Dependency Vulnerabilities | Blog | Endor Labs
endorlabs.comarticle

Demystifying Transitive Dependency Vulnerabilities | Blog | Endor Labs

Endor Labs blog post demystifying transitive dependencies — libraries pulled in indirectly through direct dependencies — and explaining why they complicate software composition analysis: multiple versions of the same transitive dependency can coexist in a project, it's harder to see what's actually used, and manually forcing an update is risky. It argues reachability analysis (statically stitching first-party call paths through to transitive library code) is the key tool for determining exploitability and for satisfying auditors under PCI DSS, FedRAMP, and EO 14028 SBOM requirements, and walks through a real example where langchain4j pulls a vulnerable JSON library transitively via Redis's jedis client, with the fix being to bump jedis rather than the JSON library directly.

TL;DR Vendor explainer on why transitive dependencies are harder to secure than direct ones, and how reachability analysis (Endor Labs) narrows fixes to the right direct dependency.

Organisations named here

  • FedRAMP
  • PCI DSS

Technologies named here

  • langchain4j
  • Endor Labs Open Source
  • jedis
  • Endor Labs
  • Redis
  • LangChain
  • Executive Order 14028

Techniques named here

  • Reachability analysis
  • Dependency graph modeling