Skip to main content
Mallory
UnratedVulnerability

CVE-2026-45110: Unicode Path-Comparison Bypass in libarchive

Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 3 in a dayToday
CVSS-Not scored
EPSS-30-day exploit probability
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
IdentifiersCVE-2026-45110CWE-176

CVE-2026-45110 is a Unicode path-handling vulnerability in libarchive that permits bypassing file-overwrite protections and directory-exclusion checks. Security comparisons distinguish pathnames that the underlying filesystem resolves to the same object. On affected macOS filesystems, an attacker-controlled archive entry with an alternative Unicode filename can evade these checks and overwrite a protected file during extraction, subject to the extracting process's write permissions.

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.

Successful exploitation can cause unauthorized file overwrites and defeat directory-exclusion policies. Depending on the files writable by the extracting process, consequences can include data corruption, configuration hijacking, compromised automated build or backup workflows, and potentially code execution. The vulnerability does not independently grant write access beyond the process's existing filesystem permissions.

Mitigation

If you can’t patch tonight, do this now.

Developers should make security-sensitive path comparisons and exclusion checks consistent with the underlying filesystem's Unicode normalization and case-folding behavior rather than relying on byte-for-byte comparisons. Monitor archive extraction for unexpected file writes. No specific end-user workaround is identified.

Remediation

Patch, then assume compromise.

Update libarchive and applications that bundle it to vendor-provided releases addressing CVE-2026-45110. Affected version ranges and a specific fixed libarchive release are not available in the supplied information.

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-45110 exploited in the wild?
As of Nov 17, 2026, Mallory has no reports of CVE-2026-45110 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2026-45110?
As of Nov 17, 2026, Mallory has found no public exploit for CVE-2026-45110.
Is there a patch for CVE-2026-45110?
Update libarchive and applications that bundle it to vendor-provided releases addressing CVE-2026-45110. Affected version ranges and a specific fixed libarchive release are not available in the supplied information.
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.