Skip to main content
Menu
CVEs

FrankenPHP out-of-bounds write in bundled Brotli decoder

Affects FrankenPHP standalone static binaries 1.8.0 to 1.13.1 when an application passes attacker-controlled data to brotli_uncompress_add(). Fixed in 1.13.2.

CVE-2026-128014GHSA-P746-JJ3F-94P8EUVD-2026-125088GHSA-G5QV-P6X9-9WPVPublished November 13, 2026, updated Needs attention

9.2CriticalCNA
Exploited
Public exploit code, no confirmed attacks
Fix
Fixed in 1.13.2
Who is exposed
Not reported

Summary

FrankenPHP's standalone static binaries bundle a Brotli decoder with an out-of-bounds write, which a remote attacker with no login can trigger by sending crafted data to an application that passes it to brotli_uncompress_add(), crashing the whole FrankenPHP process. The write could also allow memory disclosure or code execution (not demonstrated against FrankenPHP), and the bug needs a non-default setup in which the application feeds attacker-controlled data to that function.

Written by a model

Original description

FrankenPHP standalone static binaries 1.8.0 before 1.13.2 bundle the PHP brotli extension statically linked with Brotli 1.2.0, whose decoder contains an out-of-bounds write (CVE-2026-111497). Unauthenticated remote attackers can send crafted data to applications that pass it to brotli_uncompress_add() to crash the entire FrankenPHP process, and possibly cause memory disclosure or code execution.

Who should check

Teams running FrankenPHP standalone static binaries 1.8.0 to 1.13.1 whose PHP apps pass untrusted data (uploads, request bodies, queue messages) to brotli_uncompress_add().

Not fixed by: Loading the extension alone is not exploitable; Caddy's br response encoding is not affected.

“The standalone static binaries of FrankenPHP 1.8.0 to 1.13.1 include the PHP brotli extension, statically linked with Brotli 1.2.0”

github.com

What to do

Upgrade to a fixed version: 1.13.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-128014 (FrankenPHP 1.8.0 before 1.13.2 Out-of-Bounds Write via Bundled Brotli Decoder), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-128014 (entry last updated 2026-11-17):
Affected:
- Go package github.com/dunglas/frankenphp: from 1.8.0, fixed in 1.13.2
Fixed versions: 1.13.2.
Conditions (all must be true for the bug to be hit):
- Standalone static binary of FrankenPHP 1.8.0 to 1.13.1, which bundles the PHP brotli extension linked with Brotli 1.2.0 (source: https://github.com/php/frankenphp/security/advisories/GHSA-p746-jj3f-94p8)
- Application passes attacker-controlled data to brotli_uncompress_add() (source: https://github.com/php/frankenphp/security/advisories/GHSA-p746-jj3f-94p8)
- Merely loading the extension is not enough to be exploitable (source: https://github.com/php/frankenphp/security/advisories/GHSA-p746-jj3f-94p8)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-128014 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128014 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (Go): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/php/frankenphp/security/advisories/GHSA-p746-jj3f-94p8
- https://www.vulncheck.com/advisories/frankenphp-1.8.0-before-1.13.2-out-of-bounds-write-via-bundled-brotli-decoder
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-128014
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-128014"}.

Affected versions

cve.now Index

66of 100 · methodology v3
  • Exploitation22/40Public exploit on Exploit-DB or GitHub
  • Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
  • Reach17/20Affects PHP (a widely deployed server, runtime, framework or database)
  • Severity10/10CVSS 9.2, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 89 if added to CISA KEV
  • Would score about 84 if CISA's SSVC rates exploitation active
  • Would score about 71 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now1 day
  4. Exploit code on GitHub

    googlesky/CVE-2026-128014

    3 days
  5. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  6. Record last updated

Public exploit activity

10Posted on X by cve.now100%0Nov 13Nov 22
  • GitHub PoC repos: 1
  • EPSS: 0.86%
  • Posted on X by cve.now Nov 13

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Evidence 5

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · php/frankenphp · Advisory GHSA-p746-jj3f-94p8
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-128014
RecordNVD · CVE-2026-128014
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
ExploitGitHub · googlesky/CVE-2026-128014 · Repository
Other links 1
Linkvulncheck.com · advisories/frankenphp-1.8.0-before-1.13.2-out-of-bounds-write-via-bundled-brotli-decoder

Questions about CVE-2026-128014

Is CVE-2026-128014 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).

Source: cve.now feed data

What does this mean?

The Brotli decoder bundled in FrankenPHP's standalone binaries can write outside its memory bounds when it handles crafted data. This can crash the whole FrankenPHP process. It may also allow memory disclosure or code execution, though that was not demonstrated against FrankenPHP.

Source: github.com

Which versions are affected by CVE-2026-128014?

github.com/dunglas/frankenphp (Go): from 1.8.0 before 1.13.2.

Source: cve.now feed data

Am I affected, and how do I check?

Standalone static binaries of FrankenPHP 1.8.0 to 1.13.1 are in range. They include the PHP brotli extension, statically linked with Brotli 1.2.0. The issue needs an application that passes attacker-controlled data to brotli_uncompress_add(); loading the extension alone is not exploitable. To check, look at the version of the FrankenPHP binary in use and whether the application code calls that function.

Source: github.com

How do I fix CVE-2026-128014?

Upgrade FrankenPHP to 1.13.2 or later. The facts name no workaround.

Source: github.com

No corrections so far. Something wrong on this page? Report an error.