Rust's regex crate vulnerable to regular expression denial of service

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

EPSS

• CVE-2022-24713: 14.46% estimated exploitation activity in the next 30 days; percentile 96.63 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

This is a cross-post of [the official security advisory][advisory]. The official advisory contains a signed version with our PGP key, as well. [advisory]: https://groups.google.com/g/rustlang-security-announcements/c/NcNNL1Jq7Yw The Rust Security Response WG was notified that the regex crate did not properly limit the complexity of the regular expressions (regex) it parses. An attacker could use this security issue to perform a denial of service, by sending a specially crafted regex to a service accepting untrusted regexes. No known vulnerability is present when parsing untrusted input with trusted regexes. This issue has been assigned CVE-2022-24713. The severity of this vulnerability is "high" when the regex crate is used to parse untrusted regexes. Other uses of the regex crate are not affected by this vulnerability. Overview The regex crate features built-in mitigations to prevent denial of service attacks caused by untrusted regexes, or untrusted input matched by trusted…

Published by the source

8 Mar 2022, 20:00 UTC

Last modified by the source

6 Jul 2023, 16:07 UTC

Source last checked

26 Oct 2026, 15:37 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-m5pq-gvj9-9vr8

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-24713

Advisory: Rust's regex crate vulnerable to regular expression denial of service
IDs: CVE-2022-24713, GHSA-m5pq-gvj9-9vr8
Record: https://patchnext.com/advisories/cve-2022-24713 (revision 1, source checked 26 Oct 2026, 15:37 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: regex 1.5.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- crates.io regex: affected < 1.5.5; fixed in 1.5.5

## Suggested inspection (read-only)
- crates.io regex: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on regex.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-m5pq-gvj9-9vr8 (GitHub-reviewed advisory GHSA-m5pq-gvj9-9vr8 lists affected ranges: crates.io regex >=0 <1.5.5)

Commands are suggestions: review each one before running it.