CVE Tools
Sign in
Back to CVE-2022-36316

How to verify CVE-2022-36316

Confirm whether your systems are actually affected — run the exact detection check below (Nuclei command or OpenVAS NVT). Detection only; it does not exploit.

Verify with OpenVAS

Greenbone/OpenVAS ships 9 NVT checks for CVE-2022-36316. 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.

Confirm the NVT is in your feed (GMP)
gvm-cli socket --xml "<get_nvts nvt_oid='1.3.6.1.4.1.25623.1.0.821196' details='1'/>"
NVT OIDs (9)
  • 1.3.6.1.4.1.25623.1.0.821196since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.821197since 2026-06-25
  • 1.3.6.1.4.1.25623.1.0.845457since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.12.2022.5536.1since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.16.2025.1265since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.16.2025.1268since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.17.2025.0223since 2026-06-25
  • 1.3.6.1.4.1.25623.1.1.18.1.2024.12227.1since 2026-06-25
  • 1.3.6.1.4.1.25623.1.2.1.2022.28since 2026-06-25
New to OpenVAS? Greenbone documentation ↗
Confirmed exposed? That's one CVE on one host.
We check your whole external estate — hundreds of IPs and domains — for this and thousands more, on a schedule.
Scan my estate
Verify another CVE