Eml Parser
Approved changes feed: RSS · Atom
cpe:2.3:a:govcert-lu:eml_parser:*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | Govcert Lu (ad299844-7a0e-5296-8f5a-0083f1df3cb6) |
|---|---|
| Product | Eml Parser (3420c1d9-2d21-52c7-9d0c-b68ba0015cde) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-44844 |
vulnerable | 2026-06-08 08:05:11.328135 |
eml_parser: Recursion DoS via nested message/rfc822 attachments
eml_parser serves as a python module for parsing eml files and returning various information found in the e-mail as well as computed information. Prior to 3.0.1, EmlParser.get_raw_body_text() recurses unconditionally for every nested message/rfc822 attachment without any depth limit. An attacker who can supply a badly crafted EML file with approximately 120 nested message/rfc822 parts triggers an unhandled RecursionError and aborts parsing of the message. A 12 KB EML file is enough to crash a worker. Though this causes the parser to crash, it is an unlikely scenario as the suggested EML that crashes the parser would not pass basic RFC compliance tests. This vulnerability is fixed in 3.0.1.
Published: 2026-05-26T19:49:45.723Z
Updated: 2026-05-27T13:41:33.306Z |
Imported from gcve-enriched-dumps CVE data |
CVE:CVE-2026-29780 |
vulnerable | 2026-06-08 07:55:16.279792 |
eml_parser: Path Traversal in Official Example Script Leading to Arbitrary File Write
MEDIUM (5.5)
eml_parser serves as a python module for parsing eml files and returning various information found in the e-mail as well as computed information. Prior to version 2.0.1, 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. This issue has been patched in version 2.0.1.
Published: 2026-03-07T15:22:43.645Z
Updated: 2026-03-09T18:26:58.485Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.