CVE-2021-22051: Applications using Spring Cloud Gateway are vulnerable to specifically crafted requests that could make an extra request on downstream…
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.67% (FIRST EPSS); higher than 52.5% of all records.
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
- Fixed version: org.springframework.cloud:spring-cloud-gateway (Maven) 2.2.10.RELEASE0.5, 3.0.5.
Low priority for now. Upgrade to org.springframework.cloud:spring-cloud-gateway (Maven) 2.2.10.RELEASE0.5, 3.0.5 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 8, 2021
- Updated
- Jun 16, 2026
- EPSS
- 0.6% · 52th percentile
- CWE
- CWE-863
Report tools
Action score
26
Low priority for now.
- CVSS
- 26 / 40 · 6.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.6%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| vmware | spring cloud gateway | cpe:2.3:a:vmware:spring_cloud_gateway |
Versions reported by the vendor
Affected version ranges reported by the assigning authority (vmware). Independent of NVD's CPE analysis and usually ahead of it.
n/a Spring Cloud Gateway
- 3.0.0 to 3.0.4, 2.2.0.RELEASE to 2.2.9.RELEASE, and older versionsaffected
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- vmware spring cloud gatewaybefore 2.2.10
- vmware spring cloud gateway3.0.0 and later · before 3.0.5
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Maven | org.springframework.cloud:spring-cloud-gateway | from 2.2.0 · before 2.2.10.RELEASE0.5 | 2.2.10.RELEASE0.5 |
| Maven | org.springframework.cloud:spring-cloud-gateway | from 3.0.0 · before 3.0.5 | 3.0.5 |
Same product
vmware: all recordsOther highest-scoring records for the same primary product.
- CVE-2022-22947In spring cloud gateway versions prior to 3.1.1+ and 3.0.7+ , applications are vulnerable to a code injection attack when the Gateway…KEV99Now
- CVE-2026-47879Spring Cloud Gateway SSRF and native file access with gRPC34Monitor
- CVE-2026-47825Spring Cloud Gateway Server Forwards Headers from Untrusted Proxies in certain situations34Monitor
Published before and after this one in the same product
- Later →CVE-2022-22946Mar 4, 2022 · In spring cloud gateway versions prior to 3.1.1+ , applications that are configured to enable HTTP2 and no key store or trusted…23Monitor
- Later →CVE-2025-41235May 30, 2025 · CVE-2025-41235: Spring Cloud Gateway Server Forwards Headers from Untrusted Proxies34Monitor
- Later →CVE-2026-22750Apr 10, 2026 · SSL bundle configuration silently bypassed in Spring Cloud Gateway30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Maven:org.springframework.cloud:spring-cloud-gateway | 2.2.10.RELEASE0.5 | Package registry (OSV) |
| Maven:org.springframework.cloud:spring-cloud-gateway | 3.0.5 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- high · data or configuration can be modified
- Availability
- none
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- High
- Availability impact
- None
Weakness class (CWE)
CWE-863 · Incorrect AuthorizationCVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.