CVE-2026-45409

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 66% 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
Trending — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

A fix is available — apply it.

Internationalized Domain Names in Applications (IDNA) for Python provides support for Internationalized Domain Names in Applications (IDNA) and Unicode IDNA Compatibility Processing. In versions prior to 3.15, payloads such as "\u0660" * N or "\u30fb" * N + "\u6f22" utilize the valid_contexto function prior to length rejection, and for high values of N will take a long time to process. This is the same issue as CVE-2024-3651, however the original remediation in 2024 was not a complete fix. A specially crafted argument to the idna.encode() function could consume significant resources. This may lead to a denial-of-service. Starting in version 3.14, the function rejects long inputs as soon as practicable prior to any further processing to minimize resource consumption. In version 3.15, this approach was extended to lesser used alternate functions (i.e. per-label conversions and codec support). A workaround is available. Domain names cannot exceed 253 characters in length. If this length limit is enforced prior to passing the domain to the idna.encode() function, it should no longer consume significant resources. This is triggered by arbitrarily large inputs that would not occur in normal usage, but may be passed to the library assuming there is no preliminary input validation by the higher-level application.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
39(Track)
EG Risk 39/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

May 19, 2026

Last Modified

July 23, 2026

Advisory Details (1)

Auto-updated Jun 14, 2026
Patch available. Sources: github.
github Patch Available

Specially crafted inputs to idna.encode() can bypass CVE-2024-3651 fix · Advisory · kjd/idna · GitHub

https://github.com/kjd/idna/security/advisories/GHSA-65pc-fj4g-8rjx

Patch Availability(8)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3-idna (3.11-1ubuntu0.1) @ resolute2026-08-23ubuntu
redhatodf4/rook-ceph-rhel9-operator:17867068802026-08-18redhat
redhatpython-idna-0:2.10-8.el9_82026-08-13redhat
redhatpython-idna-0:3.7-6.el10_22026-08-13redhat
redhatpython-idna-0:2.5-8.el8_102026-08-12redhat
redhatpython-rpds-py-main-2026.6.3-1.hum12026-07-01redhat
redhatpython-idna-main-3.18-1.hum12026-06-12redhat
redhatjaeger-main-2.19.0-1.hum12026-06-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.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
python-idna2.10-1 ... 3.8-2 (16 versions)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-idna3.10-1 ... 3.8-2 (13 versions)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-idna3.10-13.10-1+deb13u1
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-idna3.10-1, 3.11-13.11-1.1
PyPI(1)
PackageVulnerable rangeFixed inDependents
idna0.1 ... 3.9 (37 versions)3.15

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

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 11× in last 7d / 61× 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.

Showing the most recent 100 of 127 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-45409?
CVE-2026-45409 is a medium vulnerability published on May 19, 2026. Internationalized Domain Names in Applications (IDNA) for Python provides support for Internationalized Domain Names in Applications (IDNA) and Unicode IDNA Compatibility Processing. In versions prior to 3.15, payloads such as "\u0660" N or "\u30fb" N + "\u6f22" utilize the valid_contexto function…
When was CVE-2026-45409 disclosed?
CVE-2026-45409 was first published in the National Vulnerability Database on May 19, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-45409 actively exploited?
CVE-2026-45409 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 66.3% of all scored CVEs.
What is the CVSS score of CVE-2026-45409?
CVE-2026-45409 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-45409?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-45409, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-45409

Explore →

Is Your Infrastructure Affected by CVE-2026-45409?

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