{"items":[{"id":"NVI-00014170","kind":"vulnerability","title":"eml_parser has parser DoS via deeply nested parentheses in e-mail headers","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-m66c-fw79-6359","CVE-2026-55619"],"plain_summary":"GitHub lists this reviewed advisory for eml_parser. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-0bdb4777dd2d8dfdcf621a1dc296fb9b"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-08-25T18:25:49.000Z","value":"5.3 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-5484d18e89a6e6b364bb03015a619e2c"},{"kind":"EPSS","as_of":"2026-11-05T12:03:04.000Z","value":"0.524%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.44577. Missing scores are unknown.","source_id":"sr-0bdb4777dd2d8dfdcf621a1dc296fb9b"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-5484d18e89a6e6b364bb03015a619e2c","url":"https://github.com/advisories/GHSA-m66c-fw79-6359","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-m66c-fw79-6359","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T09:56:37.775Z"},{"id":"sr-0bdb4777dd2d8dfdcf621a1dc296fb9b","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2026-55619","publisher":"FIRST EPSS","observed_at":"2026-11-06T07:17:46.387Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5484d18e89a6e6b364bb03015a619e2c"],"technology":"eml_parser","known_exclusions":[],"conditions_summary":"### Summary\n\n`eml_parser` uses the `email.utils.getaddresses()` function from the CPython standard library to parse e-mail headers that contain e-mail addresses (such as `To`, `Cc`, `Bcc`, `From`, `Reply-To`, `Sender`, ...). When the input header contains a deeply nested CFWS (comment / folding white space) construct, the recursive descent parser in the standard library exhausts the call stack. The resulting `RecursionError` is not caught by `eml_parser`, so the exception propagates and aborts parsing of the whole message.\n\n### Impact\n\nSOC pipelines use `eml_parser` to process untrusted e-mails. An attacker can easily create an eml file that will trigger the `RecursionError` during parsing.\n\nThe impact is mitigated by the fact that there are various other situations in which `eml_parser` will raise an exception when attempting to parse a malformed or pathological eml file. In particular, very deeply nested multipart e-mails also result in a `RecursionError` being raised by the library voluntarily. Therefore, systems relying on `eml_parser` already need to detect and handle errors emanating from the library in an appropriate way.\n\n### Workarounds\n\nThe issue can be avoided by wrappin","public_affected_ranges":["< 3.0.2"]}],"null_published_at":"2026-11-08T15:11:49.424Z","source_updated_at":"2026-08-25T18:25:49.000Z","source_disclosed_at":"2026-08-25T18:25:47.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-11-02T09:56:37.775Z"},{"id":"NVI-00014170","kind":"vulnerability","title":"eml_parser has parser DoS via deeply nested parentheses in e-mail headers","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-m66c-fw79-6359","CVE-2026-55619"],"plain_summary":"GitHub lists this reviewed advisory for eml_parser. Published version ranges and source prerequisites are shown below; this is not an inspection of a visitor’s application.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-5484d18e89a6e6b364bb03015a619e2c"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-08-25T18:25:49.000Z","value":"5.3 medium","meaning":"GitHub source severity; exploitability and local consequence require separate evidence.","source_id":"sr-5484d18e89a6e6b364bb03015a619e2c"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-5484d18e89a6e6b364bb03015a619e2c","url":"https://github.com/advisories/GHSA-m66c-fw79-6359","basis":"vendor_advisory","notes":"GitHub Advisory Database; CC-BY-4.0. Each advisory links its original attribution. Null normalizes fields.","title":"GHSA-m66c-fw79-6359","publisher":"GitHub Advisory Database","observed_at":"2026-11-02T09:56:37.775Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-5484d18e89a6e6b364bb03015a619e2c"],"technology":"eml_parser","known_exclusions":[],"conditions_summary":"### Summary\n\n`eml_parser` uses the `email.utils.getaddresses()` function from the CPython standard library to parse e-mail headers that contain e-mail addresses (such as `To`, `Cc`, `Bcc`, `From`, `Reply-To`, `Sender`, ...). When the input header contains a deeply nested CFWS (comment / folding white space) construct, the recursive descent parser in the standard library exhausts the call stack. The resulting `RecursionError` is not caught by `eml_parser`, so the exception propagates and aborts parsing of the whole message.\n\n### Impact\n\nSOC pipelines use `eml_parser` to process untrusted e-mails. An attacker can easily create an eml file that will trigger the `RecursionError` during parsing.\n\nThe impact is mitigated by the fact that there are various other situations in which `eml_parser` will raise an exception when attempting to parse a malformed or pathological eml file. In particular, very deeply nested multipart e-mails also result in a `RecursionError` being raised by the library voluntarily. Therefore, systems relying on `eml_parser` already need to detect and handle errors emanating from the library in an appropriate way.\n\n### Workarounds\n\nThe issue can be avoided by wrappin","public_affected_ranges":["< 3.0.2"]}],"null_published_at":"2026-11-02T10:00:37.217Z","source_updated_at":"2026-08-25T18:25:49.000Z","source_disclosed_at":"2026-08-25T18:25:47.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-11-02T09:56:37.775Z"}],"next_cursor":null,"snapshot_revision":"42594"}