CVE Vulnerability Intelligence
Vulnerability intelligence from official sources, matched to what you run
AI Inspector Lab keeps a local vulnerability database synchronised in the background from official, structured sources. Scans read from it instead of downloading feeds each time, and monitored assets are re-matched whenever new or modified CVEs arrive.
What the inspector checks
Version-range matching
Detected versions are compared with affected ranges (start/end, inclusive/exclusive) per CPE product or package - never assumed vulnerable.
Exploitation context
Known exploitation, exploitation probability, public exploit and detection availability are shown next to severity, never merged into it; a public exploit is never treated as proof.
Source attribution
Every vulnerability page lists its original references and which source supplied each piece of data, with retrieval times.
Honest labelling
Findings are labelled affected version, validated, potential, informational or unverified, so you always know how each was established.
Who uses it
- Prioritising patching by real-world exploitation
- Answering 'are we affected?' when a new CVE lands
- Audit evidence with sources
CVE Vulnerability Intelligence FAQ
How fresh is the data?
CVE changes are synchronised every 15 minutes, known-exploitation data every few hours and exploitation probabilities daily. Each report shows when its data was last synchronised.
Does a public exploit mean my system is being attacked?
No. Exploit, proof-of-concept and detection availability are context for prioritisation. Exploitation in the wild is reported separately, only when an authoritative source confirms it.
Other detectors
Try the CVE Vulnerability Intelligence for free
Check text, public websites and GitHub repositories for free - no account needed. Go Pro for private document, image and code inspections, Compare and the API.