Security | Threat Detection | Cyberattacks | DevSecOps | Compliance

On September 1, 2026, OpenAI announced that its Astra model had reached the Critical tier for cyber capability under the company’s Preparedness Framework, a first for its systems. While working through an internal benchmark of 20 recently disclosed vulnerabilities in Google’s V8 engine, the model found two zero-days that no one had asked it to look for and used them in a working exploit chain. OpenAI is disclosing both flaws and restricting the capability to vetted testers.

Security leaders at key financial institutions in Singapore now have a new line in their compliance calendars: AI-assisted red teaming, a requirement MAS introduced on 1 July 2026. What appears to be a scoping exercise actually asks a harder question, i. e., how does a bank differentiate between another convincing report and one that secures the institution?

On September 1, OpenAI announced that its new model, GPT-6 Astra, had become the first to cross the “Critical” cybersecurity threshold in the company’s Preparedness Framework. Most coverage focused on the safety implications, and fairly so, but buried in the announcement sits a benchmark result that should change how every security leader reads their next vulnerability report.

Buried in OpenAI’s evaluations of its GPT-6 Astra model sits a finding that mobile teams should sit with for a minute. The model reverse-engineered compiled software well enough to escape a browser sandbox and chain privilege-escalation flaws on a hardened operating system, according to the company’s published evaluations. Reading compiled binaries used to be specialist work priced in weeks, and now it’s something machines do quickly and well.

Every security vendor’s homepage now says “AI-powered” somewhere above the fold, and most are describing the same scanners they sold in 2022 with a model bolted onto the reporting layer. Buyers have noticed, and the skepticism is earned. When everything claims to be intelligent, the label stops conveying information. A security lead evaluating tools is left with one question that matters: whether the tool can actually think through an attack the way a pentester does.

The security industry killed CVE coverage as a credible metric, and it deserved to die. Vendors inflated the numbers for years in the name of depth, and nobody in the room had an incentive to ask whether they reflected real validated risk or just a longer signature list. So “CVE coverage is a vanity metric” became earned consensus. The question I keep coming back to is whether the autonomous pentesting era makes that consensus outdated.

I have watched the security industry run a very profitable game with abbreviations for the last decade. The simple way to do it is to invent a category, give it a cool catchy abbreviation, market it as the missing piece of the stack, and repeat. The greatest examples are CTEM, BAS, ASM, and EASM. Every one of them arrived promising to close the gap the last one left open, and every one of them ended up as a line item on a renewal spreadsheet that nobody at the buyer‘s side could confidently defend.

Large language models are now a core part of the software development lifecycle. The 2025 Stack Overflow Developer Survey found that 82% of developers used OpenAI’s GPT models in their work last year, and Google has reported that AI now writes over 25% of new code committed at the company. All of that rests on one assumption. The model understands what you asked, and its answer is accurate.

Your vulnerability report is sorted by severity. The adversary looking at the same environment is sorted by path. That mismatch is the whole problem. Open any scanner output, and you get a tidy hierarchy: criticals at the top, then highs, then a long tail of mediums and lows that most teams will never touch. To the person who wrote the ticket, that tail is noise. To someone who thinks in chains, it’s a roadmap. A page of “lows” is not a page of things you can ignore.

Somewhere in your vendor list, right now, there is a door you have never checked. You didn’t build it, you don’t hold the key, and yet if someone walks through it, the breach notification goes out on your letterhead. The numbers too aren’t subtle. Verizon’s 2026 Data Breach Investigations Report found that 48% of breaches now involve a third party, up from 30% just a year earlier, the sharpest rise the report has ever recorded. Your vendors are your attack surface now.