CVE-2022-23901: A stack overflow re2c 2.2 exists due to infinite recursion issues in src/dfa/dead_rules.cc.
CVE-2022-23901 is a critical-severity flaw (CVSS 9.8) affecting re2c. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
A stack overflow re2c 2.2 exists due to infinite recursion issues in src/dfa/dead_rules.cc.
Why this priority
- Critical severity
- Public exploit reference
- Remotely exploitable, no login, no user action
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 9.8 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 1.6% (top 24%) |
| CISA exploited list | No |
| Weakness | CWE-787 |
| Published | 2022-03-29 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-23901?
re2c: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2022-23901 being exploited?
CVE-2022-23901 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-23901 affect?
CVE-2022-23901 affects re2c. Severity is critical (CVSS 9.8). A stack overflow re2c 2.2 exists due to infinite recursion issues in src/dfa/dead_rules.cc.
How urgent is CVE-2022-23901?
Priority 63/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action
Related CVEs
- CVE-2020-11958 HIGH 7.8 DOWNGRADE MITIGATE re2c 1.3 has a heap-based buffer overflow in Scanner::fill in parse/scanner.cc via a long lexeme.
- CVE-2018-21232 MEDIUM 5.5 UPGRADE re2c before 2.0 has uncontrolled recursion that causes stack consumption in find_fixed_tags.