Table of Contents
    Get answers from the Community
    Join discussions

    In 2018, the average time between a vulnerability’s disclosure and its first exploit was 2.6 years. Today, that window is less than a day, while many remediation processes still operate on a monthly cycle.

    That is the central tension in Black Duck’s 2027 AI Readiness Report, which analyzes 65.5 million application security testing findings across roughly 13,100 applications at 533 organizations.

    The findings are stark: Discovery has accelerated, remediation has not kept pace, and the gap is widening.

    Here is what the data shows and why it matters for security teams preparing for 2027.

    Key findings

    • 18 findings were discovered for every 1 closed in May 2026 (peak of 22 to 1 in December 2025)
    • Critical and high severity findings were 16.8% of new findings in May 2026, up from 13.1% in June 2025
    • Only about 1 in 10 findings closed by the end of the study
    • The median time to close SAST and SCA findings was about 30 days

    Why the vulnerability remediation gap is widening: 18 findings found per 1 closed

    In June 2025, organizations discovered 11 new findings for every finding they closed. By May 2026, that ratio had risen to 18 to 1. It peaked at 22 to 1 in December 2025. In April 2026 alone, organizations added 10.4 million unresolved findings to their backlogs. By the end of the study, only about 1 in 10 findings had been closed.

    The backlog is not just growing, it is becoming more severe. Critical- and high-severity findings represented 16.8% of new findings in May 2026, the highest share of the year and up from 13.1% in June 2025.

    Why a 30-day time to remediate leaves you exposed

    At the median, findings identified through static application security testing (SAST) and software composition analysis (SCA) took about a month to close.

    When exploitation can follow disclosure in less than a day, month-long remediation cycles leave organizations exposed for too long.

    Does company size or scan frequency speed up vulnerability remediation?

    It would be reasonable to assume that larger organizations or those that scan more often would close findings faster. The data tells a more nuanced story.

    • The largest organizations, with more than 10,000 employees, closed findings in a median of 19 days.
    • The smallest organizations, with 100 or fewer employees, closed findings in a median of 17 days.
    • More frequent scanning improved remediation speed only to a point. At the highest frequency, 30 or more scans per month, median time to close increased to 41 days.

    Based on these stats, it’s clear the advantage did not come from headcount or scan volume alone.

    We don’t know the exact reason for the differences, but what we see from customers who are closing findings faster is an operating model that combines better tools, frequent scanning, multiple testing methods, and automation that enables them to act on findings without waiting for manual review.

    The cost of slow remediation: compliance, breach risk, and customer trust

    The widening gap isn’t just a technical problem. It’s a business risk with concrete consequences.

    • Regulatory exposure: Regulators increasingly expect timely remediation. PCI DSS 4.0.1, for example, requires critical security patches within one month of release.
    • Breach exposure: Discovery outpaced remediation by 18 to 1 in May 2026 and 22 to 1 at the December peak. Vulnerabilities sitting open for months are an open invitation.
    • Customer trust: A breach traced to a known, unpatched vulnerability won’t be seen as a purely technical failure. It raises questions about governance, prioritization, and operational discipline.

    How to close the gap: AI-assisted triage and agentic remediation

    The report’s recommendation is clear. To determine what to fix first, combine deterministic application security testing (AST) with AI-assisted triage that evaluates exploitability and business context. Then use agentic remediation to accelerate the path from findings to validated fixes.

    The Mythos Readiness Framework: 4 pillars of remediation readiness

    This approach aligns with the report’s Mythos Readiness Framework, which is built on four connected pillars.

    1. Visibility: Do you know what’s in your applications and components?
    2. Coverage: Are you testing comprehensively across your portfolio?
    3. Prioritization: Are you weighing exploitability and context in addition to criticality to decide what matters most?
    4. Remediation velocity: Can you fix what you find faster than attackers can exploit it?

    Readiness depends on turning findings into fixes faster than attackers can turn vulnerabilities into exploits.

    What’s in the full 2027 AI readiness report

    If you run an application security program, the report’s findings may confirm what you already see: Backlogs continue to grow, teams work harder, and the gap between discovery and remediation keeps widening.

    The question is not whether the gap exists. It is whether your tools and processes are built for a world in which exploitation can happen in minutes rather than months.

    Download the full 2027 AI Readiness Report to explore:

    • Monthly finding trends and severity breakdowns
    • Time-to-close percentiles by methodology, company size, revenue band, and scan frequency
    • The full Mythos Readiness Framework and guidance for applying it
    • Benchmarks from the 533 organizations in the study
    • Recommendations for implementing machine-speed defense into your remediation program

    The data is clear: The gap is real. The question is whether your organization closes it before attackers can exploit it.