Process crash via unbounded URI parser recursion
Published Dec 14, 2025 · Updated Dec 14, 2025
Uncontrolled recursion in uriparser 0 through 0.9.9 allows local users to crash a consuming process with a comma-heavy URI. ParseMustBeSegmentNzNc recursively calls itself for each comma-separated segment without a recursion bound, consuming stack until overflow. The caller must pass a sufficiently long crafted URI to a vulnerable parser build; the demonstrated consequence is a process crash, not data access or code execution.
Summary
What happened
Uncontrolled recursion in uriparser 0 through 0.9.9 allows local users to crash a consuming process with a comma-heavy URI. ParseMustBeSegmentNzNc recursively calls itself for each comma-separated segment without a recursion bound, consuming stack until overflow. The caller must pass a sufficiently long crafted URI to a vulnerable parser build; the demonstrated consequence is a process crash, not data access or code execution.
The record
- CVE
- CVE-2025-67899
- Published
- Dec 14, 2025
- Updated
- Dec 14, 2025
- Vendor
- uriparser project
- Product
- uriparser
- Classifications
- CWE-674, T1499.004
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 14, 2025CVE publishedPublication date reported by the CVE source.
- Dec 14, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=0.9.9
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub issue 282 crash reproducerproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo