NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🦀 crates.io
Not in CISA KEV

`idna` accepts Punycode labels that do not produce any non-ASCII when decodedGHSA-h97m-ww89-6jmq

GHSA-h97m-ww89-6jmq is a CWE-1289 vulnerability in idna. A fix is available for idna — see the affected versions and patch details below.

Also known asCVE-2024-12224RUSTSEC-2024-0421
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

  • CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for GHSA-h97m-ww89-6jmq.

EPSS Exploitation Probability

via FIRST.org ↗
0.2%probability of exploitation in next 30 days
Lower Risk+0.01%
Lower risk than most CVEs14th percentile — riskier than 14% of all scored CVEsHighest risk
0.00%0.24%0.49%0.73%0.2%0.2%0.2%0.2%0.2%May 26Aug 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected
🦀idna

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects crates.io packages — download data is not available via public APIs for these ecosystems.

Description

idna 0.5.0 and earlier accepts Punycode labels that do not produce any non-ASCII output, which means that either ASCII labels or the empty root label can be masked such that they appear unequal without IDNA processing or when processed with a different implementation and equal when processed with idna 0.5.0 or earlier.

Concretely, example.org and xn--example-.org become equal after processing by idna 0.5.0 or earlier. Also, example.org.xn-- and example.org. become equal after processing by idna 0.5.0 or earlier.

In applications using idna (but not in idna itself) this may be able to lead to privilege escalation when host name comparison is part of a privilege check and the behavior is combined with a client that resolves domains with such labels instead of treating them as errors that preclude DNS resolution / URL fetching and with the attacker managing to introduce a DNS entry (and TLS certificate) for an xn---masked name that turns into the name of the target when processed by idna 0.5.0 or earlier.

Remedy

Upgrade to idna 1.0.3 or later, if depending on idna directly, or to url 2.5.4 or later, if depending on idna via url. (This issue was fixed in idna 1.0.0, but versions earlier than 1.0.3 are not recommended for other reasons.)

When upgrading, please take a moment to read about alternative Unicode back ends for idna.

If you are using Rust earlier than 1.81 in combination with SQLx 0.8.2 or earlier, please also read an issue about combining them with url 2.5.4 and idna 1.0.3.

Additional information

This issue resulted from idna 0.5.0 and earlier implementing the UTS 46 specification literally on this point and the specification having this bug. The specification bug has been fixed in revision 33 of UTS 46.

Acknowledgements

Thanks to kageshiron for recognizing the security implications of this behavior.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🦀crates.ioidnaall versions1.0.0cargo update -p idna --precise 1.0.0

Affected Products

1 product · 1 configurations
Application
idnaservo
< 1.0.0
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for idna, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update idna to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h97m-ww89-6jmq is resolved across your whole dependency graph.

  3. Workarounds

    Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatModerate

This issue was rated as moderate because certain hostnames can be interpreted incorrectly by idna, potentially allowing an attacker to bypass hostname checks. Exploitation requires specific conditions, such as a client accepting unusual domain names and an attacker controlling a matching DNS entry. While it could…

Workaround published by Red Hat
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability.
Source: Red Hat security advisory for GHSA-h97m-ww89-6jmq (CC BY 4.0)
ProductFixed inAdvisory
Red Hat Enterprise Linux 10firefox-0:140.3.0-1.el10_0RHSA-2025:16109
Red Hat Enterprise Linux 10thunderbird-0:140.3.0-1.el10_0RHSA-2025:16157
Red Hat Enterprise Linux 7 Extended Lifecycle Supportfirefox-0:140.3.0-1.el7_9RHSA-2025:17453
Red Hat Enterprise Linux 8firefox-0:140.3.0-1.el8_10RHSA-2025:16260
Red Hat Enterprise Linux 8thunderbird-0:140.3.0-1.el8_10RHSA-2025:16589
Red Hat Enterprise Linux 8.2 Advanced Update Supportthunderbird-0:140.3.0-1.el8_2RHSA-2025:17340
Red Hat Enterprise Linux 8.2 Advanced Update Supportfirefox-0:140.3.0-1.el8_2RHSA-2025:17372
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Supportthunderbird-0:140.3.0-1.el8_4RHSA-2025:17341

Frequently Asked Questions

`idna` 0.5.0 and earlier accepts Punycode labels that do not produce any non-ASCII output, which means that either ASCII labels or the empty root label can be masked such that they appear unequal without IDNA processing or when processed with a different implementation and equal when processed with `idna` 0.5.0 or earlier. Concretely, `example.org` and `xn--example-.org` become equal after processing by `idna` 0.5.0 or earlier. Also, `example.org.xn--` and `example.org.` become equal after processing by `idna` 0.5.0 or earlier. In applications using `idna` (but not in `idna` itself) this may
O3 Security · Impact-Aware SCA

Is GHSA-h97m-ww89-6jmq in your dependencies?

Find it across crates.io, including transitive dependencies.

Scan my dependencies How O3 SCA works
`idna` accepts Punycode labels that do not produce any…