Cobalt Report: Trust in AI Vulnerability Scanning Plummets to 9%

The 2026 Cobalt State of Pentesting Report has revealed a dramatic collapse in enterprise confidence regarding fully automated AI vulnerability scanning, with trust dropping from 29 percent in 2025 down to just 9 percent this year.

This steep decline is primarily driven by a high volume of false negatives. According to the report, 78 percent of cybersecurity professionals surveyed indicated that fully automated AI testing tools had missed critical vulnerabilities, exposing their organizations to unacceptable levels of risk.

01What happened

Start from exposure, not from the headline. What software, cloud service, or configuration is actually in the blast radius of Cobalt Report: Trust in AI Vulnerability Scanning Plummets to 9%?

Write that list down before you open a war room. Most wasted hours on stories like this are spent debating severity before anyone knows whether they run the thing.

The 2026 Cobalt State of Pentesting Report has revealed a dramatic collapse in enterprise confidence regarding fully automated AI vulnerability scanning,… This steep decline is primarily driven by a high volume of false negatives.

02Who is exposed

Anyone running the affected component in production, CI, or a laptop fleet is in scope until proven otherwise. Inventory first. Include forgotten staging clusters and contractor laptops — those are where 'we don't run that' turns out to be false.

According to the report, 78 percent of cybersecurity professionals surveyed indicated that fully automated AI testing tools had missed critical vulnerabilities, exposing their organizations to unacceptable levels of risk. What software, cloud service, or configuration is actually in the blast radius of Cobalt Report: Trust in AI Vulnerability Scanning Plummets to 9%?

03What to do now

Patch, rotate credentials, and confirm the vendor's fixed version from their advisory — not from a social recap. If you cannot patch today, isolate the service and raise the logging floor. Record the decision and the residual risk so the next person does not re-litigate it.

Most wasted hours on stories like this are spent debating severity before anyone knows whether they run the thing. Anyone running the affected component in production, CI, or a laptop fleet is in scope until proven otherwise.

04How the issue works

Most incidents in this class are either an input-handling bug or a trust-boundary miss. Reconstruct the path with the advisory's affected-versions list in hand. If you cannot explain the path in three sentences, you do not understand it well enough to declare yourself safe.

Include forgotten staging clusters and contractor laptops — those are where 'we don't run that' turns out to be false. Patch, rotate credentials, and confirm the vendor's fixed version from their advisory — not from a social recap.

05What is still unknown

What is still unknown is as important as what shipped. Track whether exploitation is confirmed, whether a CVE is assigned, and whether your WAF or EDR signatures have caught up. Revisit the ticket when any of those three flip.

If you cannot patch today, isolate the service and raise the logging floor. Record the decision and the residual risk so the next person does not re-litigate it.

A 3–5 minute news post is a briefing, not a runbook. Keep Tech Bytes and the vendor's primary page in another tab, quote only what they printed, and write down the single decision this story forces (upgrade, wait, or ignore) before you Slack it to the rest of the team. If you need more than that decision, you want the primary docs or a later engineering deep-dive — not another recap of Cobalt Report: Trust in AI Vulnerability Scanning Plummets to 9%.

If you cannot name the surface — API, policy, model, hardware, or commercial terms — you are not ready to brief. Go back to Tech Bytes and the vendor page until you can. That extra ten minutes is cheaper than a wrong upgrade or a missed exposure.

If you cannot name the surface — API, policy, model, hardware, or commercial terms — you are not ready to brief. Go back to Tech Bytes and the vendor page until you can. That extra ten minutes is cheaper than a wrong upgrade or a missed exposure.