CVE-2025-67899

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

Published: 2025-12-14 Last update: 2026-04-15 Assigner: [email protected] Source: [email protected]
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-67899 is rated Low Risk (12.2/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.01%). Low composite risk—no urgent action required; patch on your normal maintenance cycle and revisit priority if CVSS or EPSS increases.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-67899

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-12-15 — 0.01% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-67899

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
2.9 3.1 LOW
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
 1.4 1.4 [email protected]

Weakness enumeration for CVE-2025-67899

OS Trackers for CVE-2025-67899

vendor priority summary link
alpine low CVE-2025-67899: 1 source package rows (uriparser); 9 state rows across 3 repos (3.22-community, 3.23-community, edge-community); fixed 0, open 9. https://security.alpinelinux.org/vuln/CVE-2025-67899
debian not yet assigned CVE-2025-67899 not yet assigned priority: Debian including 1 source packages (uriparser), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): open 5. https://security-tracker.debian.org/tracker/CVE-2025-67899
redhat low — https://access.redhat.com/security/cve/CVE-2025-67899
suse medium CVE-2025-67899 severity moderate: SUSE including 8 source package names (liburiparser1-0.8.5-150000.3.11.1, liburiparser1-1.0.0-1.1, …), 11 product×package rows across 3 product lines (SUSE Linux Enterprise Module for Package Hub 15 SP7, openSUSE Leap 15.6, openSUSE Tumbleweed): Fixed 11. https://www.suse.com/security/cve/CVE-2025-67899/
ubuntu medium CVE-2025-67899 medium priority: Ubuntu including 1 source packages (uriparser), 9 status rows across 9 suites (bionic, focal, jammy, noble, plucky, questing, trusty, upstream, xenial): needed 7, ignored 1, released 1. https://ubuntu.com/security/CVE-2025-67899

Affected software / configurations for CVE-2025-67899

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-67899

cvelogic Threat Intelligence