GHSA-XHRQ-2MQV-Q8WX

Vulnerability from github – Published: 2026-11-16 22:20 – Updated: 2026-11-16 22:20
VLAI
Summary
mail-parser: Uncaught `OverflowError` / `OSError` on an out-of-range `Received` date
Details

Impact

A Received header whose trailing date carries an out-of-range year, or a timezone offset large enough to push the timestamp past the int64 epoch range, raises an exception that is outside the MailParser* hierarchy. A caller that catches only mail-parser exceptions does not catch it, and the parse of the entire message is aborted — the same class of issue as GHSA-24mq-4vc6-2prf, which this survives (it is not a duplicate; 24mq is fixed in 4.6.2 and this reproduces on 4.6.2).

All entry points are affected: parse_from_string(), parse_from_bytes(), parse_from_file(), parse_from_file_obj() and the mail-parser CLI. The header is fully attacker-controlled and a single line is enough, so any pipeline that parses untrusted mail can be made to lose the message — and, if one worker handles a queue, to drop the batch.

import mailparser

raw = ("Received: from x ([1.2.3.4]) by mx.victim.com; "
       "Tue, 7 Mar 292277026596 14:29:24 +0000\r\n\r\nbody\r\n")
mailparser.parse_from_string(raw).mail_json
# <= 4.6.2 -> OverflowError: signed integer is greater than maximum
# 4.6.3    -> parses; the unusable hop date is reported as "date_utc": null

Root cause. receiveds_format() in src/mailparser/utils.py guarded the date conversion with except (TypeError, ValueError), but convert_mail_date() → email.utils.mktime_tz() → calendar.timegm() raises OverflowError for years whose epoch seconds overflow int64, and datetime.fromtimestamp() reports EOVERFLOW as OSError for a sufficiently large timezone offset. The date and timezone properties already wrapped the same conversion in except Exception; only the Received path was left open.

Affected range. Introduced by the date-handling change in ca2aa6a, first released in 3.7.0. Reproduced on PyPI 3.7.0, 3.8.0, 3.9.3, 4.0.0, 4.5.0, 4.6.0, 4.6.2 and on master before the fix (Python 3.14). 3.6.0 is not affected.

Patches

Fixed in 4.6.3. receiveds_format() now also catches OverflowError and OSError and records date_utc = None for that hop, so the rest of the message still parses:

try:
    j["date_utc"], _ = convert_mail_date(i["date"])
except (TypeError, ValueError, OverflowError, OSError):
    j["date_utc"] = None

A sweep of year magnitudes from 10^7 to 10^12 shows only ValueError, OverflowError and OSError are reachable on this path.

Workarounds

Upgrade to 4.6.3. If you cannot upgrade, wrap every parse_from_* call in a bare except Exception rather than except MailParserError, and treat the message as unparsed.

References

Show details on source website

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "mail-parser"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "3.7.0"
            },
            {
              "fixed": "4.6.3"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-129300"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-248"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-11-16T22:20:32Z",
    "nvd_published_at": "2026-11-16T18:17:30Z",
    "severity": "MODERATE"
  },
  "details": "### Impact\n\nA `Received` header whose trailing date carries an out-of-range year, or a timezone offset\nlarge enough to push the timestamp past the int64 epoch range, raises an exception that is\n**outside the `MailParser*` hierarchy**. A caller that catches only mail-parser exceptions\ndoes not catch it, and the parse of the entire message is aborted \u2014 the same class of issue\nas [GHSA-24mq-4vc6-2prf](https://github.com/SpamScope/mail-parser/security/advisories/GHSA-24mq-4vc6-2prf),\nwhich this survives (it is not a duplicate; 24mq is fixed in 4.6.2 and this reproduces on 4.6.2).\n\nAll entry points are affected: `parse_from_string()`, `parse_from_bytes()`, `parse_from_file()`,\n`parse_from_file_obj()` and the `mail-parser` CLI. The header is fully attacker-controlled and\na single line is enough, so any pipeline that parses untrusted mail can be made to lose the\nmessage \u2014 and, if one worker handles a queue, to drop the batch.\n\n```python\nimport mailparser\n\nraw = (\"Received: from x ([1.2.3.4]) by mx.victim.com; \"\n       \"Tue, 7 Mar 292277026596 14:29:24 +0000\\r\\n\\r\\nbody\\r\\n\")\nmailparser.parse_from_string(raw).mail_json\n# \u003c= 4.6.2 -\u003e OverflowError: signed integer is greater than maximum\n# 4.6.3    -\u003e parses; the unusable hop date is reported as \"date_utc\": null\n```\n\n**Root cause.** `receiveds_format()` in `src/mailparser/utils.py` guarded the date conversion\nwith `except (TypeError, ValueError)`, but `convert_mail_date()` \u2192 `email.utils.mktime_tz()` \u2192\n`calendar.timegm()` raises `OverflowError` for years whose epoch seconds overflow int64, and\n`datetime.fromtimestamp()` reports `EOVERFLOW` as `OSError` for a sufficiently large timezone\noffset. The `date` and `timezone` properties already wrapped the same conversion in\n`except Exception`; only the `Received` path was left open.\n\n**Affected range.** Introduced by the date-handling change in `ca2aa6a`, first released in\n3.7.0. Reproduced on PyPI 3.7.0, 3.8.0, 3.9.3, 4.0.0, 4.5.0, 4.6.0, 4.6.2 and on `master`\nbefore the fix (Python 3.14). 3.6.0 is not affected.\n\n### Patches\n\nFixed in **4.6.3**. `receiveds_format()` now also catches `OverflowError` and `OSError` and\nrecords `date_utc = None` for that hop, so the rest of the message still parses:\n\n```python\ntry:\n    j[\"date_utc\"], _ = convert_mail_date(i[\"date\"])\nexcept (TypeError, ValueError, OverflowError, OSError):\n    j[\"date_utc\"] = None\n```\n\nA sweep of year magnitudes from 10^7 to 10^12 shows only `ValueError`, `OverflowError` and\n`OSError` are reachable on this path.\n\n### Workarounds\n\nUpgrade to 4.6.3. If you cannot upgrade, wrap every `parse_from_*` call in a bare\n`except Exception` rather than `except MailParserError`, and treat the message as unparsed.\n\n### References\n\n- Fix: https://github.com/SpamScope/mail-parser/pull/171\n- Related: [GHSA-24mq-4vc6-2prf](https://github.com/SpamScope/mail-parser/security/advisories/GHSA-24mq-4vc6-2prf)",
  "id": "GHSA-xhrq-2mqv-q8wx",
  "modified": "2026-11-16T22:20:32Z",
  "published": "2026-11-16T22:20:32Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/SpamScope/mail-parser/security/advisories/GHSA-xhrq-2mqv-q8wx"
    },
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-129300"
    },
    {
      "type": "WEB",
      "url": "https://github.com/SpamScope/mail-parser/pull/171"
    },
    {
      "type": "WEB",
      "url": "https://github.com/SpamScope/mail-parser/commit/d69f6f9b6ad0bf74d731b373bbdeabb462c32b26"
    },
    {
      "type": "WEB",
      "url": "https://github.com/SpamScope/mail-parser/commit/e1d9fe6778045d6e2c44406bc8822e3464c1097f"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/SpamScope/mail-parser"
    },
    {
      "type": "WEB",
      "url": "https://github.com/SpamScope/mail-parser/releases/tag/4.6.3"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L",
      "type": "CVSS_V3"
    }
  ],
  "summary": "mail-parser: Uncaught `OverflowError` / `OSError` on an out-of-range `Received` date"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…