Skip to main content
Menu
CVEs

PHP truncated RFC 3986 URI serialization on oversized input

CVE-2026-129438EUVD-2026-130190Published November 19, 2026, updated

6.3MediumCNA
Exploited
No known exploitation
Fix
Fixed in 8.5.13
Who is exposed
Not reported

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

Original 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

Upgrade to a fixed version: 8.5.13.

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-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"}.

Affected versions

cve.now Index

40Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure17/25No login or user action needed per the CVSS vector, reachable over the network without a login · Unknown: No advisory context yet
  • Reach17/20Affects PHP (a widely deployed server, runtime, framework or database)
  • Severity6.3/10CVSS 6.3
  • No patch0/5No signal

What would change the score

  • Would score about 85 if added to CISA KEV
  • Would score about 80 if CISA's SSVC rates exploitation active
  • Would score about 45 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

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

  4. Record last updated

Evidence 3

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
AdvisoryGitHub · php/php-src · Advisory GHSA-mg3p-mxj9-g2mm
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-129438
RecordNVD · CVE-2026-129438

Questions about CVE-2026-129438

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: cve.now feed data

Which versions are affected by CVE-2026-129438?

PHP: from 8.5.0 before 8.5.13.

Source: cve.now feed data

How do I fix CVE-2026-129438?

Upgrade to a fixed version: 8.5.13.

Source: cve.now feed data

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