How to verify CVE-2026-31431
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-31431 -u https://your-target -rl 50 -timeout 10Runs against your own host. Don't have Nuclei? Install guide ↗
- highOfficialVerifiedcodeCopy Fail - Linux Kernel Local Privilege Escalation via AF_ALGGitHub ↗
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 130 NVT checks for CVE-2026-31431. 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.118853' details='1'/>"1.3.6.1.4.1.25623.1.0.118853since 2026-06-251.3.6.1.4.1.25623.1.0.138100since 2026-06-251.3.6.1.4.1.25623.1.0.157038since 2026-06-251.3.6.1.4.1.25623.1.0.157039since 2026-06-251.3.6.1.4.1.25623.1.0.157040since 2026-06-251.3.6.1.4.1.25623.1.0.157252since 2026-07-151.3.6.1.4.1.25623.1.0.157474since 2026-07-231.3.6.1.4.1.25623.1.0.157475since 2026-07-231.3.6.1.4.1.25623.1.0.180141since 2026-06-251.3.6.1.4.1.25623.1.0.180254since 2026-06-25
+ 120 more NVTs