{"vuln_id":"CVE-2026-129438","aliases":["GHSA-mg3p-mxj9-g2mm"],"description":"Incorrect RFC 3986 URI serialization for oversized input","published_at":"2026-11-19T14:06:16Z","modified_at":"2026-11-19T21:45:03.380000Z","first_seen_at":"2026-11-21T19:15:07.663716Z","severity":"medium","severity_source":"nvd","cvss_score":6.3,"cvss_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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","cwe":["CWE-190","CWE-252"],"vendor":null,"product":null,"kev":{"is_kev":false,"date_added":null,"due_date":null,"ransomware":false},"epss":0.00562,"epss_percentile":0.4759,"nvd_status":"Awaiting Analysis","enriched_at":null,"links":{"nvd":"https://nvd.nist.gov/vuln/detail/CVE-2026-129438"},"matched_alias":null,"items":[{"id":654,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"[SECURITY RELEASE] php/php-src php-8.5.13 - PHP 8.5.13","summary":"Fixes advisories: GHSA-8mjj-2r7p-4hg2, GHSA-2fjv-p558-g82m, GHSA-mg3p-mxj9-g2mm, GHSA-g3vh-838c-65v7, GHSA-x8r7-mg3g-74hg, GHSA-jm4m-qfqx-967m, GHSA-mmf9-xm3v-hg2x, GHSA-f6gg-rchx-xw8j, GHSA-658j-r8rw-q6mx, GHSA-gr4f-wgx5-jpfv, GHSA-fm2m-fjf5-v3cp, GHSA-4646-p932-gw34, GHSA-qc49-hpvq-g2w6, GHSA-3mg3-cr28-46gc, GHSA-5j3f-64r7-f564, GHSA-68fq-fh7h-f8gr, GHSA-q23r-hr55-xmpg\n\n(no release notes)","url":"https://github.com/php/php-src/releases/tag/php-8.5.13","published_at":"2026-11-21T02:00:50Z","updated_at":null,"fetched_at":"2026-11-21T19:15:07.553386Z","severity":"critical","cvss_score":9.2,"epss":0.71117,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"php-src","vuln_id":"CVE-2026-129474","vuln_ids":["CVE-2025-1217","CVE-2026-109619","CVE-2026-115560","CVE-2026-126714","CVE-2026-127960","CVE-2026-128064","CVE-2026-128090","CVE-2026-129182","CVE-2026-129289","CVE-2026-129291","CVE-2026-129292","CVE-2026-129438","CVE-2026-129474","CVE-2026-129481","CVE-2026-129496","CVE-2026-129501","CVE-2026-129506","CVE-2026-129538","CVE-2026-15353","CVE-2026-6735","CVE-2026-91765","GHSA-2FJV-P558-G82M","GHSA-3MG3-CR28-46GC","GHSA-4646-P932-GW34","GHSA-5J3F-64R7-F564","GHSA-658J-R8RW-Q6MX","GHSA-68FQ-FH7H-F8GR","GHSA-6WMF-4RV5-P3RP","GHSA-7QG2-V9FJ-4MWV","GHSA-8MJJ-2R7P-4HG2","GHSA-F6GG-RCHX-XW8J","GHSA-FM2M-FJF5-V3CP","GHSA-G3VH-838C-65V7","GHSA-GR4F-WGX5-JPFV","GHSA-JM4M-QFQX-967M","GHSA-MG3P-MXJ9-G2MM","GHSA-MMF9-XM3V-HG2X","GHSA-Q23R-HR55-XMPG","GHSA-Q8FM-P8FX-H6R6","GHSA-QC49-HPVQ-G2W6","GHSA-RGRP-MWPX-F6RM","GHSA-V8XR-GPVJ-CX9G","GHSA-X8R7-MG3G-74HG"],"tags":["release","repo:php/php-src","security"],"cluster_id":444,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/654","html":"https://vulnwatch.ve1ve2.com/item/654"}},{"id":8610,"source":{"id":"nvd","name":"NVD CVE API 2.0"},"title":"CVE-2026-129438: 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…","summary":"Incorrect RFC 3986 URI serialization for oversized input.\n\nThe 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.\n\nThis issue affects PHP versions 8.5.* before 8.5.13.\n\nReferences:\nhttps://github.com/php/php-src/security/advisories/GHSA-mg3p-mxj9-g2mm","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-129438","published_at":"2026-11-19T15:17:27.973000Z","updated_at":"2026-11-19T21:45:03.380000Z","fetched_at":"2026-11-21T19:15:31.484337Z","severity":"medium","cvss_score":6.3,"epss":0.00562,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":null,"product":null,"vuln_id":"CVE-2026-129438","vuln_ids":["CVE-2026-129438","GHSA-MG3P-MXJ9-G2MM"],"tags":["CWE-190","CWE-252"],"cluster_id":449,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/8610","html":"https://vulnwatch.ve1ve2.com/item/8610"}},{"id":1216,"source":{"id":"redhat","name":"Red Hat Security Data API"},"title":"CVE-2026-129438: php: Incorrect RFC 3986 URI serialization for oversized input","summary":"php: Incorrect RFC 3986 URI serialization for oversized input","url":"https://access.redhat.com/security/cve/cve-2026-129438","published_at":"2026-11-19T14:42:25Z","updated_at":null,"fetched_at":"2026-11-21T19:15:08.894056Z","severity":"medium","cvss_score":6.3,"epss":0.00562,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"redhat","product":null,"vuln_id":"CVE-2026-129438","vuln_ids":["CVE-2026-129438","GHSA-MG3P-MXJ9-G2MM"],"tags":["redhat"],"cluster_id":449,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/1216","html":"https://vulnwatch.ve1ve2.com/item/1216"}},{"id":625,"source":{"id":"gh-php-src","name":"PHP releases (GitHub php/php-src tags)"},"title":"GHSA-mg3p-mxj9-g2mm / CVE-2026-129438: Incorrect RFC 3986 URI serialization for oversized input","summary":"Incorrect RFC 3986 URI serialization for oversized input\n\n### Summary\r\n\r\nPHP'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.\r\n\r\nThis affects the `Uri\\Rfc3986\\Uri` class introduced in PHP 8.5.0. The legacy `parse_url()` function and the separate `Uri\\WhatWg\\Url` implementation are not affected by this issue.\r\n\r\n### Details\r\n\r\nPHP uses the uriparser library to convert an RFC 3986 URI back to text. The vulnerable implementation does not correctly handle the library's output-size limit or errors returned while calculating or writing the result.\r\n\r\nFor a URI whose string representation is exactly 2,147,483,647 bytes, PHP overflows the size calculation when it reserves space for the terminating byte. The conversion then fails, but PHP can still return the allocated string as a successful result. With longer URIs, PHP can use an incomplete length calculation and return only part of the URI.\r\n\r\nTesting on a normal, non-debug PHP build confirmed that `toString()` and `toRawString()` could return a 2,147,483,647-byte string containing zeroes. A URI one byte longer returned only its `a://b/` prefix. Other operations that convert an RFC 3986 URI to text can reach the same implementation.\r\n\r\nThe defect is in PHP's handling of uriparser's size limit and return values. Updating uriparser alone does not correct it. Correct handling requires PHP to reject a representation that cannot fit the library's supported output size and report a conversion error instead of returning an invalid string.\r\n\r\n### Impact\r\n\r\nExploitation requires an application to pass attacker-controlled URI data large enough to reach the approximately 2 GiB boundary to an affected operation. The PHP process must also have enough memory to construct and process the URI. Normal application-level URI length limits prevent the demonstrated inputs from reaching this condition.\r\n\r\nAn application that trusts the resulting string may make an incorrect comparison, validation or routing decision, or store an incomplete URI. The large allocations can also exhaust the request's memory allowance. In the tested development build, exceeding the soft memory limit produced a memory-exhaustion error; exceeding the hard limit immediately terminated the PHP process. This can temporarily reduce service capacity.\r\n\r\nThe allocations remain subject to PHP's memory-limit checks. A memory-limit bypass was not observed. The tests also did not establish disclosure of data from other requests: the large result allocation used fresh operating-system memory and contained zeroes. Arbitrary code execution and broader confidentiality or integrity impact have not been demonstrated.\r\n\r\n### Affected versions\r\n\r\nThe affected code was introduced in PHP 8.5.0 together with the `Uri\\Rfc3986\\Uri` class. P\n\nAffected packages: php:ext-uri\nPatched: ext-uri 8.5.13","url":"https://github.com/php/php-src/security/advisories/GHSA-mg3p-mxj9-g2mm","published_at":"2026-11-19T14:06:16Z","updated_at":"2026-11-19T19:01:06Z","fetched_at":"2026-11-21T19:15:07.553364Z","severity":"medium","cvss_score":6.3,"epss":0.00562,"is_kev":false,"has_exploit":false,"kev_due_date":null,"vendor":"php","product":"ext-uri","vuln_id":"CVE-2026-129438","vuln_ids":["CVE-2026-129438","GHSA-MG3P-MXJ9-G2MM"],"tags":["repo-advisory","php","CWE-190","CWE-252","security","repo:php/php-src"],"cluster_id":448,"links":{"self":"https://vulnwatch.ve1ve2.com/api/v1/items/625","html":"https://vulnwatch.ve1ve2.com/item/625"}}]}