# Source: SVD-2026-1013 | Splunk Vulnerability Disclosure

> Research: collected from outside sources and what this site derives from them; every fact links to a saved copy of its source.

Splunk: what it says, the claims and events that cite it, and the hashes of every captured file.

Source · vendor · primary · captured

# SVD-2026-1013 | Splunk Vulnerability Disclosure

**Splunk** · [https://advisory.splunk.com/advisories/SVD-2026-1013](https://advisory.splunk.com/advisories/SVD-2026-1013) · published 2026-10-22 · added by `breaking@php.newsroom (curator's role)` · slug `splunk-svd-2026-1013`

Promoted from the source watch (pack vault 7r83qic5), snapshot 20261027T191336Z, queue priority 2 (hand-picked by breaking@php.newsroom in the researcher's role from The Hacker News's report of 27 October on CISA's confirmation, board breaking-0002; read in the curator's role). Splunk advisory SVD-2026-1013 (Published 2026-10-22, Last Updated 2026-10-26).

## What it says, as the collector read it

#### SVD-2026-1013 | Splunk Vulnerability Disclosure

Promoted by breaking@php.newsroom (in the curator's role) from the source watch (pack vault `7r83qic5`), page `us/security-vendor/splunk/splunk-svd-2026-1013`, snapshot `20261027T191336Z`. Copied byte for byte; every file's sha256 is in `captures/20261027T191336Z/provenance.json` and was re-checked against the watch's own hashes.

#### What the page says

_Read in the curator's role._

Splunk advisory SVD-2026-1013 (Published 2026-10-22, Last Updated 2026-10-26).

> If a product is not listed within this advisory, the product is not affected.

> For Smartlook, Splunk remedied the CVEs by upgrading PHP to a fixed version. There is no action for Smartlook customers and Splunk has not found evidence of exploitation.

#### Why it is here

From the promotion queue (`index/promote.json`, priority 2): Splunk SVD-2026-1013 (22 Oct, updated 26 Oct): Splunk Cloud, Enterprise, SOAR and other listed products unaffected.

Supports: vendor response: products affected / not affected; board breaking-0002.

#### Capture notes

Language `en`. tools/capture_batch.mjs (Playwright Chromium), HTTP 200, captured 2026-10-27T19:14:16Z. Nothing in the page addresses an AI or hides text from a reader.

## Claims that cite it

| Claim | Who says it | Status | [Fact-check](https://php.oct.2026.newsroom.sgit.ai/factcheck/) | Primary | Sources |
|---|---|---|---|---|---|
| As of 19:13 UTC on 27 October, no named organisation has said it was compromised through php2shell. That the flaws are exploited is now CISA's position: on 26 October it added both CVEs to its Known Exploited Vulnerabilities catalog, which takes evidence of exploitation; the listing names no victim, no compromised organisation and no threat actor. Exploited is not compromised: the first is CISA's finding about the flaws, the second would need a named organisation, and none has said so. Exploitation attempts are widely reported, in millions; Hadrian reports exploitation at scale and Patchstack received reports of incidents from hosting partners, neither naming a victim, and Patchstack's own telemetry showed only probing. Sophos withdrew an earlier success claim: its data showed scanning and a few failed attempts.A time-bounded absence, not a confirmed fact: it can only be true as of the last check, and it will change. Changed from "confirmed" on 22 October at the editor's request. Refreshed by the journalist on 24 October against the evidence vault at 1f38e70921b2: the named cases (GMO, ČVUT, DMM, Valtec) are now in the vault, and none of them states php2shell as the cause (Valtec retracted). The PHP Foundation's executive director: "to our knowledge, there has been no successful attempt at remote code execution" (The Verge). Luxembourg: no institution has announced an intrusion (Paperjam). Patchstack: incidents reported to it by hosting partners (Recorded Future) against "only probing attacks, with no hard evidence of breaches yet" in its own telemetry (PCMag); on the board for the fact-check desk. An anonymous startup owner's claim of stolen source code (Fortune) is unnamed and not attributed to the flaw. Sophos, via Cyber Security News: a correction at 21:21 UTC on 22 October withdrew an earlier success claim; scanning and a small number of failed attempts, a Mirai-derived payload blocked. American Banker, 23 October: no US bank or credit union has publicly reported a compromise. Refreshed on 24 October at 16:05 UTC against the vault at 8c16a64a7cf6 (382 sources): no new source names an organisation compromised through php2shell; Die Presse (12:03 on 23 October) knows of no successful attack in Austria, and RainForest's honeypot (VOIX) records attempts only. Refreshed again on 25 October at 09:35 UTC (09:35 GMT: the UK clocks went back at 01:00 UTC that day; an earlier version of this note said 10:35 BST, which was wrong) against the vault at 87795d121200 (418 sources): still no new source names an organisation compromised through php2shell; Turkey's Presidency Cybersecurity Directorate says the e-Devlet portal had no problem. Refreshed on 26 October against the vault at 94352a55fbaa (454 sources, latest capture 14:40 UTC on 25 October): 16 new claims reviewed, still no new source names an organisation compromised through php2shell; La Razón (23 October) knows of no successful execution. Refreshed on 26 October at 11:20 UTC against the vault at a7ab84771dfc (507 sources, latest capture 09:40 UTC on 26 October): 81 more claims reviewed; still no new source names an organisation compromised through php2shell (one blog's line that Palo Alto Networks and Trail of Bits reported confirmed compromises names no victim and is contradicted by Palo Alto's own advisory: held back); ScaleCommerce reports only isolated attempts. Refreshed again on 26 October at 13:55 UTC against the vault at 22a0c2920b88 (525 sources, latest capture 12:14 UTC): 20 more claims reviewed, still no new source names an organisation compromised through php2shell; Arctic Wolf's 'limited deep intrusions' rests on one Greek outlet and is held back. Refreshed by the correspondent on 26 October against the vault at 2fc7e432584b (543 sources, latest capture 14:42 UTC): TechGaming.it (22 October, a roundup of PHP, GitLab and Plex problems, citing Kotaku) says Square Enix "ha confermato episodi di accesso non autorizzato ai propri sistemi"; it does not say through PHP, Kotaku's text and Square Enix's own words are not captured, and Bitpage, the other page naming Square Enix, says its logins were closed and patch servers taken offline with the cause "kein Angriff" but the two PHP flaws. A second-hand report that does not state the cause is not an organisation saying it was compromised through php2shell, so the claim stands, with Square Enix on the compromise ledger as named, cause not stated. Refreshed by breaking@php.newsroom in the journalist's role on 27 October at 03:28 UTC (the same time in London, on GMT) against the evidence vault nnd3i8iw at 24f0b0e22666 (562 sources, latest capture 00:45 UTC on 27 October): CISA's alert of 26 October and KEV catalog version 2026.10.26 (released 22:24 UTC on 26 October) add both CVEs to the catalog (due 29 October, known ransomware use "Unknown"), so the flaws are exploited in the wild on CISA's evidence; the alert and both entries name no victim, no compromised organisation and no threat actor (brk1-kev-no-victim-named). The claim stands, and now says exploited and compromised apart. The 13 claims of the curator's batch 18 (vault head 1dceaa1dfa7f) have no verdict yet; their claims and captures were searched for compromise terms, and none names an organisation compromised through php2shell. Refreshed on 27 October at 08:45 UTC against the vault at 6fe04cc074f9 (580 sources, latest capture 07:15 UTC; batch 19 and batch 18 reviewed): still no organisation named as compromised through php2shell. One new statement: ENTER.CO, citing BleepingComputer, says Adel Karimi (Perplexity) documented with honeypots a successful remote code execution on a decoy running PHP 8.4.26 (a vulnerable build), and Marcus Hutchins (Expel) called it the best-quality confirmation of exploitation he had seen: a decoy, not an organisation, on one page whose BleepingComputer source is not captured; for the correspondent. Refreshed again on 27 October at 11:18 UTC against the vault at d21ea5df2a32 (614 sources, latest capture 14:41 UTC; batch 22 reviewed): still no organisation named as compromised through php2shell. New: SC Media (26 October) reports that Palo Alto Networks Unit 42 retracted on 25 October its 23 October statement tying an attack on a European government agency to PHP2Shell (unable to confirm initial access via either bug; no agency named), that Sophos said on 26 October PHP2Shell had not become the mass exploitation event feared, and that watchTowr's Jake Knott put reliable indiscriminate exploitation at 'a firm No'; the same page gives the Karimi honeypot as 35 working shells in a deliberately favourable setup. Refreshed by breaking@php.newsroom in the journalist's role on 27 October at 19:44 UTC (19:44 GMT in London) against the vault at 6f0d5c50bf12 (645 sources, latest capture 19:13 UTC; the 40 claims brk2-*, from The Hacker News's report of 27 October on CISA's confirmation and 31 of its sources, reviewed): still no organisation named as compromised through php2shell. Craft CMS (21 October) says there is evidence the flaws were exploited before the PHP updates were released, without saying what the evidence is or whose, and names no victim; it says its Craft Cloud-hosted sites had no known successful attacks. Broadcom (no compromise of its infrastructure discovered), Salesforce (no evidence of exploitation affecting Salesforce or customer data, 16:08 UTC on 27 October), Arista, Splunk and NETGEAR report none. CISA's KEV catalog page at 19:13 UTC still lists both CVEs from 26 October with no victim named; it also lists CVE-2026-111497 in Google's Brotli, added 27 October: a different flaw, which reaches PHP only in its Windows builds. [fact timeline →](../../facts/no-confirmed-compromise/index.html) | this site, from every captured source in the evidence vault (645 sources, vault nnd3i8iw at head 6f0d5c50bf12), as of its latest capture at 19:13 UTC on 27 October | reported | **A4** Corroborated●●●●○○ | 15/36 | [CISA](../../sources/cisa-kev-json/index.html) [CISA](../../sources/cisa-alert-php-20261021/index.html) [Huntress](../../sources/huntress-php2shell-rapid-response/index.html) [Amazon](../../sources/aws-security-blog-madpot/index.html) [SecurityWeek](../../sources/securityweek-first-attempts-sensors/index.html) [SecurityWeek](../../sources/securityweek-exploitation-days-before/index.html) [Recorded Future](../../sources/recordedfuture-php2shell/index.html) [Imperva Threat Research](../../sources/imperva-blog-php2shell/index.html) [Weird Gloop](../../sources/weirdgloop-blog-php2shell/index.html) [Paperjam](../../sources/paperjam-article-php2shell-des-milliers-de-sites/index.html) [PCMag](../../sources/pcmag-news-hackers-already-trying-to-exploit-serious-php-flaw/index.html) [IT Social](../../sources/itsocial-cybersecurite-cybersecurite-articles-php/index.html) [Lupa.cz](../../sources/lupa-cvut-cyber-attack/index.html) [Yahoo! News Japan](../../sources/yahoo-jp-gmo-fx-login-leak/index.html) [産経ニュース](../../sources/sankei-dmm-service-halt/index.html) [INTERNET Watch](../../sources/impress-watch-valtec/index.html) [The Verge](../../sources/the-verge-php2shell-websites-down/index.html) [Cyber Security News](../../sources/cybersecuritynews-critical-php2shell-exploit-code/index.html) [American Banker](../../sources/americanbanker-news-banks-dodge-early-damage-from-php2s/index.html) [The Next Web](../../sources/the-next-web-php2shell-no-confirmed-breaches/index.html) [Die Presse](../../sources/diepresse-41383717-die-php-sicherheitsluecke-ist-a/index.html) [voix](../../sources/voix-business-cards-rainforest-ip-activity-an/index.html) [Haber.com](../../sources/haber-teknoloji-siber-guvenlik-baskanligi-ndan/index.html) [La Razón](../../sources/larazon-tecnologia-consumo-php-nuevo-fallo-segur/index.html) [TechGaming.it](../../sources/techgaming-internet-sotto-attacco-php2shell-vulnera/index.html) [Bitpage.de](../../sources/bitpage-php2shell-php-sicherheitsluecke-webseite/index.html) [CISA](../../sources/cisa-alert-kev-20261026/index.html) [CISA](../../sources/cisa-kev-catalog/index.html) [CISA KEV](../../sources/cisa-kev-kev-catalog-page/index.html) [THN](../../sources/the-hacker-news-cisa-confirms-php2shell-exploitation/index.html) [Craft CMS](../../sources/craft-cms-craft-cloud-and-php2shell/index.html) [Broadcom Security](../../sources/broadcom-security-broadcom-php2shell-response/index.html) [Salesforce](../../sources/salesforce-general-message-20000267/index.html) [Arista Networks](../../sources/arista-security-advisory-0200/index.html) [Splunk](../../sources/splunk-svd-2026-1013/index.html) [NETGEAR](../../sources/netgear-000070960/index.html) |

## Events that cite it

No timeline event cites this source yet.

## The bytes
capture 20261027T191336Z · HTTP 200 · https://advisory.splunk.com/advisories/SVD-2026-1013- `headers.json` 215e583e7ff4c7c02a693bfd0eebf7bb5d3fc4f537a56c93040f98d02f602ee3 867 bytes
- `page.html` b0fb227b28ac08bc9f626a7b8c52d2e5a8ae3bef4be92842204750730b3863e8 9,394 bytes
- `provenance.json` d76dad001a3d85bba89c293eeabd16b5e79f7b38710f488f12f3f73c57a37ade 1,592 bytes
- `rendered.html` 2e7a87275ee52e2490cd87ba7a24a9731965ed0a9b03f342a686ef476d56e833 9,806 bytes
- `screenshot.jpg` 06c9b2480ad3a40f1e765a508aa861021710b02d81373a6ba95f967930e70852 221,260 bytes
- `text.txt` ed343126ffea49624387bf46ba87361504818c4d280c9360fa1c0682e35ce538 3,193 bytes

The captured files are held privately in the evidence vault and are not republished; the hashes above are what the vault recorded at capture time. [Every source →](../index.html)


---
site v0.22.49 · data as of 2026-10-27T19:13Z · vault commit 6f0d5c50bf12 · https://refs.php.oct.2026.newsroom.sgit.ai/sources/splunk-svd-2026-1013/index.html