/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

← → days · ↑ ↓ browse · Enter similar · o open

Cloudflare's Matthew Prince says PHP2Shell exploit attempts on its network rose from thousands in the 10 hours before the disclosure to millions afterward

Matthew Prince /@eastdakota:

@eastdakota Matthew Prince

Context & Ripple Effects

The PHP2Shell disclosure arrived after an attempted exploitation four days before patches were public, making the vulnerability an active-response event rather than a purely theoretical flaw. Cloudflare had already enabled default WAF mitigations for its free and paid customers roughly nine hours before disclosure.

Prince's traffic figures show how quickly public technical detail translated into automated probing across Cloudflare's network, putting patching and edge-layer defenses on parallel tracks.

First-order effects

  • Cloudflare customers received the company’s pre-deployed WAF mitigation by default as exploit attempts jumped from thousands before disclosure to millions afterward.
  • PHP site operators outside that protection layer face an immediate surge in automated attempts and must prioritize the disclosed patches and their own compensating controls.

Second-order effects

  • Other CDN and WAF providers are pressured to turn signatures into default protections quickly, since a post-disclosure attack wave can arrive before every customer has patched.
  • Hosting providers and managed-service firms must treat edge filtering as a bridge to patching, not a replacement for it, because the reported pre-disclosure attempt indicates attackers were already testing the flaws.

Third-order effects

  • The episode points to a shrinking window between vulnerability disclosure and mass exploitation, increasing the value of providers able to deploy protections across many customers by default.
  • If pre-disclosure exploitation becomes more common for broadly deployed software, coordinated patch releases and pre-positioned mitigations will matter as much as the public advisory itself.

The trend: Critical software disclosures are becoming coordinated defense races in which cloud-edge providers seek to blunt automated exploitation before customers can complete patching.

Discussion

  • @ctrlaltdwayne Dwayne on x
    Philomena: Some people have been writing PHP for over 20 years. Is that because it's particularly difficult to finish? Expert: No, software is constantly evolving. Philomena: So they've been writing the same website for 20 years? Expert: No, different projects. Philomena: Have th…
  • @bettycjung Betty C. Jung on bluesky
    Millions of hacking attempts as companies, governments rush to patch PHP flaws www.reuters.com/world/asia-p...
  • r/PrepperIntel r on reddit
    Millions of hacking attempts as companies, governments rush to patch PHP flaws
  • r/news r on reddit
    Millions of hacking attempts as companies, governments rush to patch PHP flaws
  • r/worldnews r on reddit
    Millions of hacking attempts as companies, governments rush to patch PHP flaws
  • @lukolejnik Lukasz Olejnik on x
    PHPocalypse flaws existing for a decade, identified with the help of AI, let attackers hijack web servers without logging in. Amazon & Cloudflare reported exploitation attempts days before disclosure. Now the flaws are broadly exploited. Cybersecurity agencies (US, UK, EU, you na…
  • @anthonyronning Anthony Ronning on x
    Yeah I mean honestly, a significant CVE where multiple people independently found the vulnerability at nearly the same exact time should not be sat on for 2 months. Not only was this irresponsibly disclosed but it was irresponsibly held back too. I'm not sure how that happens.
  • @sughanthans1 @sughanthans1 on x
    aws says a 7-day patch deadline is now too slow for critical bugs in anything facing the internet. it wants teams to measure patching in hours. php2shell shows why. aws's honeypots logged an exploit attempt on october 17, four days before the bug went public. and aws spotted expl…
  • @jeremy_kirk Jeremy Kirk on x
    Amazon detected PHP2Shell exploitation on a honeypot four days before public disclosure: https://aws.amazon.com/...
  • @dinodaizovi Dino A. Dai Zovi on x
    Periodic reminder that for every serious, exploitable vulnerability that you find out about and patch, there was some level of exploitation of it *before* then.
  • @frichette_n Nick Frichette on x
    Turns out details leaked even sooner than previously believed. AWS saw exploitation on the 17th! https://aws.amazon.com/...
  • @4n6lady @4n6lady on x
    PHP2Shell (CVE-2026-109618/109619) hit our MadPot honeypots on Oct 17, four days before disclosure. Investigating? Start your timeline there, not at the advisory date. Patch to 8.5.12 / 8.4.27 / 8.3.36 / 8.2.35 now. https://aws.amazon.com/...
  • @dnvolz Dustin Volz on x
    Fascinating. Amazon says it has telemetry showing PHP2Shell was being exploited on Oct. 17—that is, four days prior to public disclosure. Not known who was doing it. “It remains unclear how the actor acquired exploit information prior to disclosure.” https://aws.amazon.com/...
  • Giovanni Ferraz Giovanni Ferraz on linkedin
    Someone tried to exploit PHP2Shell four days before it was disclosed.  —  On October 21, PHP shipped emergency fixes for two flaws in its core runtime, CVE-2026-109618 and CVE-2026-109619. …
  • CJ Moses CJ Moses on linkedin
    Two critical PHP vulnerabilities (CVE-2026-109618, CVE-2026-109619), known as PHP2Shell, are being broadly exploited in the wild. …
  • Peter White Peter White on linkedin
    70% of the world's websites depend on PHP, and the National Security Agency has just issued an urgent advisory regarding two critical vulnerabilities. …
  • @ericjgeller.com Eric Geller on bluesky
    Amazon says its telemetry shows attempts to exploit the PHP vulnerabilities on Oct. 17, four days before they were disclosed. aws.amazon.com/blogs/securi...
  • @brbarrett Brian Barrett on bluesky
    At least one hacker found—and used—the PHP vulnerabilities before they were disclosed.  And of course now everybody's getting in on it. from @lhn.bsky.social
  • @couts Andrew Couts on bluesky
    NEW: AWS detected attempts to exploit the PHP vulnerabilities on October 17, four days before they were patched.  Logs indicate multiple malicious actors tried to use the flaws. @lhn.bsky.social reports: www.wired.com/story/hacker...
  • @jacobshap Jacob L. Shapiro on x
    I'm a little confused here Is the story, omg, AI can find vulnerabilities and hack all of our systems and the internet is dying Or, wow, AI can find vulnerabilities we didn't know of and help patch them quickly, making us all safer in the long run https://www.wired.com/...
  • @m_jones_1797 @m_jones_1797 on x
    This is rather serious. About 70% of websites rely on PHP, which has been discovered to contain 2 major vulnerabilities. Cybersecurity specialists Cloudflare report thousands of attempts to exploit the vulnerability. Thankfully patches are available. https://www.ncsc.gov.uk/...
  • @danjarvismbe Dan Jarvis MP on x
    Do you want more information about how to protect your organisation following the PHP advisory notice? The UK's cyber experts at @NCSC have published six key steps for organisations - large or small - to follow today. https://www.ncsc.gov.uk/...
  • @sporadica @sporadica on x
    wait, if my math is correct.. doesn't this say that a full ONE THIRD of the Internet is just...perma-fucked?
  • @intcyberdigest @intcyberdigest on x
    The day the internet broke, and most of it is too old to fix.
  • @mondoab @mondoab on bluesky
    “The PHP Foundation has revealed two serious vulnerabilities that could impact millions of websites.  Security experts warn that failure to quickly patch the flaws could have dire consequences.”  —  www.wired.com/story/this-i...
  • @charles.littlegreenfootballs.com Charles Johnson on bluesky
    I spent most of the day upgrading and patching stuff on several sites.  —  ‘This Is Not a Drill’: Critical PHP Vulnerabilities Are Setting the Internet on Fire
  • @mattburgess1 Matt Burgess on bluesky
    “Updating is the only safe choice”  —  As PHP releases the details of its critical vulnerabilities, governments around the world are taking their websites offline for updates.  —  Security researchers warn things could be real bad if systems aren't patched immediately  —  Story w…
  • r/theprimeagen r on reddit
    There isn't an easy exploit for this PHP vulnerability
  • r/BetterOffline r on reddit
    Did LLMs' reward hacking behavior just cause a huge number of hours of cybersecurity labor to be expended for no good reason?
  • r/ReverseEngineering r on reddit
    There isn't an easy exploit for this PHP vulnerability
  • r/ItalyHardware r on reddit
    Ma che è successo a mezzo internet oggi?
  • r/technology r on reddit
    ‘This Is Not a Drill’: Critical PHP Vulnerabilities Are Setting the Internet on Fire