CVE-2026-42371: uriparser 1.0.1 fixes CVE-2026-42371 (integer overflow)
Published Apr 27, 2026
·Updated
Fixed CVE-2026-42371 (uriparser before 1.0.1 has numeric truncation in text range comparison). (CVE-2026-42371)
Other sources
uriparser before 1.0.1 has numeric truncation in text range comparison, if an application accepts URIs with a length in gigabytes.
— NVD
Affected Software
3 affected componentsFixes available
uriparser uriparser<1.0.1
PHP PHP<8.5.6
8.5.6
Uriparser Project Uriparser<1.0.1
Remediation
Patch Available
Event History
Apr 27, 2026
CVE Published
via MITRE·05:50 AM
Data Sourced
via MITRE·05:50 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:16 AM
RemedyAffected Software
May 7, 2026
Data Sourced
via PHP·12:00 AM
DescriptionAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2026-42371?
CVE-2026-42371 has a medium severity due to numeric truncation vulnerabilities when handling large URIs.
2
How do I fix CVE-2026-42371?
To fix CVE-2026-42371, update uriparser to version 1.0.1 or later.
3
What software is affected by CVE-2026-42371?
CVE-2026-42371 affects versions of uriparser prior to 1.0.1.
4
What type of vulnerability is CVE-2026-42371?
CVE-2026-42371 is classified as a numeric truncation vulnerability.
5
What impact does CVE-2026-42371 have on applications?
CVE-2026-42371 may lead to unexpected behavior in applications that process large URIs.