How to verify CVE-2022-22965
Confirm whether your systems are actually affected — run the exact detection check below (Nuclei command or OpenVAS NVT). Detection only; it does not exploit.
How to verify this vulnerability
Scanner data tells you how to confirm whether your systems are actually affected — not just that the CVE exists. Run a Nuclei template against your target for a yes/no answer in seconds.
nuclei -id CVE-2022-22965 -u https://your-target -rl 50 -timeout 10Runs against your own host. Don't have Nuclei? Install guide ↗
- criticalOfficialhttpSpring - Remote Code ExecutionGitHub ↗
- criticalOfficialhttpSpring Framework RCE via Data Binding on JDK 9+GitHub ↗
- criticalCommunityhttpCVE-2022-22965 - Spring4Shell RCE VulnerabilityGitHub ↗
Find every CVE you can verify
Search the whole database by Nuclei coverage — filter by vendor, severity and KEV to build a verification list for your entire stack.
- Filter all CVEs that ship a Nuclei template
- Combine with vendor, severity & KEV
- Build a scan list across your stack
This template is on GitHub already — an account lets you search and filter every CVE that has one, not just this CVE.
Verify with OpenVAS
Greenbone/OpenVAS ships 22 NVT checks for CVE-2022-22965. OpenVAS detects this CVE by NVT OID — enable the NVT in your scan config, or confirm it is in your feed with the query below.
gvm-cli socket --xml "<get_nvts nvt_oid='1.3.6.1.4.1.25623.1.0.103266' details='1'/>"1.3.6.1.4.1.25623.1.0.103266since 2026-06-251.3.6.1.4.1.25623.1.0.104252since 2026-06-251.3.6.1.4.1.25623.1.0.104444since 2026-06-251.3.6.1.4.1.25623.1.0.113865since 2026-06-251.3.6.1.4.1.25623.1.0.113882since 2026-06-251.3.6.1.4.1.25623.1.0.113888since 2026-06-251.3.6.1.4.1.25623.1.0.113889since 2026-06-251.3.6.1.4.1.25623.1.0.113890since 2026-06-251.3.6.1.4.1.25623.1.0.113926since 2026-06-251.3.6.1.4.1.25623.1.0.113927since 2026-06-25
+ 12 more NVTs