{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-82521 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-82521 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-82521 is a medium-severity path traversal vulnerability in domainaware parsedmarc, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-82521 and fix it if it is affected.\n\nWhat it is: CVE-2026-82521 is a medium-severity path traversal vulnerability in domainaware parsedmarc, published on 3 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-82521 in the wild and no public exploit code.\n\nAffected product: domainaware parsedmarc. 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-82521/ (Markdown: https://insights.sbomify.com/CVE-2026-82521/index.md)","id":"CVE-2026-82521","markdown":"https://insights.sbomify.com/CVE-2026-82521/index.md","name":"CVE-2026-82521","record":{"aliases":["GHSA-c284-w5m6-jhjm"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"DMARC parsing tool","requires_auth":"none","summary":"Attackers can write arbitrary files outside the intended directory via crafted email subjects if forensic report sample output is enabled.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"parsedmarc 9.0.6 before 11.0.1 writes forensic report sample files using an output path derived from the email subject. When the subject consists entirely of path traversal sequences, the filename sanitization function produces an empty string, and a fallback to the raw unsanitized subject causes the resulting file to be written outside the intended samples directory. An attacker who can cause a forensic failure report with a crafted Subject to be processed can write a dot-prefixed file with attacker-controlled content to an ancestor directory of the configured samples output path. Exploitation requires that file output for forensic report samples is enabled.","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":"parsedmarc 9.0.6 \u003c 11.0.1 Path Traversal via Forensic Report Subject","id":"CVE-2026-82521","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"libjxl \u003c 0.12.0 Container Box Parser Integer Underflow via 32-bit Size Truncation","id":"CVE-2026-82522"},"packages":[],"prev":{"headline":"parsedmarc \u003c 11.0.1 Zip Bomb DoS via Compressed Email Attachments","id":"CVE-2026-82520"},"products":["parsedmarc"],"published":"2026-09-03","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":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-14","vendors":["domainaware"]},"summary":"Attackers can write arbitrary files outside the intended directory via crafted email subjects if forensic report sample output is enabled.","url":"https://insights.sbomify.com/CVE-2026-82521/"}