OWASP Top 10 Risks for Open Source | Endor Labs
OWASP Top 10 Risks for Open Source
The station 9 research team teamed up with over 20 CISOs and CTOs to identify the top 10 security and operational risks introduced through reliance on open source code.
Written by
Henrik Plate
Published on
March 1, 2023
Updated on
April 29, 2026
OSS Top 10 Risks
| Risk | Description | Category |
|---|---|---|
| OSS-RISK-1 Known Vulnerabilities | A component version may contain vulnerable code, accidentally introduced by its developers. Vulnerability details are publicly disclosed, e.g, through a CVE. Exploits and patches may or may not be available. | Security |
| OSS-RISK-2 Compromise of Legitimate Package | Attackers may compromise resources that are part of an existing legitimate project or of the distribution infrastructure in order to inject malicious code into a component, e.g., through hijacking the accounts of legitimate project maintainers or exploiting vulnerabilities in package repositories. | Security |
| OSS-RISK-3 Name Confusion Attacks | Attackers may create components whose names resemble names of legitimate open-source or system components (typo-squatting), suggest trustworthy authors (brand-jacking) or play with common naming patterns in different languages or ecosystems (combo-squatting). | Security |
| OSS-RISK-4 Unmaintained Software | A component or component version may not be actively developed any more, thus, patches for functional and non-functional bugs may not be provided in a timely fashion (or not at all) by the original open source project | Ops |
| OSS-RISK-5 Outdated Software | A project may use an old, outdated version of the component (though newer versions exist). | Ops |
| OSS-RISK-6 Untracked Dependencies | Project developers may not be aware of a dependency on a component at all, e.g., because it is not part of an upstream component's SBOM, because SCA tools are not run or do not detect it, or because the dependency is not established using a package manager. | Security, Ops |
| OSS-RISK-7 License Risk | A component or project may not have a license at all, or one that is incompatible with the intended use or whose requirements are not or cannot be met. | Ops |
| OSS-RISK-8 Immature Software | An open source project may not apply development best-practices, e.g., not use a standard versioning scheme, have no regression test suite, review guidelines or documentation. As a result, a component may not work reliably or securely. | Ops |
| OSS-RISK-9 Unapproved Change (Mutable) | A component may change without developers being able to notice, review or approve such changes, e.g., because the download link points to an unversioned resource, because a versioned resource has been modified or tampered with or due to an insecure data transfer. | Security, Ops |
| OSS-RISK-10 Under/over-sized Dependency | A component may provide very little functionality (e.g. npm micro packages) or a lot of functionality (of which only a fraction may be used). | Security, Ops |
Risk Overview
Every single open source dependency of a software development project has plenty of properties - both the component (i.e. the code or binary artifact downloaded) and the corresponding open source project with all its stakeholders (e.g., contributors, maintainers) and systems (e.g., source code management, build systems).
The list above provides an overview of 10 problematic properties, which can result in significant security or operational risks for downstream consumers. Security risks can result in the compromise of system or data confidentiality, integrity or availability. Operational risks can endanger software reliability on the one hand, but can also increase the efforts and investments required to develop, maintain or operate a software solution.
Read the full report to better understand how each risk works, and can be mitigated.
What's next?
When you're ready to take the next step in securing your software supply chain, here are 3 ways Endor Labs can help:
- Explore the Secure Code Prompt Library - Download 40+ AI prompts for secure vibe coding.
- Take a tour of Endor Labs - Explore Endor Labs with a self-guided platform tour.
- Book a Demo - See Endor Labs in action with a custom walkthrough.