# CVE-2026-128024: FrankenPHP before 1.13.0 Denial of Service via goArray Nil Type Assertion


- **Severity:** High 8.2 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/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-4prg-hv4r-g6mv, GHSA-hm4x-45c3-hm42

## What is CVE-2026-128024?

CVE-2026-128024 is a high-severity vulnerability in frankenphp, published on 13 Nov 2026. 

### Official description

FrankenPHP before 1.13.0 contains a denial of service vulnerability in goArray() that allows remote attackers to abort the server process via arrays with null integer-keyed elements. Attackers can send crafted JSON passed to frankenphp_log() or returned from worker callbacks, triggering an unrecovered cgo panic that terminates every vhost and in-flight request.

Weakness: CWE-248 (Uncaught Exception)

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

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.0 |

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

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

## Is CVE-2026-128024 being exploited?

There is no known exploitation of CVE-2026-128024 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-128024 is a high-severity vulnerability in frankenphp, published on 13 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-128024 in the wild and no public exploit code.

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

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-128024/ (Markdown: https://insights.sbomify.com/CVE-2026-128024/index.md)
```

## Sources

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

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