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

Vulnerability Intelligence Directory

Explore and search through 82,900 vulnerability records.

1,381–1,392 of 82,900 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 local attacker to obtain sensitive credentials and compromise accounts due to insertion of sensitive information into log files.

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

IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to delete or overwrite arbitrary control-plane assets due to an insecure direct object reference.

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

IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information due to an insecure direct object reference.

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

IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to modify tool configuration and cause a denial of service due to improper authorization. Information supplied by the client is relied...

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

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 17, 2026
View details  →

IBM API Connect 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to obtain sensitive information from internal network resources due to server-side request forgery. Destination checks on outbound req...

▢  Published Nov 7, 2026 ↻  Updated Nov 17, 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 access internal network services due to server-side request forgery.

▢  Published Nov 7, 2026 ↻  Updated Nov 17, 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 bypass authentication across tenants due to improper authentication. Authentication checks are not s...

▢  Published Nov 7, 2026 ↻  Updated Nov 17, 2026
View details  →
!CVE-2026-17359CRITICAL 9.9

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 execute arbitrary code due to improper control of generation of code. A user-supplied value can infl...

▢  Published Nov 7, 2026 ↻  Updated Nov 17, 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 server-side request forgery.

▢  Published Nov 7, 2026 ↻  Updated Nov 17, 2026
View details  →
!CVE-2026-17367MEDIUM 5.4

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 insufficiently protected credentials.

▢  Published Nov 7, 2026 ↻  Updated Nov 17, 2026
View details  →
!CVE-2026-17369MEDIUM 5.4

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 force a user to authenticate into an attacker-controlled account due to cross-site request forgery. The sign-in fl...

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

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