CVE
7-Zip file name spoofing warning bypass in file manager
Only affects 7-Zip File Manager before 26.03, where archive entry names padded with Unicode space characters bypass the deceptive file name warning. Fixed in 26.03.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
- Exploited
- No known exploitation
- Fix
- Fixed in 26.03
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. 7-Zip File Manager versions before 26.03 Archive entry name padded with Unicode space characters before a real extension such as .hta
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 14/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
7-Zip File Manager fails to detect archive entry names padded with Unicode space characters, so a crafted entry can bypass the deceptive file name warning and hide its real script extension. A local attacker with no login needs a user to open the crafted entry, which then runs its script content.
Original description
7-Zip File Manager before 26.03 fails to detect archive entry names padded with Unicode space characters, allowing attackers to bypass the deceptive file name warning in CPanel::IsVirus_Message. Attackers can craft archive entries like a PDF name followed by ideographic spaces and .hta to hide the real extension, executing script content via ShellExecuteExW when opened.
Who should check
Anyone running 7-Zip File Manager older than 26.03, including users who open archives containing crafted entry names
“7-Zip File Manager before 26.03”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.5/10CVSS 8.5
- No patch0/5No signal
What would change the score
- Would score about 64 if added to CISA KEV
- Would score about 59 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
7-Zip File Manager versions before 26.03 Archive entry name padded with Unicode space characters before a real extension such as .htaUpgrade to a fixed version: 26.03.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-130067 (7-Zip File Manager before 26.03 File Name Spoofing Warning Bypass via Unicode Spaces), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-130067 (entry last updated 2026-11-16):
Affected:
- 7-Zip 7-Zip: fixed in 26.03
Fixed versions: 26.03.
Conditions (all must be true for the bug to be hit):
- 7-Zip File Manager versions before 26.03 (source: https://www.vulncheck.com/advisories/7-zip-file-manager-before-26.03-file-name-spoofing-warning-bypass-via-unicode-spaces)
- Archive entry name padded with Unicode space characters before a real extension such as .hta (source: https://www.vulncheck.com/advisories/7-zip-file-manager-before-26.03-file-name-spoofing-warning-bypass-via-unicode-spaces)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-130067 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-130067 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/ip7z/7zip/commit/0766b733fe3e06dd2a7f9a3cfbf2108ac73abd17
- https://github.com/ip7z/7zip/releases/tag/26.03
- https://github.com/ip7z/7zip/blob/26.02/CPP/7zip/UI/FileManager/PanelItemOpen.cpp#L867-L893
- https://www.7-zip.org/history.txt
- https://www.vulncheck.com/advisories/7-zip-file-manager-before-26.03-file-name-spoofing-warning-bypass-via-unicode-spaces
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-130067
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-130067"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- 7-Zip 7-Zip
fixed in 26.03
Evidence 7
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 5
- Patch
- Repository
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-130067
Is CVE-2026-130067 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Archive entry names padded with Unicode space characters can hide the real file extension, such as .hta, behind a harmless-looking name like a PDF. 7-Zip File Manager fails to show the deceptive file name warning for these entries, so script content in the crafted entry can run via ShellExecuteExW when opened.Source: vulncheck.com
Which versions are affected by CVE-2026-130067?
7-Zip: before 26.03.Source: cve.now feed data
Am I affected, and how do I check?
7-Zip File Manager versions before 26.03 are affected. To check your version, look at the version shown in the 7-Zip File Manager About dialog or run 7z with no arguments and read the version line; the issue concerns archives whose entry names contain Unicode space padding before a real extension.Source: vulncheck.com
How do I fix CVE-2026-130067?
Upgrade 7-Zip to version 26.03 or later, which fixes this issue.Source: vulncheck.com