# CVE-2025-67899: Denial of service in uriparser

> Attackers can cause denial of service via unbounded recursion in the uriparser library by providing large inputs with many commas.

- **Severity:** Low 2.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Dec 2025
- **Updated:** 15 Dec 2025
- **Also known as:** AZL-72379, AZL-72862, DEBIAN-CVE-2025-67899, ECHO-fafd-c1a0-0f9d, GHSA-h2vr-rqqp-xv8m, RHSA-2026:7642, SUSE-SU-2026:0444-1, SUSE-SU-2026:22084-1, UBUNTU-CVE-2025-67899, USN-8409-1, openSUSE-SU-2026:10045-1, openSUSE-SU-2026:10595-1, openSUSE-SU-2026:20910-1

## What is CVE-2025-67899?

CVE-2025-67899 is a low-severity denial of service vulnerability in uriparser, published on 14 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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

Weakness: CWE-674 (Uncontrolled Recursion)

## Which versions are affected by CVE-2025-67899?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mingw32-uriparser` | Red Hat:hummingbird:1 | All versions | 0:1.0.0-2.1.hum1 |
| `mingw64-uriparser` | Red Hat:hummingbird:1 | All versions | 0:1.0.0-2.1.hum1 |
| `uriparser` | Red Hat:hummingbird:1 | All versions | 0:1.0.0-2.1.hum1 |
| `uriparser-devel` | Red Hat:hummingbird:1 | All versions | 0:1.0.0-2.1.hum1 |
| `uriparser-doc` | Red Hat:hummingbird:1 | All versions | 0:1.0.0-2.1.hum1 |
| `uriparser` | SUSE:Linux Enterprise Module for Package Hub 15 SP7 | All versions | 0.8.5-150000.3.11.1 |
| `uriparser` | SUSE:Linux Enterprise Server 16.0 | All versions | 0.9.8-160000.4.1 |
| `uriparser` | SUSE:Linux Enterprise Server for SAP applications 16.0 | All versions | 0.9.8-160000.4.1 |
| `uriparser` | openSUSE:Leap 15.6 | All versions | 0.8.5-150000.3.11.1 |
| `uriparser` | openSUSE:Leap 16.0 | All versions | 0.9.8-160000.4.1 |
| `php8` | openSUSE:Tumbleweed | All versions | 8.5.5-1.1 |
| `uriparser` | openSUSE:Tumbleweed | All versions | 1.0.0-1.1 |

## How do I fix CVE-2025-67899?

Upgrade to a fixed version.

## Is CVE-2025-67899 being exploited?

There is no known exploitation of CVE-2025-67899 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-67899 and fix it if it is affected.

What it is: CVE-2025-67899 is a low-severity denial of service vulnerability in uriparser, published on 14 Dec 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-67899 in the wild and no public exploit code.

Affected product: uriparser. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-67899/ (Markdown: https://insights.sbomify.com/CVE-2025-67899/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-67899
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-67899
- OSV: https://osv.dev/vulnerability/CVE-2025-67899

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-67899/
Summaries are generated and may contain mistakes; the official description above is the record.