Skip to content
CORVASEC — Knowledge Defends
CORVASEC INTELLIGENCE ENGINE

Intelligence Explorer

Investigate synchronized vulnerability intelligence and vetted campaign intelligence from one workspace. Move between CVEs, exploitation context, campaigns, actors, sectors, confidence and ATT&CK relationships without mixing fundamentally different intelligence records.

▤
Indexed CVEs85,934CVEs currently synchronized
⬡
Critical CVEs7,686Across the synchronized dataset
⚑
CISA KEV1,790Known exploited vulnerabilities
♧
MITRE ATT&CK706Techniques + sub-techniques
Last synchronized 39 minutes ago · automatic refresh every 10 min
▤

Vulnerability Intelligence Directory

Explore and search through 85,934 vulnerability records.

15,133–15,144 of 85,934 records

Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.

▢  Published Nov 4, 2024 ↻  Updated Nov 9, 2026
View details  →

Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2023-2143. Reason: This candidate is a reservation duplicate of CVE-2023-2143. Notes: All CVE users should reference CVE-2023-2143 instead o...

▢  Published Oct 23, 2024 ↻  Updated Nov 9, 2026
View details  →

Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage.

▢  Published Oct 22, 2024 ↻  Updated Nov 9, 2026
View details  →

Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2024-9884. Reason: This candidate is a reservation duplicate of CVE-2024-9884. Notes: All CVE users should reference CVE-2024-9884 instead o...

▢  Published Oct 18, 2024 ↻  Updated Nov 9, 2026
View details  →

Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: CVE-2024-48251. Reason: This candidate is a reservation duplicate of CVE-2024-48251. Notes: All CVE users should reference CVE-2024-48251 instead of this can...

▢  Published Oct 14, 2024 ↻  Updated Nov 9, 2026
View details  →

Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.

▢  Published Oct 14, 2024 ↻  Updated Nov 9, 2026
View details  →

Rejected reason: ** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage.

▢  Published Oct 11, 2024 ↻  Updated Nov 9, 2026
View details  →

Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: none.

▢  Published Oct 10, 2024 ↻  Updated Nov 9, 2026
View details  →

Rejected reason: DO NOT USE THIS CVE RECORD. ConsultIDs: CVE-2024-38365. Reason: This record is a duplicate of CVE-2024-38365. Notes: All CVE users should reference CVE-2024-38365 instead of this record. All references a...

▢  Published Oct 10, 2024 ↻  Updated Nov 9, 2026
View details  →

Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage.

▢  Published Oct 9, 2024 ↻  Updated Nov 9, 2026
View details  →

Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage.

▢  Published Oct 9, 2024 ↻  Updated Nov 9, 2026
View details  →

Rejected reason: DO NOT USE THIS CANDIDATE NUMBER. Reason: This candidate was issued in error. Notes: All references and descriptions in this candidate have been removed to prevent accidental usage.

▢  Published Oct 9, 2024 ↻  Updated Nov 9, 2026
View details  →

Catalog counts represent locally imported records and depend on the most recent successful synchronization.