How to verify CVE-2015-7501
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-2015-7501 -u https://your-target -rl 50 -timeout 10Runs against your own host. Don't have Nuclei? Install guide ↗
- criticalOfficialVerifiedhttpRed Hat JBoss - Insecure DeserializationGitHub ↗
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 19 NVT checks for CVE-2015-7501. 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.105828' details='1'/>"1.3.6.1.4.1.25623.1.0.105828since 2026-06-251.3.6.1.4.1.25623.1.0.120608since 2026-06-251.3.6.1.4.1.25623.1.0.122791since 2026-06-251.3.6.1.4.1.25623.1.0.122792since 2026-06-251.3.6.1.4.1.25623.1.0.140682since 2026-06-251.3.6.1.4.1.25623.1.0.156257since 2026-06-251.3.6.1.4.1.25623.1.0.160633since 2026-06-251.3.6.1.4.1.25623.1.0.807351since 2026-06-251.3.6.1.4.1.25623.1.0.871511since 2026-06-251.3.6.1.4.1.25623.1.0.871512since 2026-06-25
+ 9 more NVTs