{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-33026 exists.","fix":"No fix has been published for CVE-2025-33026 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-33026 is a medium-severity vulnerability in PeaZip, published on 15 Apr 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-33026 and fix it if it is affected.\n\nWhat it is: CVE-2025-33026 is a medium-severity vulnerability in PeaZip, published on 15 Apr 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-33026 exists.\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-2025-33026/ (Markdown: https://insights.sbomify.com/CVE-2025-33026/index.md)","id":"CVE-2025-33026","markdown":"https://insights.sbomify.com/CVE-2025-33026/index.md","name":"CVE-2025-33026","record":{"aliases":["GHSA-vg6j-x3v7-mwq9"],"analysis":{"component_type":"desktop_application","fix_type":"no_fix_stated","impacts":["code_execution","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"PeaZip archive utility","requires_auth":"none","summary":"Attackers can bypass Mark-of-the-Web protections in PeaZip to execute arbitrary code by tricking users into opening crafted archives.","user_interaction":"required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"peazip","vendor":"peazip"}],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-829","name":"Inclusion of Functionality from Untrusted Control Sphere"},{"id":"CWE-830","name":"Inclusion of Web Functionality from an Untrusted Source"}],"description":"In PeaZip through 10.4.0, there is a Mark-of-the-Web Bypass Vulnerability. This vulnerability allows attackers to bypass the Mark-of-the-Web protection mechanism on affected installations of PeaZip. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the handling of archived files. When extracting files from a crafted archive that bears the Mark-of-the-Web, PeaZip does not propagate the Mark-of-the-Web to the extracted files. An attacker can leverage this vulnerability to execute arbitrary code in the context of the current user. NOTE: this is disputed because Mark-of-the-Web propagation can increase risk via security-warning habituation, and because the intended control sphere for file-origin metadata (e.g., HostUrl in Zone.Identifier) may be narrower than that for reading the file's content.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Security feature bypass in PeaZip","id":"CVE-2025-33026","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Security feature bypass in Bandizip","id":"CVE-2025-33027"},"packages":[],"prev":{"headline":"Command injection in RUGGEDCOM ROX MX5000","id":"CVE-2025-33025"},"products":["PeaZip"],"published":"2025-04-15","related":[{"cvss_score":5.3,"headline":"PeaZip Library dragdropfilesdll.dll uncontrolled search path","id":"CVE-2023-6891","kev_date_added":null,"published":"2023-12-17"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-10-24","vendors":["PeaZip"]},"summary":"Attackers can bypass Mark-of-the-Web protections in PeaZip to execute arbitrary code by tricking users into opening crafted archives.","url":"https://insights.sbomify.com/CVE-2025-33026/"}