CVE-2026-104025

HIGHPre-NVD 8.48.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 8.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (5th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-102023 (ENISA EUVD) · GHSA-3f37-hmcf-9x56 (GitHub Security Advisories)Source: ENISA EUVD

8.4EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 8.4Exploit: None knownExposed services: Not assessed

Upgrade to PeaZip 11.3.0 or higher (from the CVE record's solution, Secur0) — apply it.

Path Traversal (CWE-22) in the execute_obj function of the archive object viewer (peach.pas) in PeaZip 11.2.0 and earlier on Windows allows an attacker who convinces a victim to preview an entry of a crafted archive via the "Preview with... -> Associated application" action (Shift+Ctrl+O) to execute an arbitrary program already present on the victim's system, with no warning dialog. The function validates only outname (PeaZip's own temporary directory) with checkfiledirname, while the string actually executed is the concatenation outname+tempstring; tempstring is taken verbatim from the archive entry name (StringGridList.Cells[12,...]) and is never validated. checkfiledirname (list_utils.pas) rejects control and reserved characters in the file name but performs no ".." path-containment check, so an entry named ../../../../Windows/System32/calc.exe escapes the extraction directory and is passed to cp_open -> ShellExecuteW; the extracting backend (7-Zip) strips the traversal while the opener does not. In addition, the SECEXTCONST dangerous-extension confirmation prompt is implemented only in the double-click handler (grid_obj_open) and not on this preview route, so an executable inside an archive reaches ShellExecuteW unannounced, and where the prompt does fire it names the entry's display name rather than the resolved path that will run. Arbitrary code execution was demonstrated with a proof of concept against official PeaZip builds, confirmed on two archive formats (.zip and .tar) to show the defect is in PeaZip's own path handling and not in a single format parser.

CVSS v3
8.4
EG Score
8.4HIGHmedium confidence
EG Risk
38
EG Risk 38/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity84% × 45%
Impact severity (EG Severity): CVSS 8.4 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: Upgrade to PeaZip 11.3.0 or higher (from the CVE record's solution, Secur0). Apply it within your standard update timelines.
EPSS PROB
0.2%
EPSS %ILE
5th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.4): severity, escalated by confirmed exploitation. This CVE's 8.4 is its impact severity (EG Severity), not escalated.

EG Severity
8.4 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

Upgrade to PeaZip 11.3.0 or higher (from the CVE record's solution, Secur0). Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 15, 2026

Last Modified

October 16, 2026

Advisory Details (2)

Auto-updated Oct 15, 2026
Fix named in the CVE record's solution (Secur0). Sources: github_commit.
Web page

CVE-2026-104025 · Path traversal in PeaZip object preview allows execution of arbitrary programs via a crafted archive entry name | Vulnerabilities published by Secur0

https://secur0.com/en/cna/cve-list/cve-2026-104025-path-traversal-in-peazip-object-preview
GitHub commit

commit 009fc35530e2 (peazip/PeaZip)

Fix landed in peazip/PeaZip commit 009fc35530e2 — awaiting tagged release

https://github.com/peazip/PeaZip/commit/009fc35530e26729863969eddf4c18f1b48331cf

Vendor Advisories for CVE-2026-104025(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 28× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

  1. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  2. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  4. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  5. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  6. 2026-10-27 20:36 UTCEG score recompute
  7. 2026-10-27 20:36 UTCGHSA enrichmentGHSA-3f37-hmcf-9x56 · GitHub severity HIGH
  8. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  9. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  11. 2026-10-25 14:56 UTCEG score recompute
  12. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  14. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  15. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-10-20 19:14 UTCEG score recompute
  17. 2026-10-20 19:14 UTCGHSA enrichmentGHSA-3f37-hmcf-9x56 · GitHub severity HIGH
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  21. 2026-10-18 05:09 UTCEG score recompute
  22. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-10-16 20:09 UTCEG score recompute
  24. 2026-10-16 20:09 UTCGHSA enrichmentGHSA-3f37-hmcf-9x56 · GitHub severity HIGH
  25. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.2% · 4th percentile
Show 3 more
  1. 2026-10-15 13:25 UTCEG score recompute
  2. 2026-10-15 12:23 UTCEG score recomputeFirst assessed: 8.4 HIGH
  3. 2026-10-15 12:22 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-104025?
CVE-2026-104025 is a high-severity vulnerability; its CVE record was published on October 15, 2026. Path Traversal (CWE-22) in the execute_obj function of the archive object viewer (peach.pas) in PeaZip 11.2.0 and earlier on Windows allows an attacker who convinces a victim to preview an entry of a crafted archive via the "Preview with... -> Associated application" action (Shift+Ctrl+O) to…
When was CVE-2026-104025 made public?
CVE-2026-104025 was made public on September 3, 2026: that is the date its CVE record's CNA, Secur0, gives for when the vulnerability was made public. The CVE record itself was published on October 15, 2026. EchelonGraph's copy of the record carries a last-modified date of October 16, 2026; the record at its source may have been updated since.
Is CVE-2026-104025 actively exploited?
CVE-2026-104025 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (5th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-104025?
CVE-2026-104025 has a CVSS base score of 8.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-104025?
The CVE record's solution for CVE-2026-104025, written by its CNA Secur0, names the fix: "Upgrade to PeaZip 11.3.0 or higher." The vendor advisories EchelonGraph has for CVE-2026-104025 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-104025

Explore →

Is Your Infrastructure Affected by CVE-2026-104025?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs