CVE-2026-1299

MEDIUMNVD 6.06.0—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 6.0 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 83% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
6.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 1%CVSS: 6.0Exploit: NoneExposed: 0

A fix is available — apply it.

The email module, specifically the "BytesGenerator" class, didn’t properly quote newlines for email headers when serializing an email message allowing for header injection when an email is serialized. This is only applicable if using "LiteralHeader" writing headers that don't respect email folding rules, the new behavior will reject the incorrectly folded headers in "BytesGenerator".

CVSS v3
6.0
EG Score
6.0(medium)
EPSS
42.8%
KEV
Not listed

Published

January 23, 2026

Last Modified

April 15, 2026

References (10)

Vendor Advisories for CVE-2026-1299(20)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(30)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhaiis/vllm-spyre-rhel9:17782445462026-05-12redhat
redhatrhaiis/model-opt-cuda-rhel9:17757498572026-04-17redhat
redhatrhaiis/vllm-cuda-rhel9:17756801922026-04-17redhat
redhatrhaiis/vllm-rocm-rhel9:17756802622026-04-17redhat
redhatpython3-11-main-3.11.15-4.hum12026-04-17redhat
redhatpython3-12-main-3.12.13-3.hum12026-04-17redhat
redhatpython3-14-main-3.14.4-1.hum12026-04-11redhat
redhatpython3-13-main-3.13.13-1.hum12026-04-10redhat
redhatdiscovery/discovery-ui-rhel9:17756759222026-04-09redhat
redhatpython3-0:3.6.8-21.el7_9.42026-04-02redhat
redhatpython3.11-0:3.11.7-1.el9_4.112026-03-31redhat
redhatpython3-0:3.6.8-51.el8_8.132026-03-30redhat
redhatrhceph/rhceph-8-rhel9:17740028672026-03-24redhat
redhatpython3.9-0:3.9.16-1.el9_2.122026-03-23redhat
redhatpython3.9-0:3.9.10-4.el9_0.92026-03-23redhat
redhatpython3.12-0:3.12.1-4.el9_4.112026-03-23redhat
redhatpython3.9-0:3.9.21-2.el9_6.42026-03-23redhat
redhatpython3-0:3.6.8-39.el8_4.92026-03-23redhat
redhatpython3-0:3.6.8-47.el8_6.112026-03-23redhat
redhatpython3.11-0:3.11.2-2.el9_2.102026-03-23redhat
redhatpython3.12-0:3.12.9-2.el10_0.72026-03-23redhat
redhatpython3-0:3.6.8-24.el8_2.62026-03-23redhat
redhatpython3.9-0:3.9.18-3.el9_4.112026-03-23redhat
redhatpython3.11-0:3.11.2-2.el8_8.82026-03-19redhat
redhatrhui5/rhua-rhel9:17736701372026-03-18redhat
redhatpython3.12-0:3.12.12-3.el10_1.12026-03-17redhat
redhatpython3.12-0:3.12.9-1.el9_6.62026-03-17redhat
redhatpython3.12-0:3.12.12-3.el8_102026-03-12redhat
redhatpython3.11-0:3.11.13-5.el8_102026-03-12redhat
redhatpython3.9-0:3.9.25-3.el9_7.12026-03-10redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(13)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 9× in last 7d / 39× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-16 17:02 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-13 22:30 UTCEPSS rescore
  5. 2026-07-13 15:07 UTCOSV refresh
  6. 2026-07-13 06:12 UTCEPSS rescore
  7. 2026-07-12 05:46 UTCEPSS rescore
  8. 2026-07-11 08:27 UTCEPSS rescore
  9. 2026-07-09 19:10 UTCEPSS rescore
  10. 2026-07-08 15:15 UTCEPSS rescore
  11. 2026-07-08 15:15 UTCEPSS rescore
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 02:23 UTCEPSS rescore
  15. 2026-07-05 02:30 UTCEPSS rescore
  16. 2026-07-05 02:30 UTCEPSS rescore
  17. 2026-07-04 06:31 UTCEPSS rescore
  18. 2026-07-01 15:06 UTCEPSS rescore
  19. 2026-07-01 15:06 UTCEPSS rescore
  20. 2026-06-30 23:22 UTCEPSS rescore
  21. 2026-06-29 14:06 UTCEPSS rescore
  22. 2026-06-28 14:07 UTCEPSS rescore
  23. 2026-06-28 04:56 UTCEPSS rescore
  24. 2026-06-28 04:56 UTCEPSS rescore
  25. 2026-06-27 03:08 UTCEPSS rescore
Show 74 more
  1. 2026-06-25 13:49 UTCEPSS rescore
  2. 2026-06-25 12:31 UTCOSV refresh
  3. 2026-06-24 14:05 UTCEPSS rescore
  4. 2026-06-23 21:32 UTCEPSS rescore
  5. 2026-06-22 14:25 UTCEPSS rescore
  6. 2026-06-22 14:25 UTCEPSS rescore
  7. 2026-06-21 14:56 UTCEPSS rescore
  8. 2026-06-21 14:56 UTCEPSS rescore
  9. 2026-06-21 01:59 UTCEPSS rescore
  10. 2026-06-21 01:59 UTCEPSS rescore
  11. 2026-06-19 19:25 UTCEPSS rescore
  12. 2026-06-18 17:52 UTCEPSS rescore
  13. 2026-06-17 17:53 UTCEPSS rescore
  14. 2026-06-16 17:52 UTCEPSS rescore
  15. 2026-06-15 17:48 UTCEPSS rescore
  16. 2026-06-14 23:18 UTCEPSS rescore
  17. 2026-06-13 23:00 UTCEPSS rescore
  18. 2026-06-13 23:00 UTCEPSS rescore
  19. 2026-06-12 23:12 UTCEPSS rescore
  20. 2026-06-11 14:00 UTCEPSS rescore
  21. 2026-06-10 22:18 UTCEPSS rescore
  22. 2026-06-10 13:22 UTCEPSS rescore
  23. 2026-06-08 14:17 UTCEPSS rescore
  24. 2026-06-08 14:17 UTCEPSS rescore
  25. 2026-06-08 03:28 UTCEG score recompute▲ 6.00
  26. 2026-06-08 03:28 UTCVendor advisory
  27. 2026-06-08 03:28 UTCGHSA enrichment
  28. 2026-06-07 15:25 UTCEPSS rescore
  29. 2026-06-07 15:24 UTCEPSS rescore
  30. 2026-06-06 13:47 UTCEPSS rescore
  31. 2026-06-06 13:47 UTCEPSS rescore
  32. 2026-06-06 13:47 UTCEPSS rescore
  33. 2026-06-05 22:47 UTCEPSS rescore
  34. 2026-06-05 06:10 UTCEPSS rescore
  35. 2026-06-05 06:10 UTCEPSS rescore
  36. 2026-06-04 13:12 UTCEPSS rescore
  37. 2026-06-04 13:12 UTCEPSS rescore
  38. 2026-06-04 13:12 UTCEPSS rescore
  39. 2026-06-02 20:13 UTCEPSS rescore
  40. 2026-06-02 20:13 UTCEPSS rescore
  41. 2026-06-01 16:57 UTCOSV refresh
  42. 2026-06-01 13:51 UTCEPSS rescore
  43. 2026-06-01 13:51 UTCEPSS rescore
  44. 2026-06-01 13:51 UTCEPSS rescore
  45. 2026-05-31 22:30 UTCEPSS rescore
  46. 2026-05-31 22:30 UTCEPSS rescore
  47. 2026-05-31 00:16 UTCEPSS rescore
  48. 2026-05-31 00:16 UTCEPSS rescore
  49. 2026-05-31 00:16 UTCEPSS rescore
  50. 2026-05-29 13:44 UTCEPSS rescore
  51. 2026-05-29 13:44 UTCEPSS rescore
  52. 2026-05-28 13:44 UTCEPSS rescore
  53. 2026-05-28 13:44 UTCEPSS rescore
  54. 2026-05-28 13:44 UTCEPSS rescore
  55. 2026-05-27 13:40 UTCEPSS rescore
  56. 2026-05-27 13:40 UTCEPSS rescore
  57. 2026-05-27 13:40 UTCEPSS rescore
  58. 2026-05-26 13:44 UTCEPSS rescore
  59. 2026-05-26 13:44 UTCEPSS rescore
  60. 2026-05-26 07:18 UTCEPSS rescore
  61. 2026-05-26 07:18 UTCEPSS rescore
  62. 2026-05-26 07:18 UTCEPSS rescore
  63. 2026-05-22 21:16 UTCEPSS rescore
  64. 2026-05-21 22:43 UTCEPSS rescore
  65. 2026-05-21 00:08 UTCEG score recompute
  66. 2026-05-21 00:08 UTCVendor advisory
  67. 2026-05-21 00:08 UTCGHSA enrichment
  68. 2026-05-20 22:38 UTCEPSS rescore
  69. 2026-05-20 22:37 UTCEPSS rescore
  70. 2026-05-20 22:37 UTCEPSS rescore
  71. 2026-05-20 11:22 UTCEPSS rescore
  72. 2026-05-20 11:21 UTCEPSS rescore
  73. 2026-05-20 11:21 UTCEPSS rescore
  74. 2026-05-18 21:31 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-1299?
CVE-2026-1299 is a medium vulnerability published on January 23, 2026. The email module, specifically the "BytesGenerator" class, didn’t properly quote newlines for email headers when serializing an email message allowing for header injection when an email is serialized. This is only applicable if using "LiteralHeader" writing headers that don't respect email folding…
When was CVE-2026-1299 disclosed?
CVE-2026-1299 was first published in the National Vulnerability Database on January 23, 2026, with the most recent update on April 15, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-1299 actively exploited?
CVE-2026-1299 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 42.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-1299?
CVE-2026-1299 has a CVSS v3 base score of 6.0 (NVD).
How do I remediate CVE-2026-1299?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-1299, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-1299

Explore →

Is Your Infrastructure Affected by CVE-2026-1299?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs