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 CVEs84,759CVEs currently synchronized
⬡
Critical CVEs7,630Across the synchronized dataset
⚑
CISA KEV1,786Known exploited vulnerabilities
♧
MITRE ATT&CK706Techniques + sub-techniques
Last synchronized 38 minutes ago · automatic refresh every 10 min
▤

Vulnerability Intelligence Directory

Explore and search through 84,759 vulnerability records.

73,297–73,308 of 84,759 records

IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 could allow a remote authenticated attacker to bypass security restrictions due to improper authentication.

▢  Published Oct 8, 2026 ↻  Updated Oct 10, 2026
View details  →
!CVE-2026-19491CRITICAL 9.1

IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 could allow a remote attacker to bypass authentication due to improper authentication.

▢  Published Oct 8, 2026 ↻  Updated Oct 10, 2026
View details  →
!CVE-2026-16916CRITICAL 9.1

IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 could allow a remote authenticated attacker to execute arbitrary code due to a protection mechanism failure.

▢  Published Oct 8, 2026 ↻  Updated Oct 10, 2026
View details  →
!CVE-2026-11888MEDIUM 6.4

IBM Security Verify Access 10.0 through 10.0.9.2 and IBM Verify Identity Access 11.0 through 11.0.3 is vulnerable to an information disclosure attack.

▢  Published Oct 8, 2026 ↻  Updated Oct 10, 2026
View details  →
!CVE-2026-94510CRITICAL 9.9

Authorization bypass through user-controlled key in Microsoft Bookings allows an unauthorized attacker to elevate privileges over a network.

▢  Published Oct 8, 2026 ↻  Updated Oct 10, 2026
View details  →

IBM Guardium Data Protection 12.2 is vulnerable due to weak cryptographic protection and a hard-coded recovery key in the pkcrypto passkey component. A local attacker could exploit this vulnerability to recover the root...

▢  Published Oct 8, 2026 ↻  Updated Oct 10, 2026
View details  →

IBM Guardium Data Protection 12.2 is vulnerable to a local privilege escalation in the cp_wrapper component. A low-privileged local user could exploit this vulnerability to gain root privileges and access or modify sensi...

▢  Published Oct 8, 2026 ↻  Updated Oct 10, 2026
View details  →

IBM Guardium Data Protection 12.2 is affected by a command injection vulnerability in the SUID-root ssh_config_wrapper component. An authenticated high-privileged user can inject arbitrary commands through attacker-contr...

▢  Published Oct 8, 2026 ↻  Updated Oct 10, 2026
View details  →
!CVE-2026-79842CRITICAL 9.1

An authentication bypass vulnerability exists in HPE Intelligent Management Center (iMC) prior to v7.3 E0713

▢  Published Oct 8, 2026 ↻  Updated Oct 10, 2026
View details  →

IBM Guardium Data Protection 12.0, 12.1 is vulnerable to a heap-based buffer overflow in the S-TAP TrafficTap TDS login reassembly functionality. An unauthenticated remote attacker can send crafted TDS login fragments th...

▢  Published Oct 8, 2026 ↻  Updated Oct 10, 2026
View details  →

IBM Guardium Data Protection 12.0, 12.1, 12.2 is vulnerable to a heap-based buffer overflow in the MongoDB protocol parser. A remote attacker could send a specially crafted MongoDB SCRAM username containing an excessive...

▢  Published Oct 8, 2026 ↻  Updated Oct 10, 2026
View details  →

IBM Guardium Data Protection 12.0, 12.1, 12.2 is vulnerable to a heap-based out-of-bounds read in the TDS7 LOGIN7 protocol parser. A remote attacker could send a specially crafted TDS LOGIN7 packet containing invalid off...

▢  Published Oct 8, 2026 ↻  Updated Oct 10, 2026
View details  →

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