Arbitrary file write via unsanitized attachment filename
Published Mar 7, 2026 · Updated Mar 7, 2026
Path traversal in the eml_parser example script before 2.0.1 allows attackers to write files via crafted attachment filenames. The script joins each untrusted attachment filename directly to the output path, then opens the resulting path for binary writing without normalization or a boundary check. An operator must process an attacker-supplied EML with the example script, and writes remain limited to filesystem locations permitted to that process.
Summary
What happened
Path traversal in the eml_parser example script before 2.0.1 allows attackers to write files via crafted attachment filenames. The script joins each untrusted attachment filename directly to the output path, then opens the resulting path for binary writing without normalization or a boundary check. An operator must process an attacker-supplied EML with the example script, and writes remain limited to filesystem locations permitted to that process.
The record
- CVE
- CVE-2026-29780
- Published
- Mar 7, 2026
- Updated
- Mar 7, 2026
- Vendor
- GOVCERT.LU
- Product
- eml_parser
- Classifications
- CWE-22, CAPEC-126, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 7, 2026CVE publishedPublication date reported by the CVE source.
- Mar 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.0.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-389r-rccm-h3h5 proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo