PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-102514 PeaZip CVE debrief

CVE-2026-102514 is an out-of-bounds write vulnerability in PeaZip's PEA extractor that allows code execution via a crafted .pea archive. The vulnerability exists in PeaZip versions prior to 11.3.0 and is triggered when a victim opens or extracts a specially crafted .pea archive. This vulnerability has a high CVSS score of 8.4 and is considered a high-severity issue. Users of PeaZip versions prior to 11.3.0 should upgrade to the latest version to avoid potential code execution. The vulnerability is caused by an out-of-bounds write in the PEA archive extraction routine (pea.pas, unpea_procedure) of the first-party pea component in PeaZip 11.2.0 and earlier.

Vendor
PeaZip
Product
PeaZip
CVSS
HIGH 8.4
CISA KEV
Not listed in stored evidence
Original CVE published
2026-10-01
Original CVE updated
2026-10-14
Advisory published
2026-10-01
Advisory updated
2026-10-14

Who should care

Users of PeaZip versions prior to 11.3.0 should upgrade to the latest version to avoid potential code execution. This includes operators, administrators, and security teams responsible for managing PeaZip installations. Additionally, security teams should review compensating controls for exposed systems while remediation is scheduled and verified, and monitor for suspicious activity related to PeaZip. Asset inventory and vulnerability management teams are

Why it matters

CVE-2026-102514 is a high-severity vulnerability in PeaZip's PEA extractor that allows code execution via a crafted .pea archive. Users of PeaZip versions prior to 11.3.0 should upgrade to the latest version to avoid potential code execution.

  • Potential code execution via crafted .pea archive
  • Elevation of privileges for attackers
  • Data tampering and unauthorized access

Technical summary

The vulnerability is caused by an out-of-bounds write in the PEA archive extraction routine (pea.pas, unpea_procedure) of the first-party pea component in PeaZip 11.2.0 and earlier. 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.

Defensive priority

High

Recommended defensive actions

  • Upgrade PeaZip to version 11.3.0 or later
  • Avoid opening or extracting .pea archives from untrusted sources
  • Monitor for suspicious activity related to PeaZip
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented
  • Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is caused by an out-of-bounds write in the PEA archive extraction routine. The existing check 'compsize > WBUFSIZE' is applied only to the size of each following block, so the first block escapes it.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-102514 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-102514

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-102514 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-102514

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.