{"id":"EM-20261119-1AA8","url":"https://cyber.eventmonitor.net/incident/EM-20261119-1AA8/critical-php-vulnerability-cve-2026-129182/","type":"cve","title":"Critical php Vulnerability (CVE-2026-129182)","subtitle":"CVE-2026-129182","subject":"CVE-2026-129182","status":"Developing","severity":"critical","affected":[],"headline":null,"born":"2026-11-19T15:17:27.390Z","firstSignal":"2026-11-19T14:35:51.000Z","lastSignal":"2026-11-19T15:17:27.390Z","updated":"2026-11-20T02:11:11.035Z","revision":1,"life":[{"status":"Born","at":"2026-11-19T15:17:27.390Z","why":"second independent source: C6 NVD CVE API 2.0"},{"status":"Developing","at":"2026-11-19T15:17:27.390Z","why":"signals keep joining"}],"changeLog":[{"at":"2026-11-19T14:35:51.000Z","what":"First signal: C41 Red Hat Security Data"},{"at":"2026-11-19T15:17:27.390Z","what":"Born: second source, C6 NVD CVE API 2.0. Page EM-20261119-1AA8 created."}],"stages":[{"name":"Disclosed","at":"2026-11-19T15:17:27.390Z","detail":"C6 NVD published"},{"name":"Scored","at":"2026-11-19T15:17:27.390Z","detail":"CVSS 9.2"},{"name":"Exploited","at":null,"detail":"No exploitation reported"},{"name":"Advisories","at":null,"detail":"None yet"},{"name":"Vendor Response","at":"2026-11-19T14:35:51.000Z","detail":"C41 published"},{"name":"Resolved","at":null,"detail":"After 14 quiet days"}],"signals":[{"at":"2026-11-19T14:35:51.000Z","source":"C41","sourceName":"Red Hat Security Data","role":"Vendor","severity":4,"title":"Red Hat: CVE-2026-129182 (critical)","text":"php: Use-after-free via repopulation of last_fatal_error_backtrace global after shutdown","url":"https://access.redhat.com/hydra/rest/securitydata/cve/CVE-2026-129182.json"},{"at":"2026-11-19T15:17:27.390Z","source":"C6","sourceName":"NVD CVE API 2.0","role":"Database","severity":4,"title":"CVE-2026-129182 (CVSS 9.2)","text":"Use-after-free via repopulation of last_fatal_error_backtrace global after shutdown.\n\nA fatal error raised while modified INI settings are restored during request shutdown can repopulate the stored fatal error backtrace after the executor has been cleaned up. The request memory is then freed, and a diagnostic emitted before executor initialization in a later request handled by the same PHP-FPM or mod_php worker can access the stale backtrace. The shutdown error requires per-path configuration of max_memory_limit, or of zlib.output_compression together with output_handler (which .user.ini can…","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-129182"}],"crowd":[],"reference":{"nvd":{"published":"2026-11-19T15:17:27.390","score":9.2,"severity":"CRITICAL","desc":"Use-after-free via repopulation of last_fatal_error_backtrace global after shutdown.\n\nA fatal error raised while modified INI settings are restored during request shutdown can repopulate the stored fatal error backtrace after the executor has been cleaned up. The request memory is then freed, and…","product":"","seen":1795111870243},"kev":null,"epss":null,"p0":false},"mergedInto":null,"publisher":"Event Monitor Cyber"}