How to verify CVE-2022-38900
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 -t CVE-2022-38900.yaml -u https://your-target -rl 50 -timeout 10Community template — download the YAML from GitHub first, then run the command against your own host.
- highCommunityhttpdecode-uri-component <= 0.2.1 - Denial of ServiceGitHub ↗
- highCommunityhttpdecode-uri-component <= 0.2.1 - Denial of Service GitHub ↗
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 20 NVT checks for CVE-2022-38900. 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.125662' details='1'/>"1.3.6.1.4.1.25623.1.0.125662since 2026-06-251.3.6.1.4.1.25623.1.0.126333since 2026-06-251.3.6.1.4.1.25623.1.0.127537since 2026-06-251.3.6.1.4.1.25623.1.0.149672since 2026-06-251.3.6.1.4.1.25623.1.0.149740since 2026-06-251.3.6.1.4.1.25623.1.0.153489since 2026-06-251.3.6.1.4.1.25623.1.0.155843since 2026-06-251.3.6.1.4.1.25623.1.0.827375since 2026-06-251.3.6.1.4.1.25623.1.0.827379since 2026-06-251.3.6.1.4.1.25623.1.0.827385since 2026-06-25
+ 10 more NVTs