CVE-2026-82521: parsedmarc 9.0.6 < 11.0.1 Path Traversal via Forensic Report Subject

Published Sep 3, 2026
·
Updated

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.

Affected Software

1 affected component
parsedmarc>=9.0.6<11.0.1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade parsedmarc to a version that resolves this vulnerability.

    Fixed in 11.0.1
  2. Configuration

    Disable file output for forensic report samples so that crafted Subject data cannot be written to the configured samples output path.

    parsedmarc forensic report sample file output (enabled/disabled) = disabled

Event History

Sep 3, 2026
CVE Published
via MITRE·08:41 PM
Data Sourced
via MITRE·08:41 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

Deployments running parsedmarc 9.0.6 through versions before 11.0.1 are affected only when file output for forensic report samples is enabled. The issue applies to processing forensic failure reports.

2

What does an attacker need to do to exploit it?

An attacker must be able to cause a forensic failure report with a crafted Subject consisting entirely of path traversal sequences to be processed. No authentication or user interaction is indicated by the provided severity vector.

3

What can an attacker write, and where?

Successful exploitation can write a dot-prefixed file with attacker-controlled content to an ancestor directory of the configured samples output path. The write occurs because an empty sanitized filename falls back to the raw Subject value.

4

What mitigation is available if upgrading cannot happen immediately?

Disable file output for forensic report samples. Exploitation requires this output feature to be enabled.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203