Skip to main content
Mallory
UnratedVulnerability

CVE-2026-48841: Integer overflow in uriparser ComposeQueryEngine

Updated 2 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days22 mentions · peak 16 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-48841CWE-190

CVE-2026-48841 is an integer overflow or wraparound vulnerability in uriparser's ComposeQueryEngine query-composition routine. It also affects PHP deployments using the URI extension with a vulnerable bundled uriparser library. The vulnerability is fixed in uriparser 1.0.3, incorporated into PHP 8.5.13 and PHP 8.6.0. The exact arithmetic operation, triggering input, and resulting security consequences are not established.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

A FreeBSD package assessment assigns high confidentiality, integrity, and availability impacts, with a CVSS v3.0 score of 9.8. However, specific consequences such as arbitrary code execution, information disclosure, or process termination are not established by the available vulnerability-specific technical details.

Remediation

Patch, then assume compromise.

Upgrade uriparser to version 1.0.3 or a later fixed release. For affected PHP deployments, upgrade to PHP 8.5.13, PHP 8.6.0, or a later fixed release incorporating the corrected library, or install a vendor package with a confirmed backported fix. Restart affected PHP workers and rebuild deployed application images as applicable to ensure the corrected library is loaded.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
FAQ

Frequently asked questions

Is CVE-2026-48841 exploited in the wild?
As of Nov 20, 2026, Mallory has no reports of CVE-2026-48841 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-48841?
As of Nov 20, 2026, Mallory has found no public exploit for CVE-2026-48841.
Is there a patch for CVE-2026-48841?
Upgrade uriparser to version 1.0.3 or a later fixed release. For affected PHP deployments, upgrade to PHP 8.5.13, PHP 8.6.0, or a later fixed release incorporating the corrected library, or install a vendor package with a confirmed backported fix.
Activity feed

Recent activity

22 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
+16 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity1Community discussion across Reddit, Mastodon, and other social sources.