[{"data":1,"prerenderedAt":27},["ShallowReactive",2],{"nr-en-ki-sicherheitsluecken-kaum-exploitiert":3},{"slug":4,"title":5,"dek":6,"date":7,"time":8,"publishedAt":9,"updated":10,"updatedAt":10,"dateFmt":11,"updatedFmt":10,"kind":12,"tier":13,"author":14,"authorName":15,"topics":16,"tracker":10,"trackerLabel":10,"headlineStat":21,"image":22,"ogImage":23,"imageAlt":5,"csv":10,"minutes":24,"words":25,"html":26},"ki-sicherheitsluecken-kaum-exploitiert","AI finds security flaws, but attackers barely care","A VulnCheck analysis shows that of over 1,000 vulnerabilities discovered by AI, only 1.3 percent are actually exploited—the same rate as conventionally reported bugs. But attacks are getting faster.","2026-08-02","12:24","2026-08-02T12:24:00+02:00","","August 2, 2026","daten","standard","ideal-syka","Ideal Syka",[17,18,19,20],"Cybersecurity","AI Security","Vulnerability Management","Threat Intelligence","Only 1.3% of AI-discovered security vulnerabilities are exploited","\u002Fnewsroom\u002Fimg\u002Fki-sicherheitsluecken-kaum-exploitiert.webp","\u002Fog-nr\u002Fki-sicherheitsluecken-kaum-exploitiert.en.png",2,499,"\u003Cp>The fear of AI-driven cyberattacks may be overblown. That's what a new analysis by security firm VulnCheck reveals for the first half of 2026: Of a total of \u003Cstrong>1,061 security vulnerabilities uncovered through AI-powered search, only 14 were actually targeted by attackers\u003C\u002Fstrong>—a rate of \u003Cstrong>1.3 percent\u003C\u002Fstrong>. This matches exactly the exploitation rate for conventionally reported flaws.\u003C\u002Fp>\n\u003Ch2>Key takeaways\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Cstrong>1,061 AI-discovered vulnerabilities\u003C\u002Fstrong> in H1 2026, \u003Cstrong>14 exploited\u003C\u002Fstrong> (1.3 %)\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Anthropic's Project Glasswing\u003C\u002Fstrong>: 23,000 findings led to only \u003Cstrong>1 confirmed attack\u003C\u002Fstrong>\u003C\u002Fli>\n\u003Cli>\u003Cstrong>Attack speed is accelerating\u003C\u002Fstrong>: From 120 to \u003Cstrong>80 days\u003C\u002Fstrong> between disclosure and first attack\u003C\u002Fli>\n\u003Cli>\u003Cstrong>New targets\u003C\u002Fstrong>: AI products themselves are emerging as attack surfaces\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Ch2>Much noise, little danger?\u003C\u002Fh2>\n\u003Cp>The sheer volume of AI findings says little about actual risk. That's the central insight from VulnCheck's analysis. While significantly more vulnerabilities are being reported than before, the actual exploitation rate remains stable. Particularly striking: Anthropic's \u003Cstrong>Project Glasswing\u003C\u002Fstrong>, an AI project for vulnerability hunting, generated over \u003Cstrong>23,000 findings\u003C\u002Fstrong>—but led to only \u003Cstrong>126 published entries and one confirmed attack\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cp>This doesn't mean AI-powered vulnerability search is ineffective. Rather, it means that raw numbers alone are not a measure of real threats. Many AI-discovered flaws may be difficult to exploit, already patched, or simply uninteresting to attackers.\u003C\u002Fp>\n\u003Ch2>Attackers are getting faster\u003C\u002Fh2>\n\u003Cp>Despite stable exploitation rates, another trend is intensifying: \u003Cstrong>The time between disclosure and first attack is shrinking significantly\u003C\u002Fstrong>. On average, it now takes \u003Cstrong>80 days instead of 120 days\u003C\u002Fstrong> as in the previous year. Roughly \u003Cstrong>200 vulnerabilities were exploited within a month\u003C\u002Fstrong>, and roughly \u003Cstrong>23 percent were targeted on the day of release or earlier\u003C\u002Fstrong>.\u003C\u002Fp>\n\u003Cdiv class=\"tbl-scroll\">\u003Ctable>\n\u003Cthead>\n\u003Ctr>\n\u003Cth>Metric\u003C\u002Fth>\n\u003Cth>2025\u003C\u002Fth>\n\u003Cth>2026\u003C\u002Fth>\n\u003C\u002Ftr>\n\u003C\u002Fthead>\n\u003Ctbody>\u003Ctr>\n\u003Ctd>Median days to attack\u003C\u002Ftd>\n\u003Ctd>120\u003C\u002Ftd>\n\u003Ctd>80\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Attacked on release day\u003C\u002Ftd>\n\u003Ctd>–\u003C\u002Ftd>\n\u003Ctd>roughly 23 %\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003Ctr>\n\u003Ctd>Attacked within first month\u003C\u002Ftd>\n\u003Ctd>–\u003C\u002Ftd>\n\u003Ctd>~200 cases\u003C\u002Ftd>\n\u003C\u002Ftr>\n\u003C\u002Ftbody>\u003C\u002Ftable>\u003C\u002Fdiv>\n\u003Cp>This is the real alarm bell: not the volume of findings, but the speed of exploitation is increasing. Security teams have less time to respond.\u003C\u002Fp>\n\u003Ch2>Content management systems in the crosshairs\u003C\u002Fh2>\n\u003Cp>Most frequently affected are \u003Cstrong>content management systems for websites\u003C\u002Fstrong>—they account for roughly \u003Cstrong>one-third of all cases\u003C\u002Fstrong>. This is a classic target because such systems are often publicly accessible and provide access to valuable data.\u003C\u002Fp>\n\u003Cp>As a new attack surface, VulnCheck analyst Patrick Garrity identifies \u003Cstrong>AI products themselves\u003C\u002Fstrong>: tools for model building and agent interfaces are becoming targets. That makes sense—controlling AI systems potentially means controlling their outputs.\u003C\u002Fp>\n\u003Ch2>What this means for you\u003C\u002Fh2>\n\u003Cp>For organizations, the takeaway is nuanced: the sheer number of AI-discovered vulnerabilities shouldn't trigger panic. At the same time, shrinking response times are a genuine problem. Patch management needs to accelerate—not because there are more flaws, but because attackers are moving faster. If you deploy AI systems, you should also keep their own security in focus: they've become targets themselves.\u003C\u002Fp>\n\u003Ch2>Sources\u003C\u002Fh2>\n\u003Cul>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fthe-decoder.de\u002Fki-gefundene-sicherheitsluecken-werden-kaum-angegriffen-vulncheck\u002F\">The Decoder (DE)\u003C\u002Fa>\u003C\u002Fli>\n\u003Cli>\u003Ca href=\"https:\u002F\u002Fthe-decoder.com\u002Fai-finds-plenty-of-security-flaws-but-almost-none-of-them-get-exploited\u002F\">The Decoder\u003C\u002Fa>\u003C\u002Fli>\n\u003C\u002Ful>\n\u003Cp>\u003Cem>Editorially owned by \u003Ca href=\"\u002Fen\u002Fautor\u002Fideal-syka\">Ideal Syka\u003C\u002Fa>. Sources and method: \u003Ca href=\"\u002Fen\u002Fredaktion\">Newsroom & method\u003C\u002Fa>. Tips and corrections: \u003Ca href=\"mailto:ai@i6eal.de\">ai@i6eal.de\u003C\u002Fa>.\u003C\u002Fem>\u003C\u002Fp>\n",1785666620702]