CVE-2026-82521: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in domainaware parsedmarc
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.
CVSS v4.0
Score 6.3medium
Affected software
domainaware
parsedmarc
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
In parsedmarc versions >=9.0.6 and <11.0.1, a path traversal vulnerability exists in the forensic report sample file writing functionality. The output filename is derived from the email subject, which is sanitized to prevent directory traversal. However, if the subject is composed solely of path traversal sequences, the sanitization results in an empty string, causing a fallback to the unsanitized subject. This fallback allows an attacker to write files outside the intended samples directory, potentially placing dot-prefixed files with attacker-controlled content in ancestor directories. Exploitation requires that forensic report sample file output is enabled and that an attacker can trigger a forensic failure report with a crafted subject.
Potential Impact
An attacker able to cause a forensic failure report with a crafted email subject can write files outside the intended directory, potentially overwriting or creating files in ancestor directories. This could lead to unauthorized file creation or modification on the system running parsedmarc. The vulnerability does not require privileges or user interaction but does require the forensic report sample output feature to be enabled. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is applied, consider disabling forensic report sample file output to prevent exploitation. Monitor vendor communications for an official fix or update to parsedmarc versions that address this vulnerability.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-29T17:20:57.081Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a99de23acd9273b497230b5
Added to database: 09/03/2026, 20:52:51 UTC
Last enriched: 09/14/2026, 23:27:23 UTC
Last updated: 10/17/2026, 18:48:23 UTC
Views: 82
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.