{"id":"CVE-2026-102514","aliases":["EUVD-2026-91054","GHSA-6592-qv35-5gx2","MGASA-2026-0593"],"status":"published","title":"Out-of-bounds write in PeaZip PEA extractor allows code execution via a crafted .pea archive","description":"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 \u003e 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).","severity":{"version":"4.0","score":8.4,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-12","score":0.00129,"percentile":0.02588,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":false},"cwes":["CWE-125","CWE-1284","CWE-787"],"published":"2026-10-01T20:00:51Z","modified":"2026-11-12T22:45:03Z","affected":[{"source":"osv","ecosystem":"Mageia:10","package":"peazip","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"11.4.0-1.1.mga10"}]}],"bundled":2}],"products":[{"vendor":"peazip","product":"peazip"}],"references":[{"url":"https://github.com/peazip/PeaZip/commit/90ddbaee0945a4d8ffa4d972d43711bbfb9576ba","tags":["patch","fix"]},{"url":"https://secur0.com/en/cna/cve-list/cve-2026-102514-out-of-bounds-write-in-peazip-pea-extractor","tags":["third-party-advisory","technical-description","advisory"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-102514","tags":["advisory"]},{"url":"https://github.com/advisories/GHSA-6592-qv35-5gx2"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/102xxx/CVE-2026-102514.json","tags":["advisory"]},{"url":"https://github.com/peazip/PeaZip","tags":["package"]},{"url":"https://github.com/peazip/PeaZip/releases","tags":["package"]},{"url":"https://advisories.mageia.org/MGASA-2026-0593.html","tags":["advisory"]},{"url":"https://bugs.mageia.org/show_bug.cgi?id=36619","tags":["report"]},{"url":"https://github.com/peazip/PeaZip/releases#release-11.0.0","tags":["web"]},{"url":"https://github.com/peazip/PeaZip/releases#release-11.1.0","tags":["web"]},{"url":"https://github.com/peazip/PeaZip/releases#release-11.2.0","tags":["web"]},{"url":"https://github.com/peazip/PeaZip/releases#release-11.3.0","tags":["web"]},{"url":"https://github.com/peazip/PeaZip/releases#release-11.4.0","tags":["web"]}],"sources":{"cve":[{"id":"CVE-2026-102514","title":"Out-of-bounds write in PeaZip PEA extractor allows code execution via a crafted .pea archive","description":"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 \u003e 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).","status":"published","published":"2026-10-01T20:00:51.76Z","modified":"2026-10-14T16:50:59.674Z","cvss":[{"version":"4.0","score":8.4,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","level":"high","assessor":"cna"}],"cwes":["CWE-787","CWE-125","CWE-1284"],"updated_at":"2026-11-02T13:38:54.394896Z"}],"euvd":[{"id":"EUVD-2026-91054","description":"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 \u003e 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).","status":"published","published":"2026-10-01T20:00:51Z","modified":"2026-10-14T16:50:59Z","cvss":[{"version":"4.0","score":8.4,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","level":"high"}],"updated_at":"2026-11-02T17:27:14.304159Z"}],"ghsa":[{"id":"GHSA-6592-qv35-5gx2","title":"Out-of-bounds Write (CWE-787) in the PEA archive extraction routine (pea.pas, unpea_procedure) of...","description":"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 \u003e 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).","status":"published","published":"2026-10-01T21:32:53Z","modified":"2026-10-14T18:32:49Z","cvss":[{"version":"4.0","score":8.4,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high"}],"cwes":["CWE-125","CWE-787"],"updated_at":"2026-11-02T15:13:28.606179Z"}],"nvd":[{"id":"CVE-2026-102514","description":"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 \u003e 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).","status":"published","published":"2026-10-01T21:17:18.307Z","modified":"2026-10-14T17:18:10.523Z","cvss":[{"version":"4.0","score":8.4,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"high","assessor":"secondary"}],"cwes":["CWE-125","CWE-787","CWE-1284"],"updated_at":"2026-11-02T14:12:53.41762Z"}],"osv":[{"id":"CVE-2026-102514","title":"Out-of-bounds write in PeaZip PEA extractor allows code execution via a crafted .pea archive","description":"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 \u003e 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).","status":"published","published":"2026-10-01T20:00:51.76Z","modified":"2026-10-28T02:30:31.833576114Z","cvss":[{"version":"4.0","score":8.4,"vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","level":"high"}],"cwes":["CWE-125","CWE-1284","CWE-787"],"updated_at":"2026-11-02T15:44:53.83521Z"},{"id":"MGASA-2026-0593","title":"Updated peazip package fixes security vulnerabilities","description":"CVE-2026-102514 - Out-of-bounds Write (CWE-787) in the PEA archive\nextraction routine (pea.pas, unpea_procedure) of the first-party pea\ncomponent in PeaZip 11.2.0 and earlier allows an attacker who convinces\na victim to open or extract a crafted .pea archive to execute arbitrary\ncode as the user running PeaZip. While decompressing a PCOMPRESS1\nstream, the 32-bit compressed-block-size field of the first block\n(compsize) is read directly from the archive and used without validation\nas the length of a blockread into the fixed-size global buffers\nwbuf1/wbuf2 (1,114,112 bytes) and as the bound of the subsequent copy\nloop. The existing check \"compsize \u003e WBUFSIZE\" is applied only to the\nsize of each following block, so the first block escapes it; the same\nunvalidated value is also used to index wbuf1[compsize], an\nout-of-bounds read at an attacker-chosen offset. The copy loop\nadditionally copies the requested length instead of the number of bytes\nactually read, and terminates on equality rather than on an upper bound.\nBecause the project is built without range checking and no archive\npassword, integrity tag or non-default configuration is required, the\noverflow overwrites adjacent global data; code execution was\ndemonstrated by two independent researchers against the official Linux\nx86-64 and Windows x64 builds, and the denial-of-service and\nmemory-corruption primitive is cross-platform (Windows, macOS, Linux,\nBSD).\nCVE CVE-2026-105050 - PeaZip before 11.3.0, in a non-default\nconfiguration, is vulnerable to OS command injection via a filename in\nan archive because \"quotation character already used in the string\" is\nmishandled.\n","status":"published","published":"2026-11-12T22:40:23Z","modified":"2026-11-12T22:45:03.161310949Z","updated_at":"2026-11-12T23:17:33.063883Z"}]}}