Vulnerabilidades explotables hoy
406,192en la vista actual
Score único combinando CVSS, membresía KEV y EPSS. Cada CVE con su ficha propia — timeline desde publicación hasta explotación activa.
En catálogo KEV1,766
Nuevos KEV · 24H0
Exploit Today ≥ 701,698
Distribución · última ventana
- Crítico5,605
- Alto21,780
- Medio20,308
- Bajo2,107
Filtros
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2026-798136.7 MED0.2%
——0A local privilege escalation vulnerability exists in the ClearPass client software. Successful exploitation could allow a low-privileged local user to execute commands with elevated privileges on the affected system, if certain conditions outside of the attacker's control are met.24dCVE-2024-44098—0.2%
——0——CVE-2022-47323—0.2%
——0——CVE-2024-23658—0.2%
——0——CVE-2023-48342—0.2%
——0——CVE-2018-9463—0.2%
——0——CVE-2023-35692—0.2%
——0——CVE-2026-1154085.5 MED0.2%
——0In `github.com/eclipse-keypont/crypto11/v2` versions `>= 2.0.0-rc3, <= 2.0.0-rc8`, the ML-KEM key-pair lookup functions (`FindMLKEMKeyPair`, `FindMLKEMKeyPairs`, `FindMLKEMKeyPairsWithAttributes`) locate the public half of an ML-KEM key pair by `CKA_ID`/`CKA_LABEL` and never verify it against the private key. In addition, the "ID only" fallback search runs even when the private key has no `CKA_ID`, so the search template reduces to the public-key class and the ML-KEM key type and the first ML-KEM public key on the token is returned. `Encapsulate()` on the resulting key pair encrypts the fresh shared secret to that key, so its owner — not the holder of the private key the caller looked up — can recover the secret. An attacker who can open an unauthenticated session on the token and plant a public `CKK_ML_KEM` object carrying the victim's `CKA_ID`/`CKA_LABEL` receives the shared secrets for encapsulations performed through the substituted key pair, compromising the confidentiality of those secrets and of everything protected by keys derived from them. The v1 module paths have no ML-KEM support and are not affected.4dCVE-2018-9396—0.2%
——0——CVE-2026-28545—0.2%
——0——CVE-2026-00457.8 ALT0.2%
——0In bta_jv_rfcomm_connect of bta_jv_act.cc, there is a possible bypass of bonding for a secure connection due to a logic error in the code. This could lead to local escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation.101dCVE-2024-22008—0.2%
——0——CVE-2018-9462—0.2%
——0——CVE-2022-4048—0.2%
——0——CVE-2023-21139—0.2%
——0——CVE-2025-0076—0.2%
——0——CVE-2025-27062—0.2%
——0——CVE-2022-20091—0.2%
——0——CVE-2023-20826—0.2%
——0——CVE-2026-43305—0.2%
——0——CVE-2024-20026—0.2%
——0——CVE-2026-568504.4 MED0.2%
——0A flaw in Node.js HTTPS Agent connection reuse can cause PFX object-array key collisions, allowing mutual TLS (mTLS) client identities to be reused across requests configured with different client certificates.
This vulnerability affects Node.js **26.x**, **24.x**, and **22.x**.8dCVE-2022-48456—0.2%
——0——CVE-2023-20824—0.2%
——0——CVE-2025-270646.1 MED0.2%
——0Information disclosure while registering commands from clients with diag through diagHal.13dCVE-2026-22163—0.2%
——0——CVE-2025-4737—0.2%
——0——CVE-2025-22428—0.2%
——0——CVE-2018-9404—0.2%
——0——CVE-2025-48524—0.2%
——0——CVE-2018-9392—0.2%
——0——CVE-2024-20075—0.2%
——0——CVE-2022-20110—0.2%
——0——CVE-2018-9395—0.2%
——0——CVE-2023-4164—0.2%
——0——CVE-2023-38440—0.2%
——0——CVE-2025-36903—0.2%
——0——CVE-2024-13454—0.2%
——0——CVE-2022-48391—0.2%
——0——CVE-2024-32918—0.2%
——0——