Threats / VMware / CVE-2022-22947
CVE-2022-22947
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-06-22
VMware Spring Cloud Gateway vulnerability
Spring Cloud Gateway is vulnerable to code injection when the Gateway Actuator endpoint is enabled, exposed, and unsecured, allowing remote code execution.
Verdict
Today item — known-exploited.
An unauthenticated attacker can inject and execute arbitrary code on vulnerable Spring Cloud Gateway instances by exploiting an exposed, unsecured Actuator endpoint. This critical vulnerability has been actively exploited in the wild.
01
Is it exploitable?
— the evidence, ranked above the scoreExploit available
Fully weaponized — public exploit code is cataloged for this vulnerability.We link the existence of the exploit; we do not host or redistribute payloads.
Reported exploitation
307 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2022-05-16).
Probability (EPSS)
EPSS 0.98253 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: VMware, Spring Cloud Gateway. Confirm exact fixed builds in the vendor advisory.
Weakness (CWE)
Mapped to CWE-94 Code Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I discover an exposed Spring Cloud Gateway Actuator endpoint without authentication requirements.
Business
The organization has failed to properly secure or restrict access to administrative interfaces.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft a malicious payload leveraging code injection to execute arbitrary commands through the Gateway endpoint.
Business
The application processes untrusted input without proper validation or sandboxing.
3
Lateral reach — past segmentation narrative 3
Attacker
I gain remote code execution on the Gateway server with the privileges of the application process.
Business
The organization experiences unauthorized system access and potential data compromise.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05