Quick answers
- Is CVE-2026-44928 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44928 being exploited in the wild.
- How severe is CVE-2026-44928?
- Low severity, with a CVSS score of 2.9, published 8 May 2026.
- Which products and versions are affected?
- Uriparser Project Uriparser < 1.0.2.
- Is there a fix for CVE-2026-44928?
- A patch was published on 2026-05-08: Fix merged into master branch and included in version 1.0.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44928 attacked?
- It is attacked over the network or with local access, in a software library.
- Am I affected by CVE-2026-44928?
- Check whether you run Uriparser Project Uriparser at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A logic error exists in the EqualsUri function family within uriparser before version 1.0.2. Specifically, the implementation fails to correctly account for the .absolutePath property during comparison, leading to incorrect equality results (CWE-670). An attacker could exploit this by providing specially crafted URIs to an application that uses uriparser for security-critical decisions, such as allowlist validation or origin checking. This could result in unauthorized access or bypass of security restrictions. The issue is resolved in version 1.0.2.
Affected products
- uriparser project uriparser < 1.0.2
Timeline
- 2026-05-04: other: Vulnerability identified and fix proposed in pull request
- 2026-05-08: disclosed: CVE-2026-44928 published
- 2026-05-08: patched: Fix merged into master branch and included in version 1.0.2