CVE-2026-102514

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.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-91054 (ENISA EUVD) · GHSA-6592-qv35-5gx2 (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.1%CVSS: 8.4Exploit: None knownExposed services: Not assessed

Upgrade to PeaZip 11.3.0 or higher, which validates the size of the first compressed block (commit 90ddbae), copies the number of bytes actually read, and stops the block-reading loop when the address exceeds the expect… (from the CVE record's solution, Secur0) — apply it.

Out-of-bounds Write (CWE-787) in the PEA archive extraction routine (pea.pas, unpea_procedure) of the first-party pea component in PeaZip 11.2.0 and earlier allows an attacker who convinces a victim to open or extract a crafted .pea archive to execute arbitrary code as the user running PeaZip. While decompressing a PCOMPRESS1 stream, the 32-bit compressed-block-size field of the first block (compsize) is read directly from the archive and used without validation as the length of a blockread into the fixed-size global buffers wbuf1/wbuf2 (1,114,112 bytes) and as the bound of the subsequent copy loop. The existing check "compsize > WBUFSIZE" is applied only to the size of each following block, so the first block escapes it; the same unvalidated value is also used to index wbuf1[compsize], an out-of-bounds read at an attacker-chosen offset. The copy loop additionally copies the requested length instead of the number of bytes actually read, and terminates on equality rather than on an upper bound. Because the project is built without range checking and no archive password, integrity tag or non-default configuration is required, the overflow overwrites adjacent global data; code execution was demonstrated by two independent researchers against the official Linux x86-64 and Windows x64 builds, and the denial-of-service and memory-corruption primitive is cross-platform (Windows, macOS, Linux, BSD).

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.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 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, which validates the size of the first compressed block (commit 90ddbae), copies the number of bytes actually read, and stops the block-reading loop when the address exceeds the expect… (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 (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.1% 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, which validates the size of the first compressed block (commit 90ddbae), copies the number of bytes actually read, and stops the block-reading loop when the address exceeds the expect… (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 1, 2026

Last Modified

October 14, 2026

Advisory Details (2)

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

CVE-2026-102514 · Out-of-bounds write in PeaZip PEA extractor allows code execution via a crafted .pea archive | Vulnerabilities published by Secur0

https://secur0.com/en/cna/cve-list/cve-2026-102514-out-of-bounds-write-in-peazip-pea-extractor
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-102514(1)

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

Weakness Classification(3)

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

Data Freshness Timeline

(refreshed 8× in last 7d / 65× 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-02 16:43 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  2. 2026-11-01 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  3. 2026-10-31 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-10-30 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-10-28 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  6. 2026-10-27 20:36 UTCEG score recompute
  7. 2026-10-27 20:36 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  8. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  9. 2026-10-26 16:30 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  10. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  11. 2026-10-25 14:56 UTCEG score recompute
  12. 2026-10-24 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  13. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  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 19:16 UTCEG score recompute
  17. 2026-10-20 19:16 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  18. 2026-10-20 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  19. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  20. 2026-10-18 05:10 UTCEG score recompute
  21. 2026-10-17 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-16 16:40 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  23. 2026-10-15 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  24. 2026-10-14 17:36 UTCEG score recompute
  25. 2026-10-14 17:35 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
Show 48 more
  1. 2026-10-14 17:02 UTCEG score recompute
  2. 2026-10-14 17:02 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  3. 2026-10-14 16:31 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  4. 2026-10-13 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  5. 2026-10-12 16:41 UTCEG score recompute
  6. 2026-10-12 16:33 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  7. 2026-10-11 19:26 UTCEG score recompute
  8. 2026-10-11 19:26 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  9. 2026-10-11 18:28 UTCEG score recompute
  10. 2026-10-11 15:02 UTCEG score recompute
  11. 2026-10-11 06:47 UTCEG score recompute
  12. 2026-10-11 06:47 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  13. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  14. 2026-10-10 18:09 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  15. 2026-10-10 05:30 UTCEG score recompute
  16. 2026-10-10 05:29 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  17. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  18. 2026-10-09 16:49 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  19. 2026-10-09 04:11 UTCEG score recompute
  20. 2026-10-09 04:11 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  21. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  22. 2026-10-08 15:31 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  23. 2026-10-08 01:17 UTCEG score recompute
  24. 2026-10-08 01:17 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  25. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  26. 2026-10-07 12:39 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  27. 2026-10-07 00:00 UTCEG score recompute
  28. 2026-10-07 00:00 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  29. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  30. 2026-10-06 11:22 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  31. 2026-10-05 22:44 UTCEG score recompute
  32. 2026-10-05 22:44 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  33. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  34. 2026-10-05 10:04 UTCEG score recompute
  35. 2026-10-05 10:04 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  36. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  37. 2026-10-04 21:26 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  38. 2026-10-04 08:48 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  39. 2026-10-03 20:10 UTCEG score recompute
  40. 2026-10-03 20:10 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  41. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.1% · 2nd percentile
  42. 2026-10-03 07:31 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  43. 2026-10-02 18:51 UTCEG score recompute
  44. 2026-10-02 18:51 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  45. 2026-10-02 09:58 UTCGHSA enrichmentGHSA-6592-qv35-5gx2 · GitHub severity HIGH
  46. 2026-10-01 21:20 UTCEG score recompute
  47. 2026-10-01 20:22 UTCEG score recomputeFirst assessed: 8.4 HIGH
  48. 2026-10-01 20:20 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-102514?
CVE-2026-102514 is a high-severity vulnerability; its CVE record was published on October 1, 2026. Out-of-bounds Write (CWE-787) in the PEA archive extraction routine (pea.pas, unpea_procedure) of the first-party pea component in PeaZip 11.2.0 and earlier allows an attacker who convinces a victim to open or extract a crafted .pea archive to execute arbitrary code as the user running PeaZip.…
When was CVE-2026-102514 made public?
CVE-2026-102514 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 1, 2026. EchelonGraph's copy of the record carries a last-modified date of October 14, 2026; the record at its source may have been updated since.
Is CVE-2026-102514 actively exploited?
CVE-2026-102514 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-102514?
CVE-2026-102514 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-102514?
The CVE record's solution for CVE-2026-102514, written by its CNA Secur0, names the fix: "Upgrade to PeaZip 11.3.0 or higher, which validates the size of the first compressed block (commit 90ddbae), copies the number of bytes actually read, and stops the block-reading loop when the address exceeds the expect…" The vendor advisories EchelonGraph has for CVE-2026-102514 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-102514?

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

Book a Demo →Browse All CVEs