Research collected from outside sources and what this site derives from them; every fact links to a saved copy of its source Research or story?
Source · news · secondary · captured
php2shell: PHP-Schwachstellen CVE-2026-109618 und CVE-2026-109619Borns IT- und Windows-Blog
Promoted from the source watch (pack copy 7r83qic5), snapshot 20261023T160435Z, queue priority 3 (mechanical selection by researcher@php.newsroom, read by the curator). Born's IT and Windows blog (German), 21 October: two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, became public. The PHP maintai...
What it says, as the collector read it
php2shell: PHP-Schwachstellen CVE-2026-109618 und CVE-2026-109619Borns IT- und Windows-Blog
Promoted by curator@php.newsroom from the source watch (vault oq9gflln, read from its pack copy 7r83qic5), page at/news/borncity/blog-2026-10-21-php2shell-php-schwachstellen-cve-2026-109618, snapshot 20261023T160435Z. Copied byte for byte; every file's sha256 is in captures/20261023T160435Z/provenance.json and was re-checked against the watch's own hashes.
What the page says
_Curator's reading of the capture._
Born's IT and Windows blog (German), 21 October: two critical PHP vulnerabilities, CVE-2026-109618 and CVE-2026-109619, became public. The PHP maintainers had announced on 20 October that details and patches would follow on 21 October; information apparently leaked beforehand. A long running post (about 64,000 characters) with later updates; the opening was read in full.
> Die PHP-Maintainer haben zum 20. Oktober 2026 angekündigt, am heutigen 21. Oktober 2026 Details und Patches zu veröffentlichen.
_Curator's translation:_ "The PHP maintainers announced for 20 October 2026 that they would publish details and patches today, 21 October 2026."
_The watch reader's summary (researcher@php.newsroom, of its snapshot 20261022T181608Z, not necessarily this one):_ Günter Born's IT blog covers the leak and pre-announcement of the PHP fixes, notes that 8.1 and older will not be patched, and reports readers taking WordPress/Nextcloud instances offline or behind passwords. It mentions a BSI warning (criticality 3/orange), Huntress's John Hammond on webshells, and links to follow-up articles.
Why it is here
From the promotion queue (index/promote.json, priority 3): Mentions CVE-2026-109618/109619 or php2shell: "php2shell: PHP-Schwachstellen CVE-2026-109618 und CVE-2026-109619Borns IT- und Windows-Blog". Selected mechanically, not read by a person. Text also matches compromise/breach terms: check for a named organisation or cause.
Capture notes
Language de. Nothing in the page addresses an AI or hides text from a reader.
Claims that cite it
No claim cites this source yet.
Events that cite it
No timeline event cites this source yet.
The bytes
capture 20261023T160435Z · HTTP 200 · https://borncity.com/blog/2026/10/21/php2shell-php-schwachstellen-cve-2026-109618-und-cve-2026-109619/
headers.jsone5590d010f043055660e961be0a483504d7a4ed93480c36a288ca3f595ffbc6e 794 bytespage.html625aa0a420a0a900dfba6aad62794bd507aa5e6807aee58a816a4314d5539606 355,141 bytesprovenance.jsonc710138a52c85dedbb612a3dc83558a915acec7e9fb87c601bd687f9c55e3d54 1,811 bytesrendered.htmlea2064e3b443f7b73db67225a5b4a7047364619c3c600d923e4c3b23a2c4e3e8 364,116 bytesscreenshot.jpg597e71c72aa7ca054f0eaaacb05839f2cb45cc1795d5f0377bbf145dfa050fac 650,886 bytestext.txtac019c2d35b1f126f0a4b19cc896409cde99b37682e90df4cff859aeb76b3ac5 65,743 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 →