CVE-2022-24713

HIGHNVD 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 10.4%, top 7% 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
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 14%CVSS: 7.5Exploit: NoneExposed: 0

A fix is available — apply it.

regex is an implementation of regular expressions for the Rust language. The regex crate features built-in mitigations to prevent denial of service attacks caused by untrusted regexes, or untrusted input matched by trusted regexes. Those (tunable) mitigations already provide sane defaults to prevent attacks. This guarantee is documented and it's considered part of the crate's API. Unfortunately a bug was discovered in the mitigations designed to prevent untrusted regexes to take an arbitrary amount of time during parsing, and it's possible to craft regexes that bypass such mitigations. This makes it possible to perform denial of service attacks by sending specially crafted regexes to services accepting user-controlled, untrusted regexes. All versions of the regex crate before or equal to 1.5.4 are affected by this issue. The fix is include starting from regex 1.5.5. All users accepting user-controlled regexes are recommended to upgrade immediately to the latest version of the regex crate. Unfortunately there is no fixed set of problematic regexes, as there are practically infinite regexes that could be crafted to exploit this vulnerability. Because of this, it us not recommend to deny known problematic regexes.

CVSS v3
7.5
EG Score
7.5(medium)
EPSS
96.2%
KEV
Not listed

Published

March 8, 2022

Last Modified

November 21, 2024

References (24)

Vendor Advisories for CVE-2022-24713(3)

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

Patch Availability(12)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntufirefox-locale-ast (99.0+build2-0ubuntu0.20.04.2) @ focal2026-05-26ubuntu
ubuntulibrust-regex+unicode-case-dev (1.5.4-1ubuntu0.1) @ jammy2026-05-26ubuntu
redhatthunderbird-0:91.8.0-1.el8_22022-04-12redhat
redhatthunderbird-0:91.8.0-1.el8_12022-04-11redhat
redhatthunderbird-0:91.8.0-1.el8_52022-04-11redhat
redhatthunderbird-0:91.8.0-1.el7_92022-04-11redhat
redhatthunderbird-0:91.8.0-1.el8_42022-04-11redhat
redhatfirefox-0:91.8.0-1.el8_22022-04-08redhat
redhatfirefox-0:91.8.0-1.el8_12022-04-08redhat
redhatfirefox-0:91.8.0-1.el8_42022-04-08redhat
redhatfirefox-0:91.8.0-1.el7_92022-04-08redhat
redhatfirefox-0:91.8.0-1.el8_52022-04-08redhat

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

(1 across 1 ecosystem)
crates.io(1)
PackageVulnerable rangeFixed inDependents
regex1.5.5

Weakness Classification(2)

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

Additional Vendor Advisories

(10)

Data Freshness Timeline

(refreshed 5× in last 7d / 34× 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-12 05:44 UTCEPSS rescore
  2. 2026-07-11 08:25 UTCEPSS rescore
  3. 2026-07-09 19:07 UTCEPSS rescore
  4. 2026-07-08 15:12 UTCEPSS rescore
  5. 2026-07-07 13:44 UTCEPSS rescore
  6. 2026-07-05 02:28 UTCEPSS rescore
  7. 2026-07-04 06:29 UTCEPSS rescore
  8. 2026-07-04 06:29 UTCEPSS rescore
  9. 2026-07-01 15:04 UTCEPSS rescore
  10. 2026-06-29 19:02 UTCOSV refresh
  11. 2026-06-29 14:04 UTCEPSS rescore
  12. 2026-06-29 14:04 UTCEPSS rescore
  13. 2026-06-28 14:06 UTCEPSS rescore
  14. 2026-06-28 04:54 UTCEPSS rescore
  15. 2026-06-28 04:54 UTCEPSS rescore
  16. 2026-06-27 03:07 UTCEPSS rescore
  17. 2026-06-25 13:48 UTCEPSS rescore
  18. 2026-06-24 14:03 UTCEPSS rescore
  19. 2026-06-24 14:03 UTCEPSS rescore
  20. 2026-06-23 21:31 UTCEPSS rescore
  21. 2026-06-23 21:31 UTCEPSS rescore
  22. 2026-06-22 14:24 UTCEPSS rescore
  23. 2026-06-21 01:58 UTCEPSS rescore
  24. 2026-06-21 01:58 UTCEPSS rescore
  25. 2026-06-18 17:51 UTCEPSS rescore
Show 43 more
  1. 2026-06-18 17:51 UTCEPSS rescore
  2. 2026-06-17 17:51 UTCEPSS rescore
  3. 2026-06-17 17:51 UTCEPSS rescore
  4. 2026-06-16 17:51 UTCEPSS rescore
  5. 2026-06-15 17:46 UTCEPSS rescore
  6. 2026-06-13 22:58 UTCEPSS rescore
  7. 2026-06-13 22:58 UTCEPSS rescore
  8. 2026-06-12 23:10 UTCEPSS rescore
  9. 2026-06-12 23:10 UTCEPSS rescore
  10. 2026-06-12 07:36 UTCOSV refresh
  11. 2026-06-11 13:58 UTCEPSS rescore
  12. 2026-06-11 13:58 UTCEPSS rescore
  13. 2026-06-10 22:16 UTCEPSS rescore
  14. 2026-06-10 13:20 UTCEPSS rescore
  15. 2026-06-08 14:15 UTCEPSS rescore
  16. 2026-06-08 14:15 UTCEPSS rescore
  17. 2026-06-07 15:23 UTCEPSS rescore
  18. 2026-06-07 15:23 UTCEPSS rescore
  19. 2026-06-06 13:46 UTCEPSS rescore
  20. 2026-06-06 13:46 UTCEPSS rescore
  21. 2026-06-05 22:45 UTCEPSS rescore
  22. 2026-06-05 06:09 UTCEPSS rescore
  23. 2026-06-05 06:09 UTCEPSS rescore
  24. 2026-06-04 13:11 UTCEPSS rescore
  25. 2026-06-04 13:11 UTCEPSS rescore
  26. 2026-06-02 20:11 UTCEPSS rescore
  27. 2026-06-02 20:11 UTCEPSS rescore
  28. 2026-06-02 20:11 UTCEPSS rescore
  29. 2026-05-31 22:29 UTCEPSS rescore
  30. 2026-05-31 22:29 UTCEPSS rescore
  31. 2026-05-31 00:15 UTCEPSS rescore
  32. 2026-05-31 00:15 UTCEPSS rescore
  33. 2026-05-29 13:42 UTCEPSS rescore
  34. 2026-05-28 13:43 UTCEPSS rescore
  35. 2026-05-28 13:43 UTCEPSS rescore
  36. 2026-05-28 13:43 UTCEPSS rescore
  37. 2026-05-27 13:39 UTCEPSS rescore
  38. 2026-05-27 13:39 UTCEPSS rescore
  39. 2026-05-26 13:43 UTCEPSS rescore
  40. 2026-05-26 07:17 UTCEPSS rescore
  41. 2026-05-26 07:17 UTCEPSS rescore
  42. 2026-05-26 02:04 UTCEG score recompute
  43. 2026-05-26 02:04 UTCVendor advisory

Frequently asked(5)

What is CVE-2022-24713?
CVE-2022-24713 is a high vulnerability published on March 8, 2022. regex is an implementation of regular expressions for the Rust language. The regex crate features built-in mitigations to prevent denial of service attacks caused by untrusted regexes, or untrusted input matched by trusted regexes. Those (tunable) mitigations already provide sane defaults to…
When was CVE-2022-24713 disclosed?
CVE-2022-24713 was first published in the National Vulnerability Database on March 8, 2022, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2022-24713 actively exploited?
CVE-2022-24713 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 96.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-24713?
CVE-2022-24713 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2022-24713?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-24713, 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-2022-24713

Explore →

Is Your Infrastructure Affected by CVE-2022-24713?

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