How to verify CVE-2025-52999

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 19 NVT checks for CVE-2025-52999. 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.136238' details='1'/>"

NVT OIDs (19)

1.3.6.1.4.1.25623.1.0.136238since 2026-06-25
1.3.6.1.4.1.25623.1.0.155771since 2026-06-25
1.3.6.1.4.1.25623.1.0.156014since 2026-06-25
1.3.6.1.4.1.25623.1.0.156233since 2026-06-25
1.3.6.1.4.1.25623.1.0.157462since 2026-07-21
1.3.6.1.4.1.25623.1.0.180253since 2026-07-01
1.3.6.1.4.1.25623.1.0.180262since 2026-06-27
1.3.6.1.4.1.25623.1.1.11.2025.12280since 2026-06-25
1.3.6.1.4.1.25623.1.1.11.2025.14126since 2026-06-25
1.3.6.1.4.1.25623.1.1.1.1.2026.6336since 2026-06-25

+ 9 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