{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-102514 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-102514 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102514 is a high-severity memory corruption vulnerability in PeaZip, published on 1 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-102514 and fix it if it is affected.\n\nWhat it is: CVE-2026-102514 is a high-severity memory corruption vulnerability in PeaZip, published on 1 Oct 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-102514 in the wild and no public exploit code.\n\nAffected product: PeaZip. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-102514/ (Markdown: https://insights.sbomify.com/CVE-2026-102514/index.md)","id":"CVE-2026-102514","markdown":"https://insights.sbomify.com/CVE-2026-102514/index.md","name":"CVE-2026-102514","record":{"aliases":["GHSA-6592-qv35-5gx2"],"analysis":{"component_type":"desktop_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"PeaZip archive utility","requires_auth":"none","summary":"An out-of-bounds write in PeaZip allows attackers to execute arbitrary code by tricking users into opening a crafted .pea archive.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Secur0","cpe":[],"cvss":{"score":8.4,"severity":"high","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-787","name":"Out-of-bounds Write"},{"id":"CWE-1284","name":"Improper Validation of Specified Quantity in Input"},{"id":"CWE-125","name":"Out-of-bounds Read"}],"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).","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Out-of-bounds write in PeaZip PEA extractor allows code execution via a crafted .pea archive","id":"CVE-2026-102514","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"lib0 `readFromDataView` out-of-bounds read","id":"CVE-2026-102521"},"packages":[],"prev":{"headline":"Server-side request forgery in Apache PLC4X","id":"CVE-2026-102511"},"products":["PeaZip"],"published":"2026-10-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-14","vendors":["PeaZip"]},"summary":"An out-of-bounds write in PeaZip allows attackers to execute arbitrary code by tricking users into opening a crafted .pea archive.","url":"https://insights.sbomify.com/CVE-2026-102514/"}