How severe is CVE-2024-12224?

No CVSS score has been assigned to CVE-2024-12224 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-12224?

CVE-2024-12224 affects the following packages: idna (crates.io). Ecosystems affected: crates.io.

How do I fix CVE-2024-12224?

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

How do I detect CVE-2024-12224 in my crates.io dependencies?

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.

How do I mitigate CVE-2024-12224 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2024-12224?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-12224 can be triaged on real exposure rather than presence alone.

Is CVE-2024-12224 actively exploited in the wild?

No public exploit code has been indexed for CVE-2024-12224 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2024-12224?

CVE-2024-12224 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 13th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-12224?

CVE-2024-12224 is classified as CWE-1289 (CWE-1289), Cross-Site Request Forgery (CSRF) (CWE-352). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2024-12224 published, and has it been updated?

CVE-2024-12224 was published on May 30, 2025 and was last updated on August 14, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🦀 crates.io

Not in CISA KEV

CVE-2024-12224 — idna

CVE-2024-12224 is a CWE-1289 vulnerability in idna. A fix is available for idna — see the affected versions and patch details below.

idna accepts Punycode labels that do not produce any non-ASCII when decoded

Also known asGHSA-h97m-ww89-6jmqRUSTSEC-2024-0421

Published

May 30, 2025

Updated

Aug 14, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 22, 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 CVE-2024-12224.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs13th percentile — riskier than 13% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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

Ecosystem	Package	Vulnerable range	Fix
🦀crates.io	`idna`	all versions	1.0.0`cargo update -p idna --precise 1.0.0`

Detection & mitigation playbook

Open-source dependency

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.
Fix
Update idna to 1.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-12224 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-12224 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2024-12224. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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…

Product	Fixed in	Advisory
Red Hat Enterprise Linux 10	`firefox-0:140.3.0-1.el10_0`	RHSA-2025:16109
Red Hat Enterprise Linux 10	`thunderbird-0:140.3.0-1.el10_0`	RHSA-2025:16157
Red Hat Enterprise Linux 7 Extended Lifecycle Support	`firefox-0:140.3.0-1.el7_9`	RHSA-2025:17453
Red Hat Enterprise Linux 8	`firefox-0:140.3.0-1.el8_10`	RHSA-2025:16260
Red Hat Enterprise Linux 8	`thunderbird-0:140.3.0-1.el8_10`	RHSA-2025:16589
Red Hat Enterprise Linux 8.2 Advanced Update Support	`thunderbird-0:140.3.0-1.el8_2`	RHSA-2025:17340
Red Hat Enterprise Linux 8.2 Advanced Update Support	`firefox-0:140.3.0-1.el8_2`	RHSA-2025:17372
Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support	`thunderbird-0:140.3.0-1.el8_4`	RHSA-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 CVE-2024-12224 in your dependencies?

O3 Security finds CVE-2024-12224 across crates.io dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works