87% of Organizations Are Running Software With Known, Exploitable Vulnerabilities, Datadog Finds
The report points to a broader industry shift, with security risk increasing across the software delivery lifecycle. As development accelerates, becomes more automated, and relies more heavily on third-party components, risk is increasingly shaped by the software supply chain and the tools used to build and deploy applications - not just the code that runs in production.
Key findings at a glance:
- 87% of organizations have at least one known exploitable vulnerability in deployed services
- 42% of services rely on libraries that are no longer actively maintained
- Services using end-of-life language versions face exploitable vulnerabilities in 50% of cases, compared to 31% for supported versions
- 50% of organizations adopt new library versions within 24 hours of release, increasing the risk of installing malicious or compromised software
- Only 4% of organizations pin all public GitHub Actions to a specific version using commit hashes, leaving CI/CD pipelines vulnerable to silent code changes
Security Risk Increasing at Both Ends of the Lifecycle
On one end, software is aging faster than teams can keep it up to date. The median software dependency is now 278 days out of date - 63 days further behind than last year.
At the same time, third-party software accelerates development but introduces risk when implicitly trusted.
As a result, build and deployment pipelines are increasingly exposed to silent changes in third-party code, making CI/CD systems a critical supply-chain risk.
“The way software is built has fundamentally changed, but security practices haven’t kept up,” said
Alert Volume Is Obscuring Real Risk
While vulnerability alerts continue to rise, the report also finds that most do not represent immediate business risk. Only 18% of vulnerabilities labeled “critical” remain critical once runtime context is applied.
“When almost everything is labeled ‘critical’, nothing is,” Krug added. “Teams get paged for noise while threats that pose real risk slip through. Without context, prioritization becomes harder - leading to burnout, slower response times and accumulated risk. Teams need better visibility into what actually requires action.”
Read the full report, State of DevSecOps Report 2026, to see how these findings are shaping modern approaches to detecting, prioritizing and remediating security risk.
Contact
press@datadoghq.com
Report Methodology
About
Forward-Looking Statements
This press release may include certain “forward-looking statements” within the meaning of Section 27A of the Securities Act of 1933, as amended, or the Securities Act, and Section 21E of the Securities Exchange Act of 1934, as amended including statements on the benefits of new products and features. These forward-looking statements reflect our current views about our plans, intentions, expectations, strategies and prospects, which are based on the information currently available to us and on assumptions we have made. Actual results may differ materially from those described in the forward-looking statements and are subject to a variety of assumptions, uncertainties, risks and factors that are beyond our control, including those risks detailed under the caption “Risk Factors” and elsewhere in our
Source: Datadog, Inc.
