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

Vulnerability Intelligence Directory

Explore and search through 83,515 vulnerability records.

4,225–4,236 of 83,515 records

IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to improper authorization. Authorization decisions rely on informat...

▢  Published Nov 7, 2026 ↻  Updated Nov 16, 2026
View details  →

IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to broken object-level authorization.

▢  Published Nov 7, 2026 ↻  Updated Nov 16, 2026
View details  →

IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to improper authorization.

▢  Published Nov 7, 2026 ↻  Updated Nov 16, 2026
View details  →
!CVE-2026-17428MEDIUM 5.0

IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to improper authorization. Values supplied in the request URL are u...

▢  Published Nov 7, 2026 ↻  Updated Nov 16, 2026
View details  →

IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to SQL injection.

▢  Published Nov 7, 2026 ↻  Updated Nov 16, 2026
View details  →
!CVE-2026-17393MEDIUM 5.1

IBM API Connect 10.0.8.0 through 10.0.8.12 could allow a local attacker to obtain sensitive information due to the use of a cryptographically weak pseudo-random number generator.

▢  Published Nov 7, 2026 ↻  Updated Nov 16, 2026
View details  →
!CVE-2026-17391MEDIUM 6.3

IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to broken object-level authorization.

▢  Published Nov 7, 2026 ↻  Updated Nov 16, 2026
View details  →
!CVE-2026-17389MEDIUM 5.3

IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information from the connected LDAP directory due to LDAP injection. Input is not properly neutra...

▢  Published Nov 7, 2026 ↻  Updated Nov 16, 2026
View details  →

IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to broken object-level authorization.

▢  Published Nov 7, 2026 ↻  Updated Nov 16, 2026
View details  →
!CVE-2026-17371MEDIUM 5.0

IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to broken object-level authorization.

▢  Published Nov 7, 2026 ↻  Updated Nov 16, 2026
View details  →
!CVE-2026-17310MEDIUM 6.5

IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote attacker to obtain sensitive information due to the use of a hard-coded cryptographic key.

▢  Published Nov 7, 2026 ↻  Updated Nov 16, 2026
View details  →
!CVE-2026-17314MEDIUM 5.0

IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to server-side request forgery.

▢  Published Nov 7, 2026 ↻  Updated Nov 16, 2026
View details  →

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