Vulnerabilities exploitable today
354,630in 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,601
Distribution · last window
- Critical2,639
- High9,425
- Medium7,646
- Low704
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2022-50252—5.0%
——2——CVE-2024-2431—5.0%
——2——CVE-2025-20201—5.0%
——2——CVE-2025-9513—5.0%
——2——CVE-2023-34470—5.0%
——2——CVE-2023-28758—5.0%
——2——CVE-2025-20890—5.0%
——2——CVE-2022-50283—5.0%
——2——CVE-2024-58240—5.0%
——2——CVE-2025-38219—5.0%
——2——CVE-2026-393465.4 MED5.0%
——2OrangeHRM is a comprehensive human resource management (HRM) system. From 5.0 to 5.8, OrangeHRM Open Source allowed authenticated users to bypass disabled-module access controls via URL-encoded request paths and access functionality of modules disabled by an administrator. This vulnerability is fixed in 5.8.1.7dCVE-2026-23758—5.0%
——2——CVE-2024-41689—5.0%
——2——CVE-2024-12115—5.0%
——2——CVE-2026-337622.8 LOW5.0%
——2go-git is an extensible git implementation library written in pure Go. Prior to version 5.17.1, go-git’s index decoder for format version 4 fails to validate the path name prefix length before applying it to the previously decoded path name. A maliciously crafted index file can trigger an out-of-bounds slice operation, resulting in a runtime panic during normal index parsing. This issue only affects Git index format version 4. Earlier formats (go-git supports only v2 and v3) are not vulnerable to this issue. This issue has been patched in version 5.17.1.7dCVE-2026-1979—5.0%
——2——CVE-2026-12460—5.0%
——2——CVE-2022-50401—5.0%
——2——CVE-2022-31466—5.0%
——2——CVE-2025-1253—5.0%
——2——CVE-2024-23306—5.0%
——2——CVE-2026-90736.2 MED5.0%
——2A flaw was found in foreman-mcp-server. This component utilizes two distinct logging mechanisms that can expose sensitive session and authentication data. One mechanism logs session identifiers, which are treated as authentication credentials, at an informational level. The other, when debug logging is enabled, incompletely sanitizes HTTP request headers, leading to the cleartext logging of sensitive information such as authorization tokens and API keys. This vulnerability can result in a confidentiality breach, as sensitive authentication data is persisted in plain text within container logs, increasing the risk if logs are forwarded to a centralized platform.16dCVE-2022-50240—5.0%
——2——CVE-2020-0334—5.0%
——2——CVE-2022-50499—5.0%
——2——CVE-2024-47967—5.0%
——2——CVE-2026-3106—5.0%
——2——CVE-2025-31982—5.0%
——2——CVE-2026-479056.2 MED5.0%
——2CAI Content Credentials versions c2pa-web@0.7.1, c2pa-v0.80.1 and earlier are affected by an Uncontrolled Resource Consumption vulnerability. An attacker could exploit this vulnerability to exhaust system resources, resulting in an application denial-of-service condition. Exploitation of this issue does not require user interaction.8dCVE-2025-38231—5.0%
——2——CVE-2025-20888—5.0%
——2——CVE-2023-53454—5.0%
——2——CVE-2025-23399—5.0%
——2——CVE-2024-22312—5.0%
——2——CVE-2026-483546.2 MED5.0%
——2CAI Content Credentials is affected by an Integer Overflow or Wraparound vulnerability that could result in an application denial-of-service. An attacker could exploit this vulnerability to crash the application, leading to a denial-of-service condition. Exploitation of this issue does not require user interaction.15dCVE-2026-45854—5.0%
——2——CVE-2025-23400—5.0%
——2——CVE-2025-23398—5.0%
——2——CVE-2022-45112—5.0%
——2——CVE-2024-33016—5.0%
——2——