CVE-2026-129438: Incorrect RFC 3986 URI serialization for oversized input

Published Nov 19, 2026
·
Updated

Fixed (Incorrect RFC 3986 URI serialization for oversized input). (CVE-2026-129438)

Other sources

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. parseurl() and Uri\WhatWg\Url are not affected.

This issue affects PHP versions 8.5. before 8.5.13.

— MITRE

PHP's RFC 3986 URI implementation can return an incorrect string when a very large URI is converted back to text. An application that accepts attacker-controlled URI data and has enough memory to process it may receive a truncated or invalid URI instead of an error. Processing these inputs can also exhaust memory or terminate the PHP process. This affects the Uri\Rfc3986\Uri class introduced in PHP 8.5.0. The legacy parseurl() function and the separate Uri\WhatWg\Url implementation are not affected by this issue.

— OSV

Affected Software

9 affected componentsFixes available
PHP PHP<8.5.13
8.5.13
ubuntu/php5*
ubuntu/php7.0*
ubuntu/php7.2*
ubuntu/php7.4*
ubuntu/php8.1*
ubuntu/php8.3*
ubuntu/php8.5*
ubuntu/php8.5*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 8.5.13
  2. Upgrade

    Upgrade PHP to a version that resolves this vulnerability.

    Fixed in 8.5.13

Event History

Nov 19, 2026
CVE Published
via PHP·12:00 AM
Data Sourced
via PHP·12:00 AM
DescriptionAffected Software
Data Sourced
via OSV·02:00 PM
DescriptionSeverityAffected Software
CVE Published
via MITRE·02:44 PM
Data Sourced
via MITRE·02:44 PM
DescriptionWeakness
Data Sourced
via NVD·03:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which applications are realistically exposed to this issue?

Applications using the Uri\Rfc3986\Uri class and serializing attacker-controlled URIs are exposed when URI text can approach approximately 2 GiB and the application has sufficient memory to process it. The application must also rely on the serialized result for validation, routing, or other security-relevant decisions.

2

Does this affect PHP URI parsing generally?

No. parse_url() and Uri\WhatWg\Url are not affected; the issue is specific to serialization operations on Uri\Rfc3986\Uri, including toString() and toRawString().

3

What can happen if exploitation is successful?

Serialization can return a truncated or invalid URI instead of reporting an error, which can lead to incorrect validation or routing decisions if the result is trusted. Processing the oversized input can also exhaust memory or terminate the PHP process.

4

Which PHP releases are known to be affected?

PHP 8.5 releases before 8.5.13 are affected. The affected functionality is the RFC 3986 URI implementation introduced in PHP 8.5.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203