CVE-2021-22051
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- Upgrade to the fixed version for your release line, or later: spring cloud gateway 2.2.10; spring cloud gateway 3.0.5 upper bounds of the CVE record's affected ranges
- Later advisories still cover the fixes above and name higher ones: spring-cloud-gateway 3.0.7 (CVE-2022-22947) OSV advisories
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
Applications using Spring Cloud Gateway are vulnerable to specifically crafted requests that could make an extra request on downstream services. Users of affected versions should apply the following mitigation: 3.0.x users should upgrade to 3.0.5+, 2.2.x users should upgrade to 2.2.10.RELEASE or newer.
- weakness
- Specifically crafted requests could make an extra request on downstream services.
- affected
- n/a Spring Cloud Gateway
- published ranges
- vmware spring cloud gateway < 2.2.10; vmware spring cloud gateway >= 3.0.0 < 3.0.5
- first unaffected version, by branch
- spring cloud gateway 2.2.10; spring cloud gateway 3.0.5
- fixed by package (from OSV advisories)
- org.springframework.cloud:spring-cloud-gateway (Maven): 2.2.10.RELEASE0.5; 3.0.5 GHSA-2r2v-q399-qq93
- later fixes (from OSV advisories)
- spring-cloud-gateway 2.2.10.RELEASE0.5 is inside a range CVE-2022-22947 (GHSA-3gx9-37ww-9qw6) lists as affected. That advisory is fixed in 3.0.7.spring-cloud-gateway 3.0.5 is inside a range CVE-2022-22947 (GHSA-3gx9-37ww-9qw6) lists as affected. That advisory is fixed in 3.0.7.
- assigned by
- vmware
- published
- 2021-11-08
check us tanzu.vmware.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 9 Nov 2021 | 0.00416 | |
| 6 Jan 2022 | 0.0184 | |
| 4 Feb 2022 | 0.04499 | |
| 1 Apr 2022 | 0.00885 | |
| 7 Mar 2023 | 0.00052 | scoring model v2023.03.01 |
| 8 Mar 2023 | 0.00052 | |
| 1 Jun 2023 | 0.00054 | |
| 17 Mar 2025 | 0.00274 | scoring model v2025.03.14 |
| 29 Mar 2025 | 0.00327 | |
| 30 Mar 2025 | 0.00274 | |
| 4 May 2025 | 0.00184 | |
| 7 Oct 2025 | 0.00135 | |
| 15 Jun 2026 | 0.00668 | scoring model v2026.06.15 |
| 1 Sep 2026 | 0.0069 |
14 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.01 on 2026-09-01 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- Held: spring cloud gateway 2.2.10; spring cloud gateway 3.0.5. A newer fix from the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2021-22051', '2026-11-01T23:59:59.999999Z', now());