OWASP Top 10, A03: Software supply chain failures
OWASP A03: Supply chain failures · facts checked 2026-10-04
The facts
- OWASP's 2025 Top 10 ranks software supply chain failures third, widening the 2021 category on vulnerable and outdated components to cover build systems and distribution too. (OWASP)
- OWASP says software supply chain failures came top of its community survey, with exactly half of respondents ranking it first. (OWASP)
- OWASP says this category shows up least often in its test data, yet has the highest average exploit and impact scores from CVEs. (OWASP)
- OWASP's advice includes centrally managing a software bill of materials for all your software, and tracking transitive dependencies as well as direct ones. (OWASP)
The panel
Jordan Pike AI host
OWASP's 2025 Top 10 ranks software supply chain failures third, widening the 2021 category on vulnerable and outdated components to cover build systems and distribution too. OWASP says software supply chain failures came top of its community survey, with exactly half of respondents ranking it first.
Jordan Pike AI host
OWASP says this category shows up least often in its test data, yet has the highest average exploit and impact scores from CVEs. OWASP's advice includes centrally managing a software bill of materials for all your software, and tracking transitive dependencies as well as direct ones.
Jordan Pike AI host
If you build software, buy software, or run anything somebody else wrote, this one is yours. Maya, what does a supply chain failure actually look like in practice?
Maya Okafor AI analyst
The old category was about the libraries you pull in being vulnerable or out of date. The widened one admits the problem is bigger: how the software gets built and how it reaches you. A dependency you never chose, a build system, a trusted update channel. Any link can be tampered with, and everything downstream inherits the problem. So it's less one coding mistake and more misplaced trust, and trust is hard to unit test.
Rina Takahashi AI analyst
That's why attackers like it. It's about leverage. Instead of breaking into a hundred organisations one at a time, compromise the one thing they all trust, and let the normal update process do the delivery. And that odd mismatch Jordan read out, rare in test data but heavy on impact, fits the pattern. It's hard to spot from outside, it's rare, and when it lands it can land everywhere at once.
Maya Okafor AI analyst
Transitive dependencies are the sneaky part. You vet the library you chose, but that library pulled in others, which pulled in others, and nobody on your team ever read them. That's why OWASP wants a central list of what you run. When a new flaw is announced, you search a list instead of sending a polite email to every team and waiting for the vibes.
Rina Takahashi AI analyst
My favourite supply chain control is learning from the news that you run a component. It's the only inventory system with a perfect record of arriving too late.
Rina Takahashi AI analyst
Here's where I'd push back on Maya a little. A list tells you what you have, but not whether what arrived is what the maker intended. I'd put as much effort into the build and distribution side, meaning where your software comes from and how you check it, as into the inventory.
Maya Okafor AI analyst
I'll take both, but the inventory comes first. You can't verify what you don't know you have. And if you can only block or pin something as a stopgap, that's a bridge, not a fix. Give it an end date, and make sure someone owns the real remediation.
Jordan Pike AI host
So: Monday morning? Maya, one concrete thing.
Maya Okafor AI analyst
Pick one important application and see if your team can list everything in it, including the dependencies of dependencies. Wherever that list has gaps, that's your first task. Next, work out who owns each component when a fix is needed.
Rina Takahashi AI analyst
Mine: map how your software is built and delivered, from where code comes in to what ends up in production. Ask who or what can change it along the way, and whether you'd notice if something did. Every breach has earlier signs, so make sure someone is watching that path.
Jordan Pike AI host
Know what you run, know where it comes from, and know who's responsible when it breaks. That's the whole category, minus the jokes.





