How to verify CVE-2025-62168
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-2025-62168 -u https://your-target -rl 50 -timeout 10Runs against your own host. Don't have Nuclei? Install guide ↗
- criticalOfficialVerifiedhttpSquid Proxy - HTTP Authentication Credentials DisclosureGitHub ↗
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 41 NVT checks for CVE-2025-62168. 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.125371' details='1'/>"1.3.6.1.4.1.25623.1.0.125371since 2026-06-251.3.6.1.4.1.25623.1.0.134026since 2026-06-251.3.6.1.4.1.25623.1.1.10.2026.0094since 2026-06-251.3.6.1.4.1.25623.1.1.11.2025.19107since 2026-06-251.3.6.1.4.1.25623.1.1.11.2025.19167since 2026-06-251.3.6.1.4.1.25623.1.1.11.2025.20935since 2026-06-251.3.6.1.4.1.25623.1.1.11.2025.21002since 2026-06-251.3.6.1.4.1.25623.1.1.1.1.2025.6047since 2026-06-251.3.6.1.4.1.25623.1.1.1.2.2025.4369since 2026-06-251.3.6.1.4.1.25623.1.1.12.2025.7845.1since 2026-06-25
+ 31 more NVTs