CVE-2026-104024

MEDIUMPre-NVD 4.64.6
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 4.6 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1% (2nd 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-102089 (ENISA EUVD) · GHSA-7pj5-7mcm-w2c6 (GitHub Security Advisories)Source: ENISA EUVD

4.6EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 4.6Exploit: None knownExposed services: Not assessed

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

Incomplete List of Disallowed Inputs (CWE-184) in the dangerous-extension confirmation of the archive object viewer (peach.pas, grid_obj_open) in PeaZip 10.5.0 through 11.2.0 on Windows allows an attacker who convinces a victim to open an entry of a crafted archive to execute a program, or an arbitrary command, with no confirmation dialog. The prompt (Do you want to run this file?) is gated by SECEXTCONST, a hard-coded list of seven extensions (exe cmd msi bat ps1 vbs reg); the check is an exact string comparison of the entry extension against that list, so it answers only whether the extension is one of the seven and never whether the shell will execute the file. Shell-executable and scripting-host types that Windows runs through ShellExecuteW are absent from the list, among them .url and .lnk. An archived Windows Internet Shortcut (.url) whose URL line is attacker-controlled is launched with no prompt, while the byte-identical content in an entry named .bat does raise the warning in the same session. A .lnk entry raises the ceiling from launching a program to running a command line, because a Windows shortcut carries arguments: a proof-of-concept shortcut targeting cmd.exe with an attacker-chosen command line executed with no prompt. The shortcut target is not confined to the local disk; the shell also resolved an attacker-named UNC path (fetching a remote payload was only attempted, not demonstrated). No privilege escalation; everything runs as the user who opened the archive.

CVSS v3
4.6
EG Score
4.6MEDIUMmedium confidence
EG Risk
21
EG Risk 21/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)
Severity46% × 45%
Impact severity (EG Severity): CVSS 4.6 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.1% × 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 every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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.1%
EPSS %ILE
2nd
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 (4.6): severity, escalated by confirmed exploitation. This CVE's 4.6 is its impact severity (EG Severity), not escalated.

EG Severity
4.6 MEDIUMCVSS-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.1% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-28). 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 every mission impact level.CISA BOD 26-04: 60 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 every mission impact level.

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 partial (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)60 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 partial (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-104024 · Incomplete dangerous-extension list in PeaZip object open allows execution of a program or command from a crafted archive entry without confirmation | Vulnerabilities published by Secur0

https://secur0.com/en/cna/cve-list/cve-2026-104024-incomplete-extension-list-in-peazip
GitHub commit

commit 90ddbaee0945 (peazip/PeaZip)

Fix landed in peazip/PeaZip commit 90ddbaee0945 — awaiting tagged release

https://github.com/peazip/PeaZip/commit/90ddbaee0945a4d8ffa4d972d43711bbfb9576ba

Vendor Advisories for CVE-2026-104024(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 7× 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.1% · 2nd percentile
  2. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-10-29 14:51 UTCEG score recompute
  5. 2026-10-29 14:51 UTCGHSA enrichmentGHSA-7pj5-7mcm-w2c6
  6. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  8. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-25 14:56 UTCEG score recompute
  10. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  12. 2026-10-23 09:17 UTCEG score recompute
  13. 2026-10-23 09:17 UTCGHSA enrichmentGHSA-7pj5-7mcm-w2c6
  14. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  15. 2026-10-21 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  16. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  17. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-18 05:09 UTCEG score recompute
  19. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-16 20:13 UTCGHSA enrichmentGHSA-7pj5-7mcm-w2c6
  21. 2026-10-16 19:46 UTCEG score recompute
  22. 2026-10-16 19:45 UTCGHSA enrichmentGHSA-7pj5-7mcm-w2c6
  23. 2026-10-16 18:55 UTCEG score recompute
  24. 2026-10-16 18:55 UTCGHSA enrichmentGHSA-7pj5-7mcm-w2c6
  25. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
Show 3 more
  1. 2026-10-15 14:29 UTCEG score recompute
  2. 2026-10-15 13:39 UTCEG score recomputeFirst assessed: 4.6 MEDIUM
  3. 2026-10-15 13:37 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-104024?
CVE-2026-104024 is a medium-severity vulnerability; its CVE record was published on October 15, 2026. Incomplete List of Disallowed Inputs (CWE-184) in the dangerous-extension confirmation of the archive object viewer (peach.pas, grid_obj_open) in PeaZip 10.5.0 through 11.2.0 on Windows allows an attacker who convinces a victim to open an entry of a crafted archive to execute a program, or an…
When was CVE-2026-104024 made public?
CVE-2026-104024 was made public on August 27, 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-104024 actively exploited?
CVE-2026-104024 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (2nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-104024?
CVE-2026-104024 has a CVSS base score of 4.6 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-104024?
The CVE record's solution for CVE-2026-104024, written by its CNA Secur0, names the fix: "Upgrade to PeaZip 11.3.0 or higher." The vendor advisories EchelonGraph has for CVE-2026-104024 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-104024?

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

Book a Demo →Browse All CVEs