← CRA Glossary
Software Supply Chain

Transitive Dependency

A transitive dependency is a software component that a product depends on indirectly - through another component that directly depends on it. Transitive dependencies are often numerous, poorly monitored, and the source of critical vulnerabilities in CRA-covered products.

A transitive dependency is a software component that a product depends on indirectly - through another component that directly depends on it. Transitive dependencies are often numerous, poorly monitored, and the source of critical vulnerabilities in CRA-covered products.

Software Supply Chain

Last updated 27 August 2026

What Is a Transitive Dependency?

A transitive dependency is a component that your product depends on indirectly. If your product directly uses Library A, and Library A internally uses Library B, then Library B is a transitive dependency of your product. In modern software development, the ratio of transitive to direct dependencies is typically very high - an application with 50 direct dependencies may have 500 or more transitive dependencies when the full dependency graph is resolved. Transitive dependencies are the source of a significant proportion of exploited vulnerabilities in real-world attacks: the Log4Shell vulnerability (CVE-2021-44228) was a transitive dependency for many organisations - they had no direct dependency on Log4j but relied on libraries that did. Many security teams have no visibility into transitive dependencies without dedicated tooling.

CRA reference:Annex I, Annex VII

CRA Obligations and Transitive Dependencies

The CRA's essential requirements apply to the product as a whole - including vulnerabilities in transitive dependencies. Annex I requires manufacturers to identify and address security risks in their products, which necessarily includes risk from transitive components. floors the SBOM at the top-level dependencies, so a 'direct dependencies only' SBOM meets the stated minimum. It also misses the large majority of the software attack surface, which is why deeper coverage is the practical choice. Capturing the full component inventory is what makes an SBOM useful for vulnerability management. SBOM generation tools (Syft, CycloneDX plugins, SPDX generators) are configured by default to capture the full dependency graph including transitive dependencies.

CRA reference:Annex I, Annex VII

Managing Transitive Dependency Vulnerabilities

Transitive dependency vulnerabilities present unique management challenges:

  • Indirect control: The manufacturer cannot directly update a transitive dependency - they must update a direct dependency to a version that uses an updated transitive version.
  • Dependency lock conflicts: Updating a direct dependency to pull in a fixed transitive version may break other direct dependencies that require an incompatible version.
  • Vendor-managed components: When a transitive dependency is embedded in a commercial SDK or firmware component from a third-party vendor, the manufacturer must wait for the vendor to release an updated version.

Effective management requires: a complete SBOM including all transitive dependencies; automated CVE correlation against the full SBOM; a process for assessing whether a vulnerable transitive dependency is reachable in the product's specific execution paths; and vendor notification procedures for transitive vulnerabilities embedded in third-party components.

CRA reference:Annex I

VEX and Reachability Analysis for Transitive Dependencies

A powerful tool for managing transitive dependency vulnerability noise is reachability analysis combined with VEX documentation. For many transitive dependency CVEs, the vulnerable code path is not invoked in the product's actual execution - the product uses a component that depends on Library B, but the product's use case does not call the specific function in Library B that contains the vulnerability. Static analysis tools (including some SCA platforms) can assess reachability by analysing the call graph. When analysis confirms a transitive vulnerability is not reachable, the manufacturer should document this as a VEX 'not-affected' assertion. This: reduces internal triage burden; informs users that they do not need to treat the vulnerability as urgent; and demonstrates to MSAs that vulnerability monitoring is active and findings are genuinely assessed, not ignored.

Work through the CRA for each product in one workspace.

Classify each product, build the Annex VII technical file and prepare Article 14 notifications. The disclosure portal that receives vulnerability reports stays free.

Frequently asked

Does the CRA SBOM requirement cover transitive dependencies?+

floors the SBOM at the very least the top-level dependencies of the product, and the CRA does not use the term 'transitive dependency'. A top-level SBOM therefore meets the stated minimum, and deeper coverage stays permitted. Full component graph coverage is the practical choice, because the vulnerability monitoring Annex I Part II requires works better when the SBOM reaches the components carrying most of the risk. All standard SBOM generation tools capture transitive dependencies by default, so check that your tooling has not been configured to suppress transitive entries.

How many transitive dependencies does a typical IoT product have?+

The number varies enormously by technology stack and application complexity. A simple embedded C application may have very few transitive dependencies. A firmware image based on embedded Linux with a Node.js application layer could have thousands - Node.js application ecosystems are particularly known for deep transitive dependency graphs. A container-based application may have hundreds of OS-level packages plus application transitive dependencies. Manufacturers are often surprised when their first SBOM reveals their true component count.

If a vendor won't update a transitive dependency in their SDK, what should a manufacturer do?+

When a third-party SDK or component includes a vulnerable transitive dependency that the vendor has not updated, the manufacturer should: formally notify the vendor of the vulnerability and request an updated release; document this notification and the vendor's response for the Annex VII technical file; assess whether the vulnerable code path is reachable in the product's use of the SDK and document this analysis; publish a security advisory informing users of the vulnerability status and available mitigations if the vulnerability is assessed as posing real risk; and consider replacing the vendor component if no update is forthcoming within a reasonable period.

Sector checklists covering Transitive Dependency

Consumer Routers & ModemsConsumer routers and modems are high-value targets for attackers and face specific CRA requirements around default credentials, remote management security, and firmware update integrity. Routers, internet modems, switches and wireless access points are Important Class I (Annex III, point 12), for home, industrial and critical infrastructure markets alike. No CRA harmonised standard is cited yet, so today a router needs a notified body for conformity assessment (Article 32(2)).Enterprise Networking EquipmentEnterprise networking equipment - switches, firewalls, load balancers, and network management systems - spans multiple Annex III classifications. Firewalls in hardware or software form and intrusion detection and prevention systems are Important Class II. Switches, routers, wireless access points, network management systems and SIEM systems are Important Class I. A load balancer is default class unless its core functionality is a listed category, such as a web application firewall. Class II products always need third-party conformity assessment (Article 32(3)). Class I products need a notified body today, because no CRA harmonised standard is cited yet (Article 32(2)).Embedded Linux DevicesEmbedded Linux devices span a vast range - from network gateways and industrial HMIs to set-top boxes and smart displays. All are products with digital elements subject to the CRA. The open-source nature of Linux creates specific obligations around SBOM completeness and CVE monitoring. The class follows the core functionality of each device (Article 7(1)). An industrial HMI is default class. A network gateway whose core functionality is a router is Important Class I (Annex III, point 12). Industrial or infrastructure use does not change the class.

This definition is part of the EU Cyber Resilience Act guide, which explains Regulation (EU) 2024/2847 article by article.

Browse the full CRA Compliance Checklist

See how Transitive Dependency fits into your complete CRA compliance programme.

View checklists →