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

Vulnerability Intelligence Directory

Explore and search through 85,601 vulnerability records.

13,045–13,056 of 85,601 records

IBM MQ 9.2.0.0 through 9.2.0.44 LTS, 9.3.0.0 through 9.3.0.42 LTS, 9.4.0.0 through 9.4.0.26 LTS, 9.4.0.0 through 9.4.5.1 CD, and 10.0.0.0 through 10.0.0.5 LTS and CD could allow a remote authenticated attacker to cause a...

▢  Published Nov 4, 2026 ↻  Updated Nov 10, 2026
View details  →

In JetBrains IntelliJ IDEA before 2026.3 code execution in untrusted projects via a configured ShellCheck path

▢  Published Nov 6, 2026 ↻  Updated Nov 10, 2026
View details  →

In JetBrains IntelliJ IDEA before 2026.3 path traversal was possible via unpacking Dev Container archives from a remote host

▢  Published Nov 6, 2026 ↻  Updated Nov 10, 2026
View details  →

In JetBrains IntelliJ IDEA before 2026.3 improper checks allowed server certificates to be added to the trust store during headless runs

▢  Published Nov 6, 2026 ↻  Updated Nov 10, 2026
View details  →
!CVE-2026-123307MEDIUM 6.8

In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 unauthenticated connection to an arbitrary host via run configurations was possible

▢  Published Nov 6, 2026 ↻  Updated Nov 10, 2026
View details  →
!CVE-2026-123278MEDIUM 6.7

In JetBrains IntelliJ IDEA before 2026.3 code execution was possible via the unauthenticated JDBC worker RMI endpoint

▢  Published Nov 6, 2026 ↻  Updated Nov 10, 2026
View details  →

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used pem.decode(), lib/pem.js, missing END line to process the relevant inp...

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

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used pki.verifyCertificateChain(), pki.createCaStore(), duplicate subject n...

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

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used BigInteger.prototype.modInverse(), bnModInverse(), lib/jsbn.js, RSA pu...

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

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, node-forge accepted a PKCS#12 MAC or PKCS#12 password-based encryption iteration count of zero or less....

▢  Published Oct 29, 2026 ↻  Updated Nov 10, 2026
View details  →
!CVE-2026-119186MEDIUM 5.9

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, node-forge did not validate the AES-GCM tagLength option passed to start() during decryption through fo...

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

Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used forge.tls.createConnection(), fragmented handshake message, interleave...

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

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