/
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
Handles
Browse by social media handle
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

AWS analysts say that at least one actor attempted to exploit the PHP2Shell vulnerabilities on October 17, four days before their public disclosure and patching

and used—the PHP vulnerabilities before they were disclosed.  And of course now everybody's getting in on it. from @lhn.bsky.socialAndrew Couts /@couts: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...

Wired Lily Hay Newman

Context & Ripple Effects

PHP’s creators disclosed two critical unauthenticated remote-code-execution flaws affecting web-serving deployments in the PHP2Shell disclosure. AWS telemetry indicating exploitation before that disclosure changes the response from patching a newly public flaw to investigating possible prior compromise. The pattern recalls Log4j attacks observed before mass exploitation, where early attacker activity preceded a broader defensive scramble.

First-order effects

  • Affected PHP operators must treat the released security updates as incident-response work as well as patching, because AWS observed attempts to exploit the flaws before the public advisory.
  • AWS’s MadPot observations give defenders evidence that PHP2Shell was already being used by multiple malicious actors, rather than existing only as a disclosed vulnerability.

Second-order effects

  • Hosting providers and security teams protecting PHP deployments face pressure to search logs and exposed services for pre-patch activity, not merely verify that updates were installed.
  • PHP’s disclosure process is tested against an attacker timeline that began before public visibility, increasing the value of independently observed exploitation evidence in vulnerability triage.

Third-order effects

  • Broadly deployed web-software flaws are increasingly judged by the gap between attacker discovery and public remediation, not just by their severity rating.
  • If early exploitation becomes a recurring feature of major disclosures, vulnerability response will shift further toward continuous exposure monitoring and evidence-backed detection alongside patch management.

The trend: PHP2Shell is part of a trend in which attackers exploit high-impact web vulnerabilities before public advisories turn them into mass patching events.

Discussion

  • @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...
  • @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/...
  • @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…
  • @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.
  • @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/...
  • @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/...
  • @jeremy_kirk Jeremy Kirk on x
    Amazon detected PHP2Shell exploitation on a honeypot four days before public disclosure: https://aws.amazon.com/...
  • @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
  • r/ReverseEngineering r on reddit
    There isn't an easy exploit for this PHP vulnerability
  • @chainguard_dev @chainguard_dev on x
    Two critical PHP vulnerabilities (CVSS 9.2) were disclosed today, allowing unauthenticated RCE on default configurations. To help everyone patch fast we are making images for PHP 8.2, 8.3, 8.4, and 8.5 free for anyone to use. You can access them here: https://images.chainguard.de…
  • @naderman Nils Adermann on x
    Read the story around the security vulnerabilities fixed in PHP today that I wrote up for the PHP Foundation, what an exhausting last week in this process. Glad it's out, hoping you all update ASAP.
  • @andrewmohawk @andrewmohawk on x
    https://thephp.foundation/... Really disappointing that companies put marketing ahead of safety. [image]
  • @mikko @mikko on x
    @mikko  —  “On October 21st at 07:41 UTC, more than six hours before the coordinated release …
  • @arvidkahl Arvid Kahl on x
    One thing I really don't understand is why, with Cloudflare already reporting attacks, @ThePHPF didn't release their fixes asap. I get the “once patched, the vuln is exploitable on unpatched servers.” But right now, EVERY server is exploitable. Is that better?!
  • @thephpf @thephpf on x
    We have posted more information about today's security releases, including the sequence of events that led to the discovery, how the PHP security team is improving their processes, and what we need from you to continue this critical work. #php #security https://thephp.foundation/…
  • @marypcbuk Mary Branscombe on bluesky
    PHP Foundation kind of found the first vuln in 2024 but “the PHP security team, operating on consensus, struggled to choose between these and feared the repercussions of shipping the wrong choice”  —  don't dunk on a bunch of volunteers for that; dunk on everyone depending on but…
  • @lookitup.baby Ian Coldwater on bluesky
    The leak wasn't OpenAI's fault.  Chainguard unilaterally broke the embargo by releasing built images with fixes before the vulnerabilities were disclosed, forcing maintainers to scramble to release the patches early.  —  This industry is small and you just can't treat people like…
  • @avandeursen@mastodon.acm.org Arie van Deursen on mastodon
    Must-read blog post from the PHP foundation:  —  > [ In 2024 ] a PHP core developer contracted by the PHP Foundation found the first signs of the [out-of-memory] OOM problem behind CVE-2026-109618.  —  > the lack of a known path to remote code execution and the small team of core…
  • r/programming r on reddit
    Today's PHP Security Release, and How We're Strengthening PHP Security
  • r/cybersecurity r on reddit
    Today's PHP Security Release, and How We're Strengthening PHP Security — The PHP Foundation
  • @dok2001 Dane Knecht on x
    PHP sites behind Cloudflare already have an initial set of WAF rules deployed for the known exploit vectors in these vulnerabilities. The rules are available to all customers, including free. We are seeing early attacks emerging and are updating mitigations as new vectors show up…
  • @eastdakota Matthew Prince on x
    Some stats on #php2shell. In the 10 hours before it was publicly announced, across the @Cloudflare network we saw thousands of attempts to exploit it. That jumped to tens of thousands in the 45 minutes post announcement, hundreds of thousands within 2 hours, and millions now.
  • @burcs Brandon on x
    overwhelmed by the php vulns and not sure how or where to get started? we've added a copyable prompt to the cloudflare blog that you can feed your agent https://blog.cloudflare.com/ ... [image]
  • @google @google on x
    Researchers at @wiz_io put Gemini 4 Argon to the test against complex cyber threats. In real-world testing, it found more than two times more vulnerabilities than baseline models — catching a critical risk that previous frontier models missed. See how they did it ↓
  • @eastdakota Matthew Prince on x
    We had to invent a new form of WAF to mitigate this latest set of vulnerabilities. Now enabled by default for all customers for free.
  • @mitsuhiko Armin Ronacher on x
    I was super critical for years that Cloudflare turns into a single point of failure for many sites. But the flipside is that it's also has a really good positive leverage affect on security. This is great stuff. https://x.com/... [embedded post]
  • @rhyssullivan Rhys on x
    If you self host software, you really should put it behind either Cloudflare or Vercel's firewall The firewall rules & data they have on how people try to run exploits are so critical right now
  • @cloudflare @cloudflare on x
    Cloudflare has deployed default web application firewall (WAF) protections for newly disclosed PHP vulnerabilities before public disclosure. The rules use request and response signals to stop exploit attempts and prevent exposed data from reaching attackers. https://blog.cloudfla…
  • @dok2001 Dane Knecht on x
    The Cloudflare's writeup on our php2shell response is up. Rules went live at 03:02 UTC, about 9 hours before disclosure. Unfortunately the vulnerability leaked early, so we were already watching attackers mutate payloads against the rules and updating as variants appeared. New ru…
  • @burcs Brandon on x
    it's kind of wild to work at a company that can basically flip a switch and protect 20% of the internet from critical vulns [embedded post]
  • @tridevgurung Tridev Gurung on x
    we've temporarily taken buymemomo offline as a precaution, which is why you'll be seeing this screenshot. …
  • @alphaque Dinesh Nair on x
    Cloudflare is already detecting early attacks from the zero day RCEs for PHP, which powers many Malaysian websites. MKN, NACSA, National Cybersecurity Committee, MCMC have not issued any warnings nor are they doing anything about it. They're more worried about the Waze juice. [em…
  • @uwu_underground @uwu_underground on x
    Step 1. Fuzz your CloudFlare servers to figure out what gets filtered at the WAF level Step 2. reverse engineer a vulnerability Step 3. Profit [embedded post]
  • @arvidkahl Arvid Kahl on x
    Another reminder of why our $5/month is extremely well spent. [embedded post]
  • @cstanley Christopher Stanley on x
    Thanks Dane, Cloudflare has always been a huge shield for the public. Appreciate you all so much. [image] [embedded post]
  • @blackroomsec @blackroomsec on x
    Reposting this from my own comment so you all see it.  Re: PHP patch today. …
  • watchTowr watchTowr on linkedin
    🚨 Yesterday, information leaked about two Remote Code Execution vulnerabilities in PHP, now known as “PHP2Shell” (CVE-2026-109618 …
  • r/anime_titties r on reddit
    PHP2Shell: AI uncovers critical RCE vulnerabilities affecting 70% of the Internet
  • r/cybersecurity r on reddit
    Wiz got pre-auth RCE on WordPress, Drupal and Joomla through vulnerabilities in PHP itself
  • r/GeminiAI r on reddit
    Gemini 4 Argon credited for “invaluable contributions” to PHP2Shell vulnerability discovery
  • @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/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
  • r/kubernetes r on reddit
    PHP blames Chainguard for putting huge chunks of the web at risk
  • r/PHP r on reddit
    Today's PHP Security Release, and How We're Strengthening PHP Security
  • 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. …
  • 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. …
  • 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. …
  • @mciabuca Mike on x
    @Techmeme @abhiiswriting my phone pin has more bits than that
  • @bee_fumo @bee_fumo on x
    Holy fucking shit it actually killed them. https://www.reuters.com/... [image]
  • r/IndianStreetBets r on reddit
    eMudhra to exit global website security certificate business after key-generation flaw
  • r/LinusTechTips r on reddit
    Can't make this shitup, Indian CA's root private certificate fiasco
  • @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…
  • @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/...
  • @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...
  • 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?
  • @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/...
  • @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