Path Traversal in eml-parser (CVE-2026-29780)
Summary
Path traversal in eml-parser (CVE-2026-29780). Data can be tampered with by attackers. Mitigation: upgrade to 2.0.1 or later.
Original description
The description as published by the source.
Summary
The official example script examples/recursively_extract_attachments.py contains a path traversal vulnerability that allows arbitrary file write outside the intended output directory. Attachment filenames extracted from parsed emails are directly used to construct output file paths without any sanitization, allowing an attacker-controlled filename to escape the target directory.
Details
File: examples/recursively_extract_attachments.py
Lines: 61–64
for a in m['attachment']:
out_filepath = out_path / a['filename'] # No sanitization
print(f'\tWriting attachment: {out_filepath}')
with out_filepath.open('wb') as a_out:
a_out.write(base64.b64decode(a['raw']))
The value a['filename'] is attacker-controlled via crafted email attachment headers:
Content-Disposition: attachment; filename="../outside/pwned.txt"
No path normalization or boundary validation is performed before writing.
PoC
- Create a malicious
.emlfile:
Content-Disposition: attachment; filename="../outside/pwned.txt"
- Run the example script:
python recursively_extract_attachments.py -p ./emails -o ./safe
- Expected:
./safe/pwned.txt - Actual:
./outside/pwned.txt← written outside the intended directory
Verified on Kali Linux with eml_parser installed via pip in a virtual environment.
Impact
This vulnerability is limited to the example script only and does not affect the core eml_parser library. However, as the…
Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-29780 has been found in eml-parser.
Data can be tampered with by attackers.
What to do: upgrade eml-parser to 2.0.1 or later.
If unsure, ask your IT team or search "eml-parser CVE-2026-29780" on the vendor's site.
CVE-2026-29780 (eml-parser) — CWE-22
Attack vector: local / unauthenticated
Patched: 2.0.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Path traversal (CWE-22) exists in eml-parser.
Check the vendor advisory for the affected versions of eml-parser.
Severity: ?. Data can be tampered with by attackers.
Update to 2.0.1.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'eml-parser' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'eml-parser' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
eml-parserを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade eml-parser to 2.0.1ステージング環境で 2.0.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com