Vulnerabilities exploitable today
376,337in 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,713
New KEV · 24H0
Exploit Today ≥ 701,646
Distribution · last window
- Critical2,380
- High8,732
- Medium6,772
- Low724
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-29783—29.9%
——9——CVE-2025-681524.9 MED29.9%
——9Juju is an open source application orchestration engine that enables any application operation on any infrastructure at any scale through special operators called ‘charms’. From versions 2.9 to before 2.9.56 and 3.6 to before 3.6.19, it is possible that a compromised workload machine under a Juju controller can read any log file for any entity in any model at any level. This issue has been patched in versions 2.9.56 and 3.6.19.56dCVE-2024-50541—29.9%
——9——CVE-2021-2232—29.9%
——9——CVE-2026-22325—29.9%
——9——CVE-2026-34579—29.9%
——9——CVE-2026-22331—29.9%
——9——CVE-2025-23538—29.9%
——9——CVE-2026-585307.8 HIG29.9%
——9Heap-based buffer overflow in Windows Resilient File System (ReFS) allows an unauthorized attacker to execute code locally.58dCVE-2026-27046—29.9%
——9——CVE-2022-45307—29.9%
——9——CVE-2026-184088.8 HIG29.9%
——9Untrusted data inclusion in pg_dump in PostgreSQL allows a malicious superuser of the origin server to inject arbitrary code for restore-time execution as the client operating system account running psql to restore the dump, via psql \restrict meta-command input expansion. The fix for CVE-2025-8714 introduced \restrict and \unrestrict to block this attack, but \unrestrict itself was sufficient for an attack. pg_dumpall is also affected. pg_restore is affected when used to generate a plain-format dump. Non-core use of \restrict would be affected, but we've not identified non-core use. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.20dCVE-2018-1962—29.9%
——9——CVE-2026-178967.5 HIG29.9%
——9Use after free in DevTools in Google Chrome prior to 151.0.7922.72 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: Medium)46dCVE-2023-1690—29.9%
——9——CVE-2025-23519—29.9%
——9——CVE-2026-925655.3 MED29.9%
——9Rallly before 4.15.0 contains an information disclosure vulnerability in the polls.get tRPC procedure that returns scheduled-event invitee names and email addresses to unauthenticated callers. Attackers can access a poll's urlId from public invite links to retrieve sensitive invitee information regardless of privacy settings.2dCVE-2022-45305—29.9%
——9——CVE-2024-1621—29.9%
——9——CVE-2025-49545—29.9%
——9——CVE-2003-1215—29.9%
——9——CVE-2025-23555—29.9%
——9——CVE-2023-1688—29.9%
——9——CVE-2021-43937—29.9%
——9——CVE-2019-11151—29.9%
——9——CVE-2025-30352—29.9%
——9——CVE-2026-777758.6 HIG29.9%
——9Headroom's LLM proxy lets a client choose the upstream destination with the x-headroom-base-url request header. _resolve_openai_upstream_base in headroom/proxy/handlers/openai.py accepts the header value, requires only that it parse with an http or https scheme and a hostname, and returns it for use as the upstream base; _select_passthrough_base_url in headroom/providers/proxy_routes.py reads the same header for the passthrough routes. No check rejects loopback, link-local, or RFC 1918 destinations, and because the component is a proxy the upstream response is returned to the caller, so the request reaches internal services and cloud metadata addresses and their responses are disclosed. The Authorization header accompanying the request is forwarded unchanged to the caller-designated host. The pip console script binds 127.0.0.1 by default, but the reference docker-compose.yml ships --host 0.0.0.0 with published ports and no required HEADROOM_PROXY_TOKEN, which the server itself warns about at startup, so a deployment following the shipped compose exposes the affected data-plane routes to the network without authentication.9dCVE-2023-3757—29.9%
——9——CVE-2025-23521—29.9%
——9——CVE-2024-46450—29.9%
——9——CVE-2026-464099.6 CRI29.9%
——9OpenYak is a local-first agent runtime for reliable tool-using models, with a desktop workspace built on top. Prior to version 1.1.3, the OpenYak desktop backend binds an HTTP API to `127.0.0.1:<random port>` (commonly 19141) without server-side Origin validation, loopback authentication, or Content-Type enforcement, and with a wildcard CORS policy. Any webpage a user visits while OpenYak is running can issue cross-origin requests to this local server — the browser acts as a proxy into loopback, bypassing OS-level network isolation. Chained, this lets a malicious page execute arbitrary shell commands on the host (RCE) via the build agent with `permission_presets.bash=true`, shut down the service, and exfiltrate chat history and account PII — with no user interaction beyond opening the page. Version 1.1.3 patches the issue.39dCVE-2025-45609—29.9%
——9——CVE-2024-5955—29.9%
——9——CVE-2024-13351—29.9%
——9——CVE-2025-30445—29.9%
——9——CVE-2023-3853—29.9%
——9——CVE-2025-23587—29.9%
——9——CVE-2024-8920—29.9%
——9——CVE-2014-1845—29.9%
——9——CVE-2023-41335—29.9%
——9——