# CVE-2026-128017: FrankenPHP before 1.13.4 Double Free in Worker Mode via Non-Form POST


- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Nov 2026
- **Updated:** 13 Nov 2026
- **Also known as:** GHSA-cwwm-gfxf-5342, GHSA-h764-4wh7-m7j2

## What is CVE-2026-128017?

CVE-2026-128017 is a medium-severity vulnerability in frankenphp, published on 13 Nov 2026. 

### Official description

FrankenPHP before 1.13.4 contains a double free vulnerability in worker mode that frees SG(request_info).content_type_dup twice when a worker script ends its loop after a non-form POST request. Unauthenticated attackers can send repeated JSON POST requests until the worker loop ends, aborting the whole process when USE_ZEND_ALLOC=0 is set.

Weakness: CWE-415 (Double Free)

## Which versions are affected by CVE-2026-128017?

1 open source package ship an affected version, including github.com/dunglas/frankenphp.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `github.com/dunglas/frankenphp` | Go | `pkg:golang/github.com/dunglas/frankenphp` | All versions | 1.13.4 |

## How do I fix CVE-2026-128017?

Upgrade github.com/dunglas/frankenphp to 1.13.4 or later.

## Is CVE-2026-128017 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-128017 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-128017 and fix it if it is affected.

What it is: CVE-2026-128017 is a medium-severity vulnerability in frankenphp, published on 13 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-128017 exists.

Affected packages and fixed versions:
- github.com/dunglas/frankenphp (Go): affected all versions; fixed in 1.13.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-128017/ (Markdown: https://insights.sbomify.com/CVE-2026-128017/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-128017
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-128017
- OSV: https://osv.dev/vulnerability/CVE-2026-128017

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-128017/
Summaries are generated and may contain mistakes; the official description above is the record.
