CVE-2026-105050

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (44th 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

Also known asEUVD-2026-91838 (ENISA EUVD) · GHSA-377g-778f-272q (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
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.5%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

PeaZip before 11.3.0, in a non-default configuration, is vulnerable to OS command injection via a filename in an archive because "quotation character already used in the string" is mishandled.

CVSS
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/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)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.5% × 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: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.5%
EPSS %ILE
44th
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 (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source
EG Likelihood
0.5% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-10). 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).

A fix is available. 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 2, 2026

Last Modified

October 6, 2026

Advisory Details (4)

Auto-updated Oct 2, 2026
Patch available. Sources: github_release, github_commit.
GitHub commit

commit 009fc35530e2 (peazip/PeaZip)

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

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

Secur0 - Plataforma de bug bounty

https://app.secur0.com/certificate/ys3yqg-avrwaq-5ybnwl
Web page

PeaZip/peazip-sources at sources · peazip/PeaZip · GitHub

https://github.com/peazip/PeaZip/tree/sources/peazip-sources
GitHub release Patch Available

PeaZip 11.3.0

Patch available: peazip/PeaZip 11.3.0

https://github.com/peazip/PeaZip/releases/tag/11.3.0

Vendor Advisories for CVE-2026-105050(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 37× 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 its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS → 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:50 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  2. 2026-11-12 16:32 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  3. 2026-11-11 16:37 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  4. 2026-11-11 03:23 UTCEchelonGraph re-scored
  5. 2026-11-11 03:23 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  6. 2026-11-10 16:41 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  7. 2026-11-10 08:50 UTCEchelonGraph re-scored
  8. 2026-11-10 08:50 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  9. 2026-11-09 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  10. 2026-11-08 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  11. 2026-11-07 16:38 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  12. 2026-11-06 16:35 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  13. 2026-11-05 16:36 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  14. 2026-11-04 16:34 UTCEPSS rescoreEPSS 0.5% · 44th percentile
  15. 2026-11-03 19:50 UTCEchelonGraph re-scored
  16. 2026-11-03 19:50 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  17. 2026-11-03 16:46 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  18. 2026-11-03 09:03 UTCEchelonGraph re-scored
  19. 2026-11-03 09:03 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  20. 2026-11-02 16:43 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  21. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  22. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  23. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  24. 2026-10-29 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  25. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
Show 72 more
  1. 2026-10-27 20:01 UTCEchelonGraph re-scored
  2. 2026-10-27 20:01 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  3. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  4. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  5. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  6. 2026-10-25 14:55 UTCEchelonGraph re-scored
  7. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  8. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  9. 2026-10-22 16:33 UTCEPSS rescoreEPSS 0.5% · 43rd percentile
  10. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  11. 2026-10-20 19:13 UTCEchelonGraph re-scored
  12. 2026-10-20 19:13 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  13. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  14. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  15. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  16. 2026-10-18 05:09 UTCEchelonGraph re-scored
  17. 2026-10-17 19:37 UTCEchelonGraph re-scored
  18. 2026-10-17 19:37 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  19. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  20. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  21. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  22. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  23. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  24. 2026-10-12 16:40 UTCEchelonGraph re-scored
  25. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  26. 2026-10-12 00:58 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  27. 2026-10-11 20:15 UTCEchelonGraph re-scored
  28. 2026-10-11 18:27 UTCEchelonGraph re-scored
  29. 2026-10-11 15:01 UTCEchelonGraph re-scored
  30. 2026-10-11 13:47 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  31. 2026-10-11 13:27 UTCEchelonGraph re-scored
  32. 2026-10-11 13:26 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  33. 2026-10-11 01:56 UTCEchelonGraph re-scored
  34. 2026-10-11 01:56 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  35. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  36. 2026-10-10 14:29 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  37. 2026-10-10 03:03 UTCEchelonGraph re-scored
  38. 2026-10-10 03:03 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  39. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  40. 2026-10-09 15:38 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  41. 2026-10-09 04:12 UTCEchelonGraph re-scored
  42. 2026-10-09 04:12 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  43. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  44. 2026-10-08 16:47 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  45. 2026-10-08 04:50 UTCEchelonGraph re-scored
  46. 2026-10-08 04:50 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  47. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 42nd percentile
  48. 2026-10-07 17:25 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  49. 2026-10-07 05:58 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  50. 2026-10-06 18:33 UTCEchelonGraph re-scored
  51. 2026-10-06 18:33 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  52. 2026-10-06 17:47 UTCEchelonGraph re-scored
  53. 2026-10-06 17:47 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  54. 2026-10-06 16:21 UTCEchelonGraph re-scored
  55. 2026-10-06 16:21 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  56. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  57. 2026-10-06 07:24 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  58. 2026-10-05 19:59 UTCEchelonGraph re-scored
  59. 2026-10-05 19:59 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  60. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  61. 2026-10-05 08:35 UTCEchelonGraph re-scored
  62. 2026-10-05 08:35 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  63. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  64. 2026-10-04 21:09 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  65. 2026-10-04 09:43 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  66. 2026-10-03 22:16 UTCEchelonGraph re-scored
  67. 2026-10-03 22:16 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  68. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 41st percentile
  69. 2026-10-03 10:51 UTCGHSA enrichmentGHSA-377g-778f-272q · GitHub severity HIGH
  70. 2026-10-02 23:26 UTCEchelonGraph re-scored
  71. 2026-10-02 22:47 UTCEchelonGraph re-scoredFirst assessed: 7.1 HIGH
  72. 2026-10-02 22:45 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-105050?
CVE-2026-105050 is a high-severity vulnerability; its CVE record was published on October 2, 2026. PeaZip before 11.3.0, in a non-default configuration, is vulnerable to OS command injection via a filename in an archive because "quotation character already used in the string" is mishandled.
When was the CVE record for CVE-2026-105050 published?
The CVE record for CVE-2026-105050 was published on October 2, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 6, 2026; the record at its source may have been updated since.
Is CVE-2026-105050 actively exploited?
CVE-2026-105050 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (44th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-105050?
CVE-2026-105050 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-105050?
A fix for CVE-2026-105050 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-105050 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-105050?

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