Vulnerabilidades explotables hoy
367,284en 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,685
Nuevos KEV · 24H0
Exploit Today ≥ 701,629
Distribución · última ventana
- Crítico2,295
- Alto9,356
- Medio5,353
- Bajo528
Ventana
Severidad
Filtros
CVECVSSEPSSKEVRExplotTítuloVis.
CVE-2022-25696—0.3%
——0——CVE-2024-43764—0.3%
——0——CVE-2023-35653—0.3%
——0——CVE-2018-9403—0.3%
——0——CVE-2023-32788—0.3%
——0——CVE-2023-30937—0.3%
——0——CVE-2023-30925—0.3%
——0——CVE-2025-36898—0.3%
——0——CVE-2025-47350—0.3%
——0——CVE-2023-20836—0.3%
——0——CVE-2026-24922—0.3%
——0——CVE-2023-33911—0.3%
——0——CVE-2026-33697—0.3%
——0——CVE-2023-32789—0.3%
——0——CVE-2026-411166.3 MED0.3%
——0Dell Inventory Collector Client, versions prior to 13.8.0, contain an Improper Link Resolution Before File Access ('Link Following') vulnerability. A low privileged attacker with local access could potentially exploit this vulnerability, leading to Arbitrary File Write.40dCVE-2026-81322—0.3%
——0Exposure of Sensitive Information to an Unauthorized Actor vulnerability in ash-project ash_cloak allows anyone with access to logs, error trackers, or crash reports, or anyone who can trigger a validation error, to recover the plaintext of a field the library encrypts.
AshCloak.Transformers.SetUpEncryption removes each cloaked attribute from the action's accept list and adds an action argument that carries the plaintext into the encryption change. That argument is built with sensitive?: attr.sensitive?, inheriting the flag from the source attribute, so a cloaked attribute declared without sensitive? true produces a non-sensitive argument. It is the only place the cleartext value lives, and the one place Ash will not redact: it appears verbatim in inspect(changeset), Ash.Error.Invalid and validation error messages, telemetry, :sys dumps, and error-tracker payloads. The generated encrypted attribute and decrypt calculation are already hardcoded sensitive.
This issue affects ash_cloak: from 0.1.0 before 0.4.0.2dCVE-2023-33906—0.3%
——0——CVE-2023-5342—0.3%
——0——CVE-2024-43095—0.3%
——0——CVE-2022-47324—0.3%
——0——CVE-2025-32350—0.3%
——0——CVE-2023-30923—0.3%
——0——CVE-2023-30926—0.3%
——0——CVE-2023-30939—0.3%
——0——CVE-2026-20417—0.3%
——0——CVE-2023-30920—0.3%
——0——CVE-2025-32326—0.3%
——0——CVE-2024-40677—0.3%
——0——CVE-2023-30941—0.3%
——0——CVE-2025-48555—0.3%
——0——CVE-2022-47325—0.3%
——0——CVE-2023-30866—0.3%
——0——CVE-2026-23601—0.3%
——0——CVE-2018-9435—0.3%
——0——CVE-2025-21444—0.3%
——0——CVE-2025-27036—0.3%
——0——CVE-2023-20717—0.3%
——0——CVE-2022-44427—0.3%
——0——CVE-2018-9462—0.3%
——0——CVE-2025-21432—0.3%
——0——