Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2025-67899: uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input…

LowCVSS 2.9 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 11/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 0.14% (FIRST EPSS).
  • Someone with local access to the system can trigger it. No account or password is required. No user action is required. Special conditions such as timing or configuration are required.
  • Fixed version: uriparser (Debian:14) 1.0.1+dfsg-1; uriparser (openSUSE:Leap 15.6) 0.8.5-150000.3.11.1; uriparser (openSUSE:Leap 16.0) 0.9.8-160000.4.1.

Low priority for now. Upgrade to uriparser (Debian:14) 1.0.1+dfsg-1; uriparser (openSUSE:Leap 15.6) 0.8.5-150000.3.11.1; uriparser (openSUSE:Leap 16.0) 0.9.8-160000.4.1 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

uriparser through 0.9.9 allows unbounded recursion and stack consumption, as demonstrated by ParseMustBeSegmentNzNc with large input containing many commas.

Published
Dec 14, 2025
Updated
Oct 14, 2026
EPSS
0.1% · 3th percentile

Report tools

JSON

Action score

11

Monitor

Low priority for now.

CVSS
11 / 40 · 2.9 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 0.1%

CISA SSVC decision

Exploitation
none
Automatable
no
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · mitre
2.9
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2025-67899

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

—

Versions reported by the vendor

Affected version ranges reported by the assigning authority (mitre). Independent of NVD's CPE analysis and usually ahead of it.

  • uriparser project uriparser

    • up to and including 0.9.9affected · semver

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Debian:12uriparserfrom 0—
Debian:14uriparserbefore 1.0.1+dfsg-11.0.1+dfsg-1
openSUSE:Leap 15.6uriparserbefore 0.8.5-150000.3.11.10.8.5-150000.3.11.1
openSUSE:Leap 16.0uriparserbefore 0.9.8-160000.4.10.9.8-160000.4.1
openSUSE:Tumbleweedphp8before 8.5.5-1.18.5.5-1.1
openSUSE:Tumbleweeduriparserbefore 1.0.0-1.11.0.0-1.1
Red Hat:hummingbird:1mingw32-uriparserbefore 0:1.0.0-2.1.hum10:1.0.0-2.1.hum1
Red Hat:hummingbird:1mingw64-uriparserbefore 0:1.0.0-2.1.hum10:1.0.0-2.1.hum1
Red Hat:hummingbird:1uriparserbefore 0:1.0.0-2.1.hum10:1.0.0-2.1.hum1
Red Hat:hummingbird:1uriparser-develbefore 0:1.0.0-2.1.hum10:1.0.0-2.1.hum1
Red Hat:hummingbird:1uriparser-docbefore 0:1.0.0-2.1.hum10:1.0.0-2.1.hum1
SUSE:Linux Enterprise Module for Package Hub 15 SP7uriparserbefore 0.8.5-150000.3.11.10.8.5-150000.3.11.1
SUSE:Linux Enterprise Server 16.0uriparserbefore 0.9.8-160000.4.10.9.8-160000.4.1

Other highest-scoring records for the same primary product.

  • CVE-2018-20721URI_FUNC() in UriParse.c in uriparser before 0.9.1 has an out-of-bounds read (in uriParse*Ex* functions) for an incomplete URI with an IPv6…
    40Plan
  • CVE-2018-19199An issue was discovered in uriparser before 0.9.0.
    40Plan
  • CVE-2018-19198An issue was discovered in uriparser before 0.9.0.
    40Plan

Published before and after this one in the same product

  • ← EarlierCVE-2024-34402May 2, 2024 · An issue was discovered in uriparser through 0.9.7.
    34Monitor
  • ← EarlierCVE-2024-34403May 2, 2024 · An issue was discovered in uriparser through 0.9.7.
    23Monitor
  • Later →CVE-2026-42371Apr 27, 2026 · uriparser before 1.0.1 has numeric truncation in text range comparison, if an application accepts URIs with a length in gigabytes.
    20Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
debian:uriparser1.0.1+dfsg-1 · Debian:14Package registry (OSV)
opensuse:php88.5.5-1.1 · openSUSE:TumbleweedPackage registry (OSV)
opensuse:uriparser0.8.5-150000.3.11.1 · openSUSE:Leap 15.6Package registry (OSV)
red hat:mingw32-uriparser0:1.0.0-2.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:mingw64-uriparser0:1.0.0-2.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:uriparser0:1.0.0-2.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:uriparser-devel0:1.0.0-2.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
red hat:uriparser-doc0:1.0.0-2.1.hum1 · Red Hat:hummingbird:1Package registry (OSV)
suse:uriparser0.8.5-150000.3.11.1 · SUSE:Linux Enterprise Module for Package Hub 15 SP7Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Someone with local access to the system can trigger it.
  • No account or password is required.
  • No user action is required.
  • Special conditions such as timing or configuration are required.

If successful

Confidentiality
none
Integrity
none
Availability
low · the service can be disrupted
Attack vector
Local
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
Low

CVSS vector

CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

References

Show all references (2 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records