The vulnerability tsunami is a forecast from Jason D. Clinton, Deputy Chief Information Security Officer at Anthropic, that AI-driven bug discovery will produce more critical software flaws than defenders can patch for about 18 months. For PR teams, October 2026 supplied the first test: the PHP, eMudhra, Railway and Node.js incidents showed that companies now explain security events within hours, in public, often about software they did not write.
Last updated: November 19, 2026
- Who Jason Clinton is and what he predicted
- How October's incidents played out publicly
- Which communications teams are most exposed
- What a first statement should contain
- How breach disclosure standards have moved
- What to watch through 2028
- Frequently asked questions
Who is Jason Clinton and what did he predict?
Jason D. Clinton is Anthropic's Deputy Chief Information Security Officer, who predicted in August 2026 that AI bug discovery would create an 18-month surge of critical software vulnerabilities that defenders cannot patch in time. His view matters because Anthropic builds the frontier AI models that discover software flaws faster than maintainers can fix them. On Oct. 22, 2026, Clinton posted on X that things would get a lot worse before they get better, as OfficeChai reported.
The timeline below shows how the warning, the evidence and the incidents line up. Every date comes from a named source.
| Date | Event | Source |
| May 22, 2026 | Anthropic reports that Claude Mythos Preview and about 50 Project Glasswing partners found more than 10,000 high or critical vulnerabilities, with 97 of 23,019 open-source findings patched | The Decoder |
| August 2026 | Clinton warns that a vulnerability surge will arrive within months | NewsBytes, Magica |
| Oct. 21, 2026 | PHP ships emergency updates for two critical flaws | Magica, Tasnim News |
| Oct. 22, 2026 | Clinton asks the industry to hold on for about 18 months | OfficeChai |
Counting 18 months from Clinton's Oct. 22, 2026 post, as OfficeChai reported it, lands in April 2028, which gives communications teams a planning horizon. Clinton did not say that every incident ends then, only that the pressure would ease as cheap verification tools reach developers.
How did October's incidents play out in public?
October's incidents played out through four kinds of public voices: a platform CEO, government agencies, an affected company and the stock market. Each spoke on a different clock, and the companies caught in the middle had to speak into all four at once. The details come from OfficeChai's reporting on the week.
The CEO of Cloudflare told the public that exploit attempts against the PHP flaws rose from thousands to millions within hours. Japan's Prime Minister and the FBI took to X to urge patching. Railway disclosed a breach and paused all deployments because customer secrets may have been exposed. In India, eMudhra's stock hit a 20 percent lower circuit after a certificate key compromise, and the company lost roughly ₹1,450 crore in market value in two days, according to OfficeChai.
The lesson for PR teams is about sequence. Third parties set the pace before most affected companies had finished their own investigation. A company that waited for a complete picture spoke after governments, vendors and investors had already framed the story.
Which communications teams are most exposed?
Communications teams at software vendors, cloud platforms, developer tools and identity providers are most exposed, because October's incidents hit those categories directly. The table maps each incident type to the audience that asks first and the PR task that follows. It is this article's analysis of the reported events.
| Incident type | Reported example | Who asks first | PR task |
| Language or runtime flaw | PHP, two critical bugs | Customers running the software | Say whether the company is affected and what it has patched |
| Cloud platform breach | Railway paused deployments | Developers holding secrets on the platform | State what may be exposed and what customers should rotate |
| Developer tooling flaw | Node.js Brotli decoder, with Vercel firewall rules | Engineering teams and hosting customers | Explain mitigations that exist before a full fix |
| Certificate or key compromise | eMudhra | Investors, regulators and relying parties | Coordinate market disclosure with customer notices |
Security vendors carry an extra burden because their customers judge the product by the vendor's own conduct. EPR's cybersecurity vendor ranking in AI search shows which vendors AI assistants name first, and that is the audience a vendor's own incident statement will reach.
What belongs in a first statement during a surge?
A first statement during a surge should contain five items: what is affected, what customers should do now, what is still unknown, the time of the next update and a named contact. Each item answers a question that customers, reporters and regulators ask in the first hour of an incident.
- State what is affected in plain terms, for example which product and which version, so customers can check themselves.
- Give one action customers can take today, such as rotating secrets or applying a patch, because customers read for instructions before they read for explanation.
- Say what is not yet known. Railway's notice that customer secrets may have been exposed shows that calibrated uncertainty can be published within the incident window.
- Print the time of the next update. A fixed time stops repeated calls for status between statements.
- Name a person or team customers can contact, so the statement does not read as a one-way broadcast.
EPR's European cybersecurity breach responses collects sourced cases, including Norsk Hydro, Maersk and Ireland's HSE, for teams that want historical models of how large organizations communicated during major incidents.
How have breach disclosure standards moved?
Breach disclosure standards have moved toward faster, formal notice under regulatory mandates in the United States and Europe. The SEC's Form 8-K Item 1.05 requires US public companies to disclose a material cybersecurity incident within four business days of determining it is material, and GDPR Article 33 sets a 72-hour window to notify the supervisory authority where feasible. Legal counsel decides which rules apply to a given company.
EPR's overview of AI-compressed attacks and the SEC disclosure era traces how shorter attack windows and the four-day rule changed cybersecurity communications in 2026. Clinton's forecast adds pressure to the same pinch point: if more flaws are found and exploited faster, the interval between discovery and disclosure keeps shrinking.
Anthropic's own data points to why. Anthropic reported in May 2026 that a high or critical bug takes about two weeks to fix on average, and The Decoder noted that Palo Alto Networks shipped five times as many patches as usual in its latest release. Microsoft said the number of new patches would keep trending larger for some time. More patches mean more advisories, and each advisory is a potential customer question.
What should communications leaders watch through 2028?
Communications leaders should watch four measurable indicators through 2028: patch volumes from major vendors, the share of discovered flaws that get patched, the speed of exploitation after disclosure and the arrival of cheap code verification. Each indicator tells a communications team whether the pressure is rising or easing.
- Patch volumes from major vendors, because Palo Alto Networks and Microsoft both reported larger patch counts in 2026.
- The patched share of discovered flaws, which stood at 97 of 23,019 open-source findings on May 22, 2026, according to The Decoder.
- The time between public disclosure and mass exploitation, which Cloudflare's CEO put at hours in the PHP case.
- Adoption of low-cost verification inside developer pipelines, which Clinton calls the path to vulnzero.
The constructive reading of Clinton's forecast is that preparation pays off. Clinton asked security leaders to seek funding for the basics, including patching, access control and network segmentation, and communications teams can support that case with dated public examples of what failures cost. EPR's ranking of cybersecurity PR agencies helps companies find outside support for the technical side of that work.
Sources and dates used in this article
- OfficeChai, Oct. 23, 2026: Clinton's Oct. 22 post, the PHP, eMudhra, Railway, Node.js and Vercel incidents, and vulnzero.
- The Decoder, May 23, 2026: Anthropic's Project Glasswing update, with counts as of May 22, 2026. Read the full Glasswing summary.
- NewsBytes, Magica and Tasnim News, October 2026: the August 2026 warning and the PHP patch date.
- Xataka, October 2026: Clinton's career background.
- SEC Form 8-K Item 1.05 and GDPR Article 33: the disclosure clocks.