CVE-2026-44927

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

Published: 2026-05-08 Last update: 2026-05-12 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2026-44927 is rated Low Risk (11.7/100): CVSS Low severity, with low exploitation likelihood (EPSS 0.00%). Mandatory action: 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-2026-44927

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 2026-05-08 0.00%

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-44927

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:L/A:N 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:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
1.4 1.4 [email protected]
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
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:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
3.9 1.4 [email protected]

Weakness enumeration for CVE-2026-44927

GitHub Security Advisory for CVE-2026-44927

GHSA-gmxg-5w57-j63q · Severity: low — In uriparser before 1.0.2, there is pointer difference truncation to int in various places.

OS Trackers for CVE-2026-44927

vendor priority summary link
debian not yet assigned CVE-2026-44927 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-2026-44927
suse high https://www.suse.com/security/cve/CVE-2026-44927/
ubuntu medium CVE-2026-44927 medium priority: Ubuntu including 1 source packages (uriparser), 9 status rows across 9 suites (bionic, focal, jammy, noble, questing, resolute, trusty, upstream, xenial): needs-triage 9. https://ubuntu.com/security/CVE-2026-44927

Affected software / configurations for CVE-2026-44927

Vendor Product Version Raw CPE
uriparser_project uriparser < 1.0.2 cpe:2.3:a:uriparser_project:uriparser:*:*:*:*:*:*:*:*

References for CVE-2026-44927

URL Tags
https://github.com/uriparser/uriparser/pull/304 Issue Tracking Patch
cvelogic Threat Intelligence