CVE-2022-22978

CRITICALNVD 9.89.8
EchelonGraph scoreHIGH confidence

Score elevated to 9.8 because EPSS predicts 89% probability of exploitation within the next 30 days (top 0.5% of all CVEs). NVD baseline CVSS 9.8 retained for reference. Confidence: see factors.

Triggered by: EPSS exploit prediction ≥85%
Sources: epss, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 11%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

In spring security versions prior to 5.4.11+, 5.5.7+ , 5.6.4+ and older unsupported versions, RegexRequestMatcher can easily be misconfigured to be bypassed on some servlet containers. Applications using RegexRequestMatcher with . in the regular expression are possibly vulnerable to an authorization bypass.

CVSS v3
9.8
EG Score
9.8(high)
EPSS
95.3%
KEV
Not listed

Published

May 19, 2022

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated Jun 10, 2026
No patch confirmed yet.
generic

CVE-2022-22978: Authorization Bypass in RegexRequestMatcher

https://spring.io/security/cve-2022-22978

Vendor Advisories for CVE-2022-22978(1)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatjenkins-0:2.387.3.1684911776-3.el82023-05-24redhat
redhatspring-security2022-07-07redhat

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

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFixed inDependents
org.springframework.security:spring-security-core2.0.0 ... 5.4.9 (144 versions)5.4.11
org.springframework.security:spring-security-web3.0.0.RELEASE ... 5.4.9 (135 versions)5.4.11

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

Publicly available exploits

(4 references)

Working exploit code is in the public domain (4 GitHub PoCs). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • GitHub PoCumakant76705/CVE-2022-22978
    First seen Mar 1, 2023
    Open source ↗
  • GitHub PoCaeifkz/CVE-2022-22978
    First seen Jul 13, 2022

    CVE-2022-22978 POC Project

    Open source ↗
  • GitHub PoCducluongtran9121/CVE-2022-22978-PoC
    First seen Jun 4, 2022

    PoC of CVE-2022-22978 vulnerability in Spring Security framework

    Open source ↗
  • GitHub PoCDeEpinGh0st/CVE-2022-22978
    First seen May 31, 2022

    CVE-2022-22978 Spring-Security bypass Demo

    Open source ↗

Frequently asked(5)

What is CVE-2022-22978?
CVE-2022-22978 is a critical vulnerability published on May 19, 2022. In spring security versions prior to 5.4.11+, 5.5.7+ , 5.6.4+ and older unsupported versions, RegexRequestMatcher can easily be misconfigured to be bypassed on some servlet containers. Applications using RegexRequestMatcher with . in the regular expression are possibly vulnerable to an…
When was CVE-2022-22978 disclosed?
CVE-2022-22978 was first published in the National Vulnerability Database on May 19, 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-22978 actively exploited?
CVE-2022-22978 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 95.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2022-22978?
CVE-2022-22978 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2022-22978?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2022-22978, 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-22978

Explore →

Is Your Infrastructure Affected by CVE-2022-22978?

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