# CVE-2026-44927: Integer overflow in uriparser

> An attacker can cause pointer difference truncation in uriparser, potentially leading to denial of service or unexpected behavior.

- **Severity:** Low 2.9 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 8 May 2026
- **Updated:** 10 May 2026
- **Also known as:** AZL-86109, DEBIAN-CVE-2026-44927, ECHO-0dda-835f-39bb, GHSA-gmxg-5w57-j63q, ROOT-OS-DEBIAN-12-CVE-2026-44927, UBUNTU-CVE-2026-44927

## What is CVE-2026-44927?

CVE-2026-44927 is a low-severity vulnerability in uriparser, published on 8 May 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

In uriparser before 1.0.2, there is pointer difference truncation to int in various places.

Weakness: CWE-197 (Numeric Truncation Error)

## Which versions are affected by CVE-2026-44927?

It affects 1 product.


Products: Uriparser Project Uriparser.

## How do I fix CVE-2026-44927?

Upgrade to a fixed version.

## Is CVE-2026-44927 being exploited?

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

## Other vulnerabilities in uriparser

- [CVE-2026-42371](https://insights.sbomify.com/CVE-2026-42371/): Integer overflow in uriparser (medium 5.1)
- [CVE-2026-44928](https://insights.sbomify.com/CVE-2026-44928/): Other in uriparser (low 2.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44927 and fix it if it is affected.

What it is: CVE-2026-44927 is a low-severity vulnerability in uriparser, published on 8 May 2026. 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-2026-44927 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-2026-44927/ (Markdown: https://insights.sbomify.com/CVE-2026-44927/index.md)
```

## Sources

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

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