Internationalized Domain Names in Applications (IDNA): Specially crafted inputs to idna.encode() can bypass CVE-2024-3651 fix
Noroxi assessment
Priority: Monitor (action score 27/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.45% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: python3-idna (AlmaLinux:10) 3.7-6.el10_2; python3-idna (AlmaLinux:8) 2.5-8.el8_10; python3-idna (AlmaLinux:9) 2.10-8.el9_8.
Low priority for now. Upgrade to python3-idna (AlmaLinux:10) 3.7-6.el10_2; python3-idna (AlmaLinux:8) 2.5-8.el8_10; python3-idna (AlmaLinux:9) 2.10-8.el9_8 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- GHSA-65pc-fj4g-8rjx
- ALSA-2026:54290
- ALSA-2026:54481
- ALSA-2026:54484
- openSUSE-SU-2026:10829-1
- openSUSE-SU-2026:21048-1
- PYSEC-2026-215
- RHSA-2026:25039
- RHSA-2026:25503
- RHSA-2026:26223
- RHSA-2026:34119
- RHSA-2026:54290
- RHSA-2026:54481
- RHSA-2026:54484
- RLSA-2026:54290
- RLSA-2026:54481
- RLSA-2026:54484
- SUSE-SU-2026:22271-1
- SUSE-SU-2026:22356-1
- SUSE-SU-2026:2828-1
- Published
- Jun 5, 2026
- Updated
- Jul 23, 2026
- EPSS
- 0.4% · 38th percentile
- CWE
- CWE-1333
Report tools
Action score
27
Monitor
Low priority for now.
- CVSS
- 27 / 40 · 6.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · GitHub_M
- 6.9
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| kjd | internationalized domain names in applications | cpe:2.3:a:kjd:internationalized_domain_names_in_applications |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- kjd internationalized domain names in applicationsbefore 3.15
Versions reported by the vendor
Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.
kjd idna
- < 3.15affected
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| AlmaLinux:10 | python3-idna | before 3.7-6.el10_2 | 3.7-6.el10_2 |
| AlmaLinux:8 | python3-idna | before 2.5-8.el8_10 | 2.5-8.el8_10 |
| AlmaLinux:9 | python3-idna | before 2.10-8.el9_8 | 2.10-8.el9_8 |
| Debian:12 | python-idna | from 0 | — |
| Debian:13 | python-idna | before 3.10-1+deb13u1 | 3.10-1+deb13u1 |
| Debian:14 | python-idna | before 3.11-1.1 | 3.11-1.1 |
| openSUSE:Leap 16.0 | python-idna | before 3.10-160000.3.1 | 3.10-160000.3.1 |
| openSUSE:Tumbleweed | python-idna | before 3.15-1.1 | 3.15-1.1 |
| PyPI | idna | before 3.15 | 3.15 |
| Red Hat:enterprise_linux:10.2 | python-idna | before 0:3.7-6.el10_2 | 0:3.7-6.el10_2 |
| Red Hat:enterprise_linux:10.2 | python3-idna | before 0:3.7-6.el10_2 | 0:3.7-6.el10_2 |
| Red Hat:enterprise_linux:8::baseos | python-idna | before 0:2.5-8.el8_10 | 0:2.5-8.el8_10 |
| Red Hat:enterprise_linux:8::baseos | python3-idna | before 0:2.5-8.el8_10 | 0:2.5-8.el8_10 |
| Red Hat:enterprise_linux:9::baseos | python-idna | before 0:2.10-8.el9_8 | 0:2.10-8.el9_8 |
| Red Hat:enterprise_linux:9::baseos | python3-idna | before 0:2.10-8.el9_8 | 0:2.10-8.el9_8 |
| Red Hat:hummingbird:1 | jaeger | before 0:2.19.0-1.hum1 | 0:2.19.0-1.hum1 |
| Red Hat:hummingbird:1 | python-idna | before 0:3.18-1.hum1 | 0:3.18-1.hum1 |
| Red Hat:hummingbird:1 | python-jsonschema | before 0:4.26.0-9.hum1 | 0:4.26.0-9.hum1 |
| Red Hat:hummingbird:1 | python-rpds-py | before 0:2026.6.3-1.hum1 | 0:2026.6.3-1.hum1 |
| Red Hat:hummingbird:1 | python3-idna | before 0:3.18-1.hum1 | 0:3.18-1.hum1 |
| Red Hat:hummingbird:1 | python3-jsonschema+format | before 0:4.26.0-9.hum1 | 0:4.26.0-9.hum1 |
| Red Hat:hummingbird:1 | python3-rpds-py | before 0:2026.6.3-1.hum1 | 0:2026.6.3-1.hum1 |
| Rocky Linux:10 | python-idna | before 0:3.7-6.el10_2 | 0:3.7-6.el10_2 |
| Rocky Linux:8 | python-idna | before 0:2.5-8.el8_10 | 0:2.5-8.el8_10 |
+96
Same product
kjd: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-3651Denial of Service via Quadratic Complexity in kjd/idna30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| almalinux:python3-idna | 2.5-8.el8_10 · AlmaLinux:8 | Package registry (OSV) |
| debian:python-idna | 3.10-1+deb13u1 · Debian:13 | Package registry (OSV) |
| opensuse:python-idna | 3.15-1.1 · openSUSE:Tumbleweed | Package registry (OSV) |
| PyPI:idna | 3.15 | Package registry (OSV) |
| red hat:jaeger | 0:2.19.0-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:python-idna | 0:3.18-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:python-jsonschema | 0:4.26.0-9.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:python-rpds-py | 0:2026.6.3-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:python3-idna | 0:3.18-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:python3-jsonschema+format | 0:4.26.0-9.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| red hat:python3-rpds-py | 0:2026.6.3-1.hum1 · Red Hat:hummingbird:1 | Package registry (OSV) |
| rocky linux:python-idna | 0:2.5-8.el8_10 · Rocky Linux:8 | Package registry (OSV) |
| suse:python-idna | 3.10-160000.3.1 · SUSE:Linux Micro 6.2 | Package registry (OSV) |
| suse:saltbundlepy | 3.11.15-100002.1.9.1 · SUSE:EL-10:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
| suse:saltbundlepy-cffi | 1.17.1-100002.1.6.2 · SUSE:EL-10:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
| suse:saltbundlepy-core | 3.11.15-100002.1.9.1 · SUSE:EL-10:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
| suse:saltbundlepy-cryptography | 3.3.2-100002.1.6.2 · SUSE:EL-10:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
| suse:saltbundlepy-cssselect | 1.3.0-100002.1.6.2 · SUSE:EL-10:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
| suse:saltbundlepy-editables | 0.5-100002.1.6.2 · SUSE:EL-10:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
| suse:saltbundlepy-exceptiongroup | 1.2.2-100002.1.6.2 · SUSE:EL-10:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
| suse:saltbundlepy-exceptiongroup-test | 1.2.2-100002.1.6.2 · SUSE:EL-10:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
| suse:saltbundlepy-flit-core | 3.12.0-100002.1.6.1 · SUSE:EL-10:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
| suse:saltbundlepy-hatch-fancy-pypi-readme | 25.1.0-100002.1.6.1 · SUSE:EL-10:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
| suse:saltbundlepy-hatch-fancy-pypi-readme-test | 25.1.0-100002.1.6.1 · SUSE:EL-10:Update:Products:MultiLinuxManagerTools:Update | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
No nightly-computed relations.
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-1333 · Inefficient Regular Expression ComplexityCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
—
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.