How to verify CVE-2026-4800

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 37 NVT checks for CVE-2026-4800. 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.136388' details='1'/>"

NVT OIDs (37)

1.3.6.1.4.1.25623.1.0.136388since 2026-08-01
1.3.6.1.4.1.25623.1.0.136482since 2026-07-25
1.3.6.1.4.1.25623.1.0.180253since 2026-07-01
1.3.6.1.4.1.25623.1.1.10.2026.0175since 2026-06-25
1.3.6.1.4.1.25623.1.1.11.2026.10710since 2026-06-25
1.3.6.1.4.1.25623.1.1.11.2026.10713since 2026-06-25
1.3.6.1.4.1.25623.1.1.11.2026.19008since 2026-06-25
1.3.6.1.4.1.25623.1.1.11.2026.19167since 2026-06-25
1.3.6.1.4.1.25623.1.1.11.2026.24331since 2026-06-25
1.3.6.1.4.1.25623.1.1.1.2.2026.4663since 2026-07-15

+ 27 more NVTs

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