Vulnerabilities exploitable today
355,213in 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,523
- High9,111
- Medium7,331
- Low692
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2023-42433—6.9%
——2——CVE-2026-30985—6.9%
——2——CVE-2026-272908.6 HIG6.9%
——2Adobe Framemaker versions 2022.8 and earlier are affected by an Untrusted Search Path vulnerability that might allow attackers to execute arbitrary code in the context of the current user. If the application uses a search path to locate critical resources such as programs, then an attacker could modify that search path to point to a malicious program, which the targeted application would then execute. Exploitation of this issue does not require user interaction.10dCVE-2023-52645—6.9%
——2——CVE-2024-27003—6.9%
——2——CVE-2024-57963—6.9%
——2——CVE-2026-40243—6.9%
——2——CVE-2025-383958.4 HIG6.9%
——2In the Linux kernel, the following vulnerability has been resolved:
regulator: gpio: Fix the out-of-bounds access to drvdata::gpiods
drvdata::gpiods is supposed to hold an array of 'gpio_desc' pointers. But
the memory is allocated for only one pointer. This will lead to
out-of-bounds access later in the code if 'config::ngpios' is > 1. So
fix the code to allocate enough memory to hold 'config::ngpios' of GPIO
descriptors.
While at it, also move the check for memory allocation failure to be below
the allocation to make it more readable.5dCVE-2022-50871—6.9%
——2——CVE-2026-100018.3 HIG6.9%
——2Use after free in PerformanceManager in Google Chrome prior to 148.0.7778.216 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)14dCVE-2026-351453.1 LOW6.9%
——2HCL DFXAnalytics is affected by a Missing HTTP Strict-Transport-Security Header vulnerability. The application fails to implement the HTTP Strict Transport Security (HSTS) policy within its responses, which could allow a remote attacker to downgrade the communication channel to an unencrypted connection (HTTP) and conduct man-in-the-middle (MitM) attacks. To remediate this, the application must include the "Strict-Transport-Security" header in all web application responses.18dCVE-2026-61795.4 MED6.9%
——2Stored Cross Site Scripting in NightWolf Penetration Testing Platform allows attack trigger and run malicious script in user's browser28dCVE-2023-41069—6.9%
——2——CVE-2021-35097—6.9%
——2——CVE-2024-32589—6.9%
——2——CVE-2024-27002—6.9%
——2——CVE-2021-37686—6.9%
——2——CVE-2026-64417—6.9%
——2In the Linux kernel, the following vulnerability has been resolved:
mm: shrinker: fix NULL pointer dereference in debugfs
shrinker_debugfs_add() creates both "count" and "scan" debugfs files
unconditionally.
That assumes every shrinker implements both count_objects() and
scan_objects(), which is not guaranteed. For example, the xen-backend
shrinker sets count_objects() but leaves scan_objects() NULL, so writing
to its scan file calls through a NULL function pointer and panics the
kernel:
BUG: kernel NULL pointer dereference, address: 0000000000000000
RIP: 0010:0x0
Code: Unable to access opcode bytes at 0xffffffffffffffd6.
Call Trace:
<TASK>
shrinker_debugfs_scan_write+0x12e/0x270
full_proxy_write+0x5f/0x90
vfs_write+0xde/0x420
? filp_flush+0x75/0x90
? filp_close+0x1d/0x30
? do_dup2+0xb8/0x120
ksys_write+0x68/0xf0
? filp_flush+0x75/0x90
do_syscall_64+0xb3/0x5b0
entry_SYSCALL_64_after_hwframe+0x76/0x7e
The count path has the same issue in principle if a shrinker omits
count_objects().
To fix it, only create "count" and "scan" debugfs files when the
corresponding callbacks are present.10dCVE-2023-5993—6.9%
——2——CVE-2021-46925—6.9%
——2——CVE-2023-43078—6.9%
——2——CVE-2022-50863—6.9%
——2——CVE-2025-65009—6.9%
——2——CVE-2024-13115—6.9%
——2——CVE-2022-50232—6.9%
——2——CVE-2023-35140—6.9%
——2——CVE-2017-13231—6.9%
——2——CVE-2026-483888.6 HIG6.9%
——2Adobe Photoshop Installer was affected by an Uncontrolled Search Path Element vulnerability that could have resulted in arbitrary code execution in the context of the current user. An attacker could have exploited this vulnerability by placing a malicious library in a directory searched by the installer. Exploitation of this issue required user interaction in that a victim must have been running the installer. Scope is changed.7dCVE-2026-31795—6.9%
——2——CVE-2023-42928—6.9%
——2——CVE-2025-40829—6.9%
——2——CVE-2023-30660—6.9%
——2——CVE-2023-30662—6.9%
——2——CVE-2022-36866—6.9%
——2——CVE-2019-9463—6.9%
——2——CVE-2026-99888.3 HIG6.9%
——2Use after free in WebRTC in Google Chrome on Linux prior to 148.0.7778.216 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)14dCVE-2026-348136.4 MED6.9%
——2Endian Firewall version 3.3.25 and prior allow stored cross-site scripting (XSS) via the user parameter to /cgi-bin/proxyuser.cgi. An authenticated attacker can inject arbitrary JavaScript that is stored and executed when other users view the affected page.11dCVE-2025-20956—6.9%
——2——CVE-2026-272947.8 HIG6.9%
——2Adobe Framemaker versions 2022.8 and earlier are affected by an out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.10dCVE-2026-272967.8 HIG6.9%
——2Adobe Framemaker versions 2022.8 and earlier are affected by an Integer Underflow (Wrap or Wraparound) vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.10d