# PHP 19 Nov 2026 security release: detection pack

Pack 1.0.0, 19 Nov 2026. Store folder `php-security-release-2026-11-19/`, published to hubfs
`php-security-release-2026-11-19-pack-v1` (the page links that hubfs folder; the store folder name stays as it is).

## At a glance

| | | Source |
|---|---|---|
| Release | PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36, all dated 19 Nov 2026 and tagged as security releases. PHP 8.6.0 is a feature release dated the same day; php-src NEWS for 8.6.0 lists the same advisories | PHP changelog, PHP releases index, php-src NEWS |
| Advisories | 17 GitHub Security Advisories published from 14:05 GMT on 19 Nov 2026 | PHP GHSA list |
| Critical (PHP CVSS 4.0 9.2) | CVE-2026-115560, CVE-2026-126714, CVE-2026-129182, CVE-2026-129289, CVE-2026-129474, CVE-2026-129481, CVE-2026-129496 | PHP GHSA advisories |
| High | CVE-2026-129291 (8.8), CVE-2026-127960 (8.7), CVE-2026-128064 (8.2), CVE-2026-128090 (7.7) | PHP GHSA advisories |
| Medium | CVE-2026-129538 (6.9), CVE-2026-129438 (6.3, PHP 8.5 and 8.6), CVE-2026-129501 (6.3, PHP 8.4 and later), CVE-2026-129506 (6.3), CVE-2026-15353 (6.3), CVE-2026-129292 (5.3) | PHP GHSA advisories |
| Also listed in 8.5.13 and 8.6.0 notes | Upgrade to uriparser 1.0.3 (CVE-2026-48841). This is a bundled-library bump, not one of the 17 php-src GHSAs | PHP changelog, php-src NEWS |
| Exploitation | No exploitation reported by PHP or CISA as of 19 Nov 2026. Not in CISA KEV (catalogue 2026.11.18, date released 19:17 GMT on 18 Nov 2026) | PHP advisories, CISA KEV |
| Related, already in KEV | PHP2Shell CVE-2026-109618 and CVE-2026-109619 (added 26 Oct 2026), fixed earlier in 8.2.35, 8.3.36, 8.4.27 and 8.5.12. This release includes incomplete-fix follow-ups for CVE-2026-109619 (see below) | CISA KEV, PHP advisories |

**Patch now regardless of KEV status.** Confirm the running PHP worker, not only the package, reports a fixed build, then restart every worker.

This pack uses the word Critical only for the seven CVEs that PHP scores CVSS 4.0 9.2. High and Medium items are not called Critical, including where the impact is serious (for example CVE-2026-129291).

## Affected and fixed, every CVE in the release

Ranges and CVSS 4.0 scores are from PHP's own GHSA advisories. The 8.6.0 column is from php-src NEWS for PHP 8.6.0 (the advisories themselves list 8.2 to 8.5 only). Pre-releases such as 8.6.0RC7 are treated as AFFECTED. PHP 8.1 and earlier are end of life (security support for 8.1 ended on 31 Dec 2025; 8.2 remains in security support until 31 Dec 2026).

| CVE | GHSA | PHP severity (CVSS 4.0) | Affected (advisory ranges) | Fixed |
|---|---|---|---|---|
| CVE-2026-115560 | GHSA-658j-r8rw-q6mx | Critical 9.2 | 8.2.0 to 8.2.35, 8.3.0 to 8.3.36, 8.4.0 to 8.4.27, 8.5.0 to 8.5.12; 8.6 pre-releases | 8.2.36, 8.3.37, 8.4.28, 8.5.13, 8.6.0 |
| CVE-2026-126714 | GHSA-fm2m-fjf5-v3cp | Critical 9.2 | same 8.2 to 8.5 ranges; 8.6 pre-releases | same |
| CVE-2026-129182 | GHSA-2fjv-p558-g82m | Critical 9.2 | 8.5.0 to 8.5.12 only (engine); 8.6 pre-releases | 8.5.13, 8.6.0 |
| CVE-2026-129289 | GHSA-qc49-hpvq-g2w6 | Critical 9.2 | 8.2.0 to 8.2.35, 8.3.0 to 8.3.36, 8.4.0 to 8.4.27, 8.5.0 to 8.5.12 (sapi-fpm); 8.6 pre-releases | same as 115560 |
| CVE-2026-129474 | GHSA-8mjj-2r7p-4hg2 | Critical 9.2 | 8.5.0 to 8.5.12 only (engine); 8.6 pre-releases | 8.5.13, 8.6.0 |
| CVE-2026-129481 | GHSA-g3vh-838c-65v7 | Critical 9.2 | 8.3.0 to 8.3.36, 8.4.0 to 8.4.27, 8.5.0 to 8.5.12 (not 8.2); 8.6 pre-releases | 8.3.37, 8.4.28, 8.5.13, 8.6.0 |
| CVE-2026-129496 | GHSA-gr4f-wgx5-jpfv | Critical 9.2 | same 8.2 to 8.5 ranges as 115560; 8.6 pre-releases | same as 115560 |
| CVE-2026-129291 | GHSA-jm4m-qfqx-967m | High 8.8 | 8.2.7 to 8.2.35, 8.3.0 to 8.3.36, 8.4.0 to 8.4.27, 8.5.0 to 8.5.12 (sapi-fpm); 8.6 pre-releases | same as 115560 |
| CVE-2026-127960 | GHSA-mmf9-xm3v-hg2x | High 8.7 | 8.2.28 to 8.2.35, 8.3.18 to 8.3.36, 8.4.5 to 8.4.27, 8.5.0 to 8.5.12; 8.6 pre-releases | same as 115560 |
| CVE-2026-128064 | GHSA-f6gg-rchx-xw8j | High 8.2 | same 8.2 to 8.5 ranges as 115560; 8.6 pre-releases | same as 115560 |
| CVE-2026-128090 | GHSA-68fq-fh7h-f8gr | High 7.7 | same 8.2 to 8.5 ranges as 115560; 8.6 pre-releases | same as 115560 |
| CVE-2026-129538 | GHSA-5j3f-64r7-f564 | Medium 6.9 | same 8.2 to 8.5 ranges (sapi-cgi); 8.6 pre-releases | same as 115560 |
| CVE-2026-129438 | GHSA-mg3p-mxj9-g2mm | Medium 6.3 | 8.5.0 to 8.5.12 only (ext-uri); 8.6 pre-releases | 8.5.13, 8.6.0 |
| CVE-2026-129501 | GHSA-x8r7-mg3g-74hg | Medium 6.3 | 8.4.0 to 8.4.27 and 8.5.0 to 8.5.12 (ext-dom); 8.6 pre-releases | 8.4.28, 8.5.13, 8.6.0 |
| CVE-2026-129506 | GHSA-4646-p932-gw34 | Medium 6.3 | same 8.2 to 8.5 ranges as 115560; 8.6 pre-releases | same as 115560 |
| CVE-2026-15353 | GHSA-q23r-hr55-xmpg | Medium 6.3 | same 8.2 to 8.5 ranges as 115560; 8.6 pre-releases | same as 115560 |
| CVE-2026-129292 | GHSA-3mg3-cr28-46gc | Medium 5.3 | same 8.2 to 8.5 ranges (sapi-fpm); 8.6 pre-releases | same as 115560 |

## Conditions and interim settings (as PHP states them)

These are PHP's conditions and workarounds, not ours. The complete fix is to upgrade and restart workers.

- **CVE-2026-129289 (FPM request smuggling).** PHP can fail to discard unread bytes from an HTTP request body before reusing a persistent PHP-FPM or LSAPI connection. Exploitation requires a front end that enables persistent backend connections and an application path that opens `php://input` without reading it fully. Relevant configurations include nginx with `fastcgi_keep_conn on`, Apache `mod_proxy_fcgi` with `enablereuse=on`, HAProxy FastCGI applications that retain backend connections, and LSAPI. Standard nginx and Apache configurations that close the FastCGI connection after each request are not affected by the demonstrated PHP-FPM attack. For PHP-FPM, PHP describes unauthenticated execution of attacker-controlled PHP code as the worker. For LSAPI, PHP says the shared cleanup error can desynchronise the request stream, but "this advisory does not establish arbitrary code execution through LSAPI." Interim: disable backend connection reuse (leave `fastcgi_keep_conn` off, leave `enablereuse` off, close HAProxy FastCGI backends after each request).
- **CVE-2026-115560 (session serializer mismatch).** Session upload progress can write data in one serialization format and later read it in another. PHP: an application must set `session.serialize_handler` to `php_binary` or `php_serialize` in its configuration and then switch it to `php` at runtime with `ini_set()` before `session_start()`, and session upload progress must still be enabled. An application that never changes its serializer at runtime can still be affected if another process writes incompatible data into the same session store. A suitable object gadget chain in the application can turn this into code execution. The fix disables session upload progress by default and rejects runtime changes to session settings while the feature is enabled. An explicit enable still overrides the new default. Interim: set `session.upload_progress.enabled=0` administratively, before request input is processed (`ini_set()` is too late).
- **CVE-2026-126714 (partially overwritten session files).** Affects the default `files` session save handler. An interrupted write can leave a file containing parts of two sessions; a suitable gadget chain can lead to code execution. Interim: disable `session.upload_progress.enabled` if the feature is not needed (this removes that input path but does not fix applications that independently store attacker-controlled session data). A backend that replaces records atomically avoids this file-write defect.
- **CVE-2026-129496 (timezone cache use-after-free).** Requires a suitable startup diagnostic, PHP error logging to a file, and an early request diagnostic in a fresh worker. PHP has demonstrated code execution locally in FPM and Apache mod_php with additional assumptions. Interim: correct configuration errors that produce startup diagnostics and restart the master and all workers; sending PHP errors to syslog avoids the demonstrated trigger.
- **CVE-2026-129474 (magic method backtraces, PHP 8.5 and 8.6).** The demonstrated remote attack requires `fatal_error_backtraces=1` (enabled by default in PHP 8.5) and `zend.exception_ignore_args=0`. `php.ini-production` sets `zend.exception_ignore_args=1` and prevents this attack path. Interim: set `zend.exception_ignore_args=1` and restart workers; on PHP 8.5 and later, `fatal_error_backtraces=0` also prevents this path.
- **CVE-2026-129182 (last_fatal_error_backtrace, PHP 8.5 and 8.6).** Further scenarios after the CVE-2026-109619 fix in 8.5.12, in which a fatal diagnostic during later shutdown work repopulates the global. PHP: "RCE through these specific entry points has not been demonstrated." Interim: `fatal_error_backtraces=0` and restart workers.
- **CVE-2026-129481 (interrupted session shutdown).** An incomplete fix for CVE-2026-109619. It affects PHP 8.3 and later; PHP 8.2 does not contain the affected session filename field. PHP: code execution through this specific field has not been demonstrated. Interim: avoid fatal errors in session-cleanup callbacks; for PHP-FPM, `pm.max_requests=1` prevents the demonstrated second-request sequence, at a performance cost. Disabling session upload progress does not address this path.
- **CVE-2026-129291 (FPM epoll local privilege escalation, High 8.8).** Requires local code execution in an FPM worker, `catch_workers_output` enabled, the epoll backend, and the ability to manipulate worker lifetimes. The default outside official PHP-FPM Docker images is `catch_workers_output = no`. The delayed-cleanup path was introduced in PHP 8.2.7 (and 8.1.20). Interim: disable `catch_workers_output` in affected pools.
- **CVE-2026-128090 (PHAR OpenSSL signature bypass, High 7.7).** An attacker who can modify an OpenSSL-signed Phar, but not its trusted `.pubkey` file, can switch the signature type to a keyless hash. `phar.require_hash` alone does not authenticate keyless signatures.
- **CVE-2026-129538 (PHP-CGI PATH_INFO, Medium 6.9).** Affects `php-cgi` in CGI and FastCGI mode when `cgi.fix_pathinfo=1` (the default). PHP-FPM and PHP as an Apache module are not affected. Interim: `cgi.fix_pathinfo=0`, and check that routing still works.
- **CVE-2026-128064, CVE-2026-127960, CVE-2026-129292, CVE-2026-129438, CVE-2026-129501, CVE-2026-129506, CVE-2026-15353.** See the linked GHSA advisories for conditions. They are included in the checker and in the table above.

## Corrections to the original flag

1. **Seven Critical 9.2 CVEs, not four.** The flag correctly scored CVE-2026-129289, CVE-2026-115560, CVE-2026-126714 and CVE-2026-129496 at CVSS 4.0 9.2 Critical. PHP also scores CVE-2026-129474, CVE-2026-129182 and CVE-2026-129481 at 9.2 Critical. Use Critical only for those seven.
2. **GHSA IDs.** GHSA-qc49-hpvq-g2w6 is CVE-2026-129289, GHSA-fm2m-fjf5-v3cp is CVE-2026-126714, and GHSA-gr4f-wgx5-jpfv is CVE-2026-129496, as the flag said. CVE-2026-115560 is GHSA-658j-r8rw-q6mx (not named in the flag).
3. **CVE-2026-129289 and LSAPI.** The unauthenticated PHP code execution path is the PHP-FPM path. PHP does not establish arbitrary code execution through LSAPI; LSAPI is described as request-stream desynchronisation only.
4. **CVE-2026-129182** is PHP 8.5 only (8.5.0 to below 8.5.13), plus 8.6 pre-releases. It is a follow-up to the CVE-2026-109619 `last_fatal_error_backtrace` fix in 8.5.12. PHP says RCE through these specific entry points has not been demonstrated. Workaround: `fatal_error_backtraces=0`.
5. **CVE-2026-129481** is an incomplete fix for CVE-2026-109619, but it is not 8.5-only and it is not in 8.2. Advisory range: 8.3.0 to below 8.3.37, 8.4.0 to below 8.4.28, and 8.5.0 to below 8.5.13. PHP 8.2 does not contain the affected session filename field.
6. **CVE-2026-129474** is PHP 8.5 only (plus 8.6 pre-releases). The demonstrated path needs `zend.exception_ignore_args=0` and `fatal_error_backtraces=1`. `php.ini-production` sets `zend.exception_ignore_args=1`.
7. **CVE-2026-129291** is High, CVSS 4.0 8.8 (not only "High"). It needs `catch_workers_output` enabled (default is no, except official PHP-FPM Docker images) and starts at 8.2.7 on the 8.2 branch.
8. **CVE-2026-128090** is High, CVSS 4.0 7.7 (PHAR OpenSSL signature bypass via algorithm downgrade). The flag did not give a score.
9. **Eight further advisories in the same release** were not in the flag: CVE-2026-129538 (Medium 6.9, php-cgi only), CVE-2026-129438 (Medium 6.3, PHP 8.5 URI), CVE-2026-129501 (Medium 6.3, DOM, PHP 8.4 and 8.5), CVE-2026-129506 (Medium 6.3, SOAP UAF), CVE-2026-15353 (Medium 6.3, SOAP disclosure), CVE-2026-128064 (High 8.2, mixed-case HTTPS/FTPS URLs), CVE-2026-127960 (High 8.7, folded HTTP response headers, with higher lower-bounds: 8.2.28, 8.3.18, 8.4.5), and CVE-2026-129292 (Medium 5.3, FPM status XSS). The 8.5.13 and 8.6.0 notes also bump uriparser for CVE-2026-48841.
10. **8.6.0.** PHP's releases index dates 8.6.0 to 19 Nov 2026 and does not tag it as a security release. php-src NEWS for PHP 8.6.0 lists all 17 GHSAs plus the uriparser bump. This pack treats 8.6.0 and later 8.6 builds as FIXED, and 8.6 pre-releases as AFFECTED. The GHSA affected-version lists themselves do not include 8.6.
11. **Exploitation wording.** No exploitation reported by PHP or CISA as of 19 Nov 2026. None of the 19 Nov CVEs is in CISA KEV (2026.11.18). Do not use wording that denies exploitation outright. PHP2Shell remains in KEV; that is a separate, earlier pair of CVEs.

## Response

**Vendor fix (credited to PHP):** upgrade to 8.2.36, 8.3.37, 8.4.28, 8.5.13 or 8.6.0 for your branch, then restart every PHP worker (PHP-FPM, Apache mod_php, php-cgi, LiteSpeed/LSAPI, FrankenPHP and any other long-lived worker). The version that counts is the one the live worker reports after it comes back. Distribution packages may lag the php.net tarballs; follow your vendor's advisory as well.

**Vendor interim settings (credited to PHP), until patched:**

1. Set `session.upload_progress.enabled=0` administratively (php.ini, FPM pool or the web-server configuration that applies before request input is processed). Restart workers.
2. Disable FastCGI keep-alive or connection reuse: leave nginx `fastcgi_keep_conn` off, leave Apache `enablereuse` off, and close HAProxy FastCGI backends after each request.
3. Use `php.ini-production` defaults, including `zend.exception_ignore_args=1`. On PHP 8.5, set `fatal_error_backtraces=0` for CVE-2026-129182 and CVE-2026-129474.
4. For CVE-2026-129291, disable `catch_workers_output` in affected FPM pools.
5. For CVE-2026-129538 (php-cgi only), set `cgi.fix_pathinfo=0` and check routing.

**OUR ADVICE (CybaVerse, not from PHP or CISA): inventory, hunt and rotation**

1. Inventory every PHP runtime: hosting panels, WordPress and LAMP estates, containers, official PHP-FPM images, and cPanel or Plesk bundled PHP (these often lag). Run the checker with `--version-file` or `--php-i-file` and the relevant `--ini`, `--fpm-pool`, `--nginx-conf`, `--apache-conf` and `--haproxy-conf` paths. Use KQL Q7 for Defender inventory.
2. Patch internet-facing PHP-FPM behind nginx, Apache or HAProxy with connection reuse first, then other internet-facing PHP, then internal workers. Apply the interim settings where you cannot patch today.
3. After patching, restart every worker and rerun the checker against the version the worker reports.
4. Hunt (Q1 to Q7 and the Sigma rules) back to at least the release date, and further if your retention allows. Treat a shell under php-fpm as an incident.
5. If compromise is suspected: isolate the host, keep memory and logs, restore from known-good, and rotate application, database and other credentials the worker could read. Rebuild from a patched image rather than cleaning in place.
6. KEV due dates for the earlier PHP2Shell CVEs apply to US federal agencies only (BOD 26-04). They are not a reason to delay this upgrade.

## Hunts (all OUR PATTERN)

`kql/php-security-release-2026-11-19-hunting.kql`, for Microsoft Sentinel and Microsoft Defender advanced hunting. There are no published IOCs for these CVEs; this pack invents none. Each hunt is a lead to review, not proof.

| ID | Hunt | Table |
|---|---|---|
| Q1 | PHP or PHP-FPM spawning a shell or downloader | DeviceProcessEvents |
| Q2 | New or changed .php files under common web roots or upload paths | DeviceFileEvents |
| Q3 | php.ini / .user.ini / FPM pool changes, or command lines that set auto_prepend_file or allow_url_include | DeviceFileEvents, DeviceProcessEvents |
| Q4 | PHP-FPM or php-cgi crash or segfault | Syslog |
| Q5 | Successful IIS requests to PHP under upload or temp paths | W3CIISLog |
| Q6 | The same idea in CommonSecurityLog | CommonSecurityLog |
| Q7 | Defender TVM inventory of PHP versions versus the fixed builds | DeviceTvmSoftwareInventory |

Web-root and upload path lists are OUR ASSUMPTION [UNVERIFIED]. Adjust them to your estate. Defender hunts use `Timestamp`; Sentinel Log Analytics tables use `TimeGenerated`. The KQL in this pack has NOT been run against a live tenant.

## Sigma (all OUR PATTERN)

Seven Sigma rules in `sigma/`, with Kusto conversions in `sigma/converted/` for five pipelines (no pipeline, Microsoft XDR, Microsoft 365 Defender, Sentinel ASIM, Azure Monitor). `tests/run_all.sh` with `REGEN=1` rewrites the converted files; a later run without `REGEN` checks they still match. Some conversions are expected to fail on some pipelines; those failures are recorded in the converted files.

## Checker

Read-only. It never runs `php`, never touches the network, never writes a file and never prints secrets or file contents.

    bash scripts/check-php-security-release.sh --version-file php-v.txt --ini /etc/php/8.4/fpm/php.ini --fpm-pool /etc/php/8.4/fpm/php-fpm.conf --nginx-conf /etc/nginx/nginx.conf
    pwsh -NoProfile -File scripts/Check-PhpSecurityRelease.ps1 --php-i-file php-i.txt --apache-conf /etc/apache2/sites-enabled/000-default.conf --haproxy-conf /etc/haproxy/haproxy.cfg

- **Version.** Pass `--php-version`, a saved `php -v` file (`--version-file`), or a saved `php -i` file (`--php-i-file`). Distro suffixes such as `-1ubuntu0.1` are ignored. Pre-releases (RC, alpha, beta, dev) of a fixed-or-lower patch are AFFECTED. 8.7 and later, and unparseable text, are REVIEW. 8.1 and earlier are EOL.
- **Config.** `--ini`, `--fpm-pool`, `--nginx-conf`, `--apache-conf` and `--haproxy-conf` may be repeated. Includes are followed, with limits (256 files, 4 MiB, depth 16). The checker flags `fastcgi_keep_conn on`, `enablereuse=on`, HAProxy `fcgi-app` / `use-fcgi-app` / `proto fcgi`, `session.upload_progress.enabled`, `session.save_handler`, `session.serialize_handler`, `zend.exception_ignore_args`, `auto_prepend_file` (when set), `allow_url_include` (when on), `catch_workers_output` (when on), `cgi.fix_pathinfo` and `fatal_error_backtraces`.
- **Secrets.** Known password, token, Bearer, PEM and canary values are not printed. Unrecognised environment assignments in FPM pools are not printed.

| Exit | Meaning |
|---|---|
| 0 | FIXED: a supported branch (or 8.6.0+) is at or above the fixed build, and the config scan had no warnings |
| 1 | not used (reserved for unexpected runtime errors) |
| 2 | AFFECTED: a supported branch below the fixed build, or an 8.6 pre-release |
| 3 | REVIEW: version unknown or undocumented, sources disagree, or a file or include warning |
| 4 | EOL: PHP 8.1 or earlier |
| 5 | usage or a required file could not be read |

A fixed version with a missing include or an unreadable file is reported as REVIEW (exit 3), so an incomplete scan is not silently treated as clean. Config flags on a fixed build do not by themselves change the exit code; they are still printed so you can confirm interim settings and leftover risk.

## Caveats

- The KQL in this pack has NOT been run against a live tenant. Parsing against the modelled schemas proves syntax and column names only.
- KEV due dates apply to US federal agencies only (BOD 26-04, not the revoked BOD 22-01).
- Patch now regardless of KEV status.
- No exploitation reported by PHP or CISA as of 19 Nov 2026. Do not read that as a finding that exploitation has been ruled out.
- The checker is static. It does not evaluate runtime `ini_set()` changes, and it does not run PHP. A missing include is reported as REVIEW and may be harmless.
- Credit for the underlying reports goes to security researchers. This pack does not name individuals or firms listed in the advisories or in PHP NEWS.

## Credits

Vendor documentation is credited to PHP (the PHP Group / php-src advisories and changelog). Hunting logic, Sigma rules and the checker are ours (CybaVerse threat hunt). Findings described in the advisories are credited to security researchers. Research is credited to security researchers only.

## Sources

- PHP 8 changelog (8.5.13, 8.4.28, 8.3.37, 8.2.36): https://www.php.net/ChangeLog-8.php
- PHP news archive, 19 Nov 2026 releases and the 18 Nov pre-announcement: https://www.php.net/archive/2026.php
- PHP supported versions: https://www.php.net/supported-versions.php
- PHP releases index (8.6.0 dated 19 Nov 2026, not tagged security; 8.5.13, 8.4.28, 8.3.37 and 8.2.36 tagged security): https://www.php.net/releases/index.php
- php-src NEWS for PHP 8.6.0 (tag php-8.6.0)
- PHP GHSA advisories (cite by ID): GHSA-qc49-hpvq-g2w6, GHSA-658j-r8rw-q6mx, GHSA-fm2m-fjf5-v3cp, GHSA-gr4f-wgx5-jpfv, GHSA-8mjj-2r7p-4hg2, GHSA-2fjv-p558-g82m, GHSA-g3vh-838c-65v7, GHSA-jm4m-qfqx-967m, GHSA-68fq-fh7h-f8gr, GHSA-5j3f-64r7-f564, GHSA-mg3p-mxj9-g2mm, GHSA-x8r7-mg3g-74hg, GHSA-4646-p932-gw34, GHSA-q23r-hr55-xmpg, GHSA-f6gg-rchx-xw8j, GHSA-mmf9-xm3v-hg2x, GHSA-3mg3-cr28-46gc, at https://github.com/php/php-src/security/advisories
- CISA KEV catalogue 2026.11.18: https://www.cisa.gov/known-exploited-vulnerabilities-catalog and https://www.cisa.gov/sites/default/files/feeds/known_exploited_vulnerabilities.json
- CISA BOD 26-04: https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk

## Files

- `README.md` (this file)
- `kql/php-security-release-2026-11-19-hunting.kql`
- `sigma/*.yml` and `sigma/converted/`
- `scripts/check-php-security-release.sh` and `scripts/Check-PhpSecurityRelease.ps1`
- `tests/` (cases, fixtures, gates, KQL parse, Sigma conversion, Pester and bash tests)
