How to verify CVE-2026-42167
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-2026-42167 -u your-target:port -rl 50 -timeout 10Runs against your own host. Don't have Nuclei? Install guide ↗
- highOfficialVerifiedtcpProFTPD mod_sql - Preauth User BackdoorGitHub ↗
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 21 NVT checks for CVE-2026-42167. 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.180022' details='1'/>"1.3.6.1.4.1.25623.1.0.180022since 2026-06-251.3.6.1.4.1.25623.1.1.10.2026.0200since 2026-06-251.3.6.1.4.1.25623.1.1.13.2026.118.01since 2026-06-251.3.6.1.4.1.25623.1.1.13.2026.154.03since 2026-06-251.3.6.1.4.1.25623.1.1.16.2026.2158since 2026-06-251.3.6.1.4.1.25623.1.1.16.2026.2159since 2026-06-251.3.6.1.4.1.25623.1.1.16.2026.2264since 2026-06-251.3.6.1.4.1.25623.1.1.16.2026.2266since 2026-06-251.3.6.1.4.1.25623.1.1.16.2026.2760since 2026-07-151.3.6.1.4.1.25623.1.1.17.2026.0230since 2026-07-30
+ 11 more NVTs