Vulnerabilities exploitable today
354,470in current view
Single score combining CVSS, KEV membership and EPSS. Every CVE with its own record — timeline from publication to active exploitation.
In KEV catalog1,656
New KEV · 24H0
Exploit Today ≥ 701,602
Distribution · last window
- Critical2,643
- High9,463
- Medium7,694
- Low694
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2022-50447—4.7%
——1——CVE-2022-29470—4.7%
——1——CVE-2026-31954—4.7%
——1——CVE-2024-35968—4.7%
——1——CVE-2022-25864—4.7%
——1——CVE-2020-37064—4.7%
——1——CVE-2020-37091—4.7%
——1——CVE-2026-42842—4.7%
——1——CVE-2023-28405—4.7%
——1——CVE-2025-25104—4.7%
——1——CVE-2023-25944—4.7%
——1——CVE-2025-71135—4.7%
——1——CVE-2021-39663—4.7%
——1——CVE-2020-0150—4.7%
——1——CVE-2025-30077—4.7%
——1——CVE-2026-420146.6 MED4.7%
——1A flaw was found in GnuTLS. The `gnutls_pkcs11_token_set_pin` function, used for changing the Security Officer PIN, can lead to a use-after-free vulnerability. This occurs when an attacker attempts to change the PIN with a NULL old PIN for a token that lacks a protected authentication path.9dCVE-2026-45335—4.7%
——1——CVE-2017-20226—4.7%
——1——CVE-2024-22184—4.7%
——1——CVE-2020-36935—4.7%
——1——CVE-2020-0102—4.7%
——1——CVE-2020-0273—4.7%
——1——CVE-2026-602717.8 HIG4.7%
——1Vulnerability in the Oracle Coherence product of Oracle Fusion Middleware (component: Core). Supported versions that are affected are 12.2.1.4.0, 14.1.1.0.0, 14.1.2.0.0 and 15.1.1.0.0. Easily exploitable vulnerability allows low privileged attacker with logon to the infrastructure where Oracle Coherence executes to compromise Oracle Coherence. Successful attacks of this vulnerability can result in takeover of Oracle Coherence. CVSS 3.1 Base Score 7.8 (Confidentiality, Integrity and Availability impacts). CVSS Vector: (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).4dCVE-2022-50241—4.7%
——1——CVE-2025-57983—4.7%
——1——CVE-2026-437497.8 HIG4.7%
——1A parsing issue in the handling of directory paths was addressed with improved path validation. This issue is fixed in macOS Sequoia 15.7.8, macOS Sonoma 14.8.8, macOS Tahoe 26.6. An app may be able to gain root privileges.3dCVE-2023-40685—4.7%
——1——CVE-2025-39865—4.6%
——1——CVE-2021-35092—4.6%
——1——CVE-2024-23909—4.6%
——1——CVE-2022-41593—4.6%
——1——CVE-2026-546567.8 HIG4.6%
——1datamodel-code-generator generates Pydantic v2 models, dataclasses, TypedDict, and msgspec.Struct from OpenAPI, JSON Schema, GraphQL, Avro, Protobuf, and raw JSON, YAML, or CSV. From 0.52.1 until 0.60.2, datamodel-code-generator interpolates validators from --extra-template-data in src/datamodel_code_generator/model/pydantic_v2/base_model.py through _process_validators into @field_validator decorators without safe validation, allowing Python code execution when the generated Pydantic v2 model is imported. This issue is fixed in version 0.60.2.14hCVE-2024-23907—4.6%
——1——CVE-2025-71180—4.6%
——1——CVE-2021-35118—4.6%
——1——CVE-2022-39844—4.6%
——1——CVE-2024-0043—4.6%
——1——CVE-2026-648214.3 MED4.6%
——1djangoSIGE through 1.10 (commit a6fe7e8) contains a cross-site request forgery vulnerability that allows unauthenticated attackers to cancel sales or purchase orders on behalf of authenticated users by exploiting order-cancellation logic implemented inside HTTP GET method handlers in CancelarOrcamentoVendaView, CancelarPedidoVendaView, CancelarOrcamentoCompraView, and CancelarPedidoCompraView. Attackers can lure an authenticated victim with change_orcamentovenda or equivalent permissions to a page containing a cross-origin reference such as an img tag pointing to the cancellation endpoint, bypassing CSRF token validation entirely since Django's CsrfViewMiddleware only enforces CSRF checks on unsafe HTTP methods.8dCVE-2026-554385.8 MED4.6%
——1Coder allows organizations to provision remote development environments via Terraform. Prior to versions 2.29.17, 2.32.7, 2.33.8, and 2.34.2, Coder's subdomain-based workspace app proxy allowed the same-owner CORS check to be bypassed. When a workspace-name subdomain segment parsed as a UUID, the workspace was resolved by ID without confirming the URL's username matched the real owner, while the CORS middleware trusted the unverified username in the hostname. Practical exploitation requires subdomain app routing (wildcard hostname) enabled and a victim who visits the attacker's crafted app URL while authenticated. The fix in versions 2.29.17, 2.32.7, 2.33.8, and 2.34.2 validates the subdomain username against the resolved workspace's actual owner and bases the same-owner CORS decision on the authoritative owner identity. No known workarounds are available.23dCVE-2025-38081—4.6%
——1——