CVE
FrankenPHP denial of service via nil type assertion in goArray
Only affects FrankenPHP before 1.13.0 when crafted JSON reaches frankenphp_log() or a worker callback. Fixed in 1.13.0.
Written by a model from the sources below. Verify against them.
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
- No known exploitation
- Fix
- Fixed in 1.13.0
- Who is exposed
- Default setups
Do first: Check every install: default setups are affected.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.45% · 39th percentile
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 47/100
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Default setups
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
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.
Who should check
Teams running FrankenPHP before 1.13.0 (Go) that pass decoded JSON to frankenphp_log() or worker callbacks, including Go extensions converting PHP arrays.
“Affecting frankenphp >= 0, < 1.13.0”
cve.now Index
- Exploitation0/40No signal
- Exposure22/25Default setups, reachable over the network without a login
- Reach17/20Affects PHP (a widely deployed server, runtime, framework or database)
- Severity8.2/10CVSS 8.2
- No patch0/5No signal
What would change the score
- Would score about 87 if added to CISA KEV
- Would score about 82 if CISA's SSVC rates exploitation active
What to do
Check every install: default setups are affected.
Upgrade to a fixed version: 1.13.0.
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-128024 (FrankenPHP before 1.13.0 Denial of Service via goArray Nil Type Assertion), 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-128024 (entry last updated 2026-11-13):
Affected:
- Go package github.com/dunglas/frankenphp: fixed in 1.13.0
Fixed versions: 1.13.0.
Conditions (all must be true for the bug to be hit):
- FrankenPHP versions before 1.13.0 (source: https://www.vulncheck.com/advisories/frankenphp-before-1.13.0-denial-of-service-via-goarray-nil-type-assertion)
- The array must be a real hash table, not a packed array (source: https://github.com/php/frankenphp/security/advisories/GHSA-4prg-hv4r-g6mv)
- The array must contain an integer-keyed element whose value is null (source: https://github.com/php/frankenphp/security/advisories/GHSA-4prg-hv4r-g6mv)
- The crafted JSON must be passed to frankenphp_log() or returned from a worker callback (source: https://www.vulncheck.com/advisories/frankenphp-before-1.13.0-denial-of-service-via-goarray-nil-type-assertion)
Setup: the bug is reachable in a default setup; no special feature or setting is needed.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-128024 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-128024 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-4prg-hv4r-g6mv
- https://www.vulncheck.com/advisories/frankenphp-before-1.13.0-denial-of-service-via-goarray-nil-type-assertion
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-128024
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-128024"}.Public exploit activity
- EPSS: 0.45%
- Posted on X by cve.now Nov 13
Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
fixed in 1.13.0
Fixed in v1.13.0 (released Oct 4, 2026, 40 days before disclosure).
The latest release, v1.13.5, is not affected.
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-128024
Is CVE-2026-128024 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. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A crafted JSON array can make FrankenPHP dereference a null value under a type assertion, which aborts the whole server process. This takes down every virtual host and all in-flight requests at once.Source: vulncheck.com, github.com
Which versions are affected by CVE-2026-128024?
github.com/dunglas/frankenphp (Go): before 1.13.0.Source: cve.now feed data
Am I affected, and how do I check?
FrankenPHP versions before 1.13.0 are affected, but only when the array is a real hash table rather than a packed array and contains an integer-keyed element whose value is null. The crafted JSON must also be passed to frankenphp_log() or returned from a worker callback. To check your version, run frankenphp version or inspect the version used by your build.Source: vulncheck.com, github.com
How do I fix CVE-2026-128024?
Upgrade FrankenPHP to version 1.13.0 or later, which is the fixed version listed for this vulnerability.Source: vulncheck.com, github.com