Threats / VMware Tanzu / CVE-2022-22963
CVE-2022-22963
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
VMware Tanzu Spring Cloud vulnerability
Spring Cloud Function routing allows unauthenticated remote code execution via malicious SpEL expressions, enabling attackers to execute arbitrary code and access local resources on affected systems.
Verdict
Today item — known-exploited.
A critical remote code execution vulnerability in VMware Tanzu Spring Cloud Function's routing functionality permits attackers to inject and execute arbitrary code through specially crafted SpEL expressions, with active exploitation confirmed in the wild.
CISA KEV Yes · 2022-08-255EPSS 0.99939 (verify live)6Exploit Weaponized · public PoC7CVSS 9.8 (CISA)4CISA SSVC Exploitation: active · Automatable: yes · Impact: total4
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
125 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-08-25).
Probability (EPSS)
EPSS 0.99939 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: VMware Tanzu, Spring Cloud. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-94 Code Injection — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 146 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module, nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
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 craft a malicious SpEL expression and submit it as a routing parameter to the vulnerable Spring Cloud Function endpoint.
Business
Attackers gain unauthenticated code execution capability against internet-facing Spring Cloud Function deployments.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I execute arbitrary commands on the target system through the evaluated SpEL expression.
Business
Complete system compromise becomes possible, including data exfiltration, lateral movement, and persistent access establishment.
3
Lateral reach — past segmentation narrative 3
Attacker
I access local resources and sensitive files available to the application process.
Business
Confidential data, credentials, and configuration information stored on affected servers are exposed to attackers.
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