Vulnerabilities exploitable today
359,691in 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,665
New KEV · 24H0
Exploit Today ≥ 701,608
Distribution · last window
- Critical2,519
- High11,198
- Medium7,132
- Low649
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2025-65831—11.1%
——3——CVE-2025-57849—11.1%
——3——CVE-2025-54335—11.1%
——3——CVE-2022-50138—11.1%
——3——CVE-2025-33248—11.1%
——3——CVE-2020-3674—11.1%
——3——CVE-2026-25971—11.1%
——3——CVE-2026-32842—11.1%
——3——CVE-2026-12438—11.1%
——3——CVE-2021-47490—11.1%
——3——CVE-2020-11148—11.1%
——3——CVE-2025-46732—11.1%
——3——CVE-2023-21894—11.1%
——3——CVE-2003-1226—11.1%
——3——CVE-2023-52918—11.1%
——3——CVE-2024-26605—11.1%
——3——CVE-2025-14054—11.1%
——3——CVE-2025-64309—11.1%
——3——CVE-2026-99468.3 HIG11.1%
——3Use after free in ANGLE 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)25dCVE-2022-39401—11.1%
——3——CVE-2024-579457.8 HIG11.1%
——3In the Linux kernel, the following vulnerability has been resolved:
riscv: mm: Fix the out of bound issue of vmemmap address
In sparse vmemmap model, the virtual address of vmemmap is calculated as:
((struct page *)VMEMMAP_START - (phys_ram_base >> PAGE_SHIFT)).
And the struct page's va can be calculated with an offset:
(vmemmap + (pfn)).
However, when initializing struct pages, kernel actually starts from the
first page from the same section that phys_ram_base belongs to. If the
first page's physical address is not (phys_ram_base >> PAGE_SHIFT), then
we get an va below VMEMMAP_START when calculating va for it's struct page.
For example, if phys_ram_base starts from 0x82000000 with pfn 0x82000, the
first page in the same section is actually pfn 0x80000. During
init_unavailable_range(), we will initialize struct page for pfn 0x80000
with virtual address ((struct page *)VMEMMAP_START - 0x2000), which is
below VMEMMAP_START as well as PCI_IO_END.
This commit fixes this bug by introducing a new variable
'vmemmap_start_pfn' which is aligned with memory section size and using
it to calculate vmemmap address instead of phys_ram_base.11dCVE-2022-27873—11.1%
——3——CVE-2025-68508—11.1%
——3——CVE-2022-50181—11.1%
——3——CVE-2022-50091—11.1%
——3——CVE-2025-7496—11.1%
——3——CVE-2026-8557—11.1%
——3——CVE-2025-42956—11.1%
——3——CVE-2025-61606—11.1%
——3——CVE-2024-39767—11.1%
——3——CVE-2026-6575—11.1%
——3——CVE-2022-48862—11.1%
——3——CVE-2020-1857—11.1%
——3——CVE-2026-5476310.0 CRI11.1%
——3Traefik is an HTTP reverse proxy and load balancer. Prior to v2.11.51, v3.6.22, and v3.7.6, Traefik's BasicAuth, DigestAuth, and ForwardAuth middlewares strip canonical-cased spoofed identity headers before writing Traefik's own value, but do not account for underscore-variant header names, which many backends normalize identically to dashed forms. An attacker able to reach a protected route can inject an underscore-variant header that survives Traefik's stripping and reaches the backend alongside, or on the unauthenticated ForwardAuth authResponseHeaders path instead of, the value Traefik intended to set, spoofing identity or authorization context. This issue is fixed in versions v2.11.51, v3.6.22, and v3.7.6.37dCVE-2025-68267—11.1%
——3——CVE-2025-22802—11.1%
——3——CVE-2022-34312—11.1%
——3——CVE-2025-52451—11.1%
——3——CVE-2021-1568—11.1%
——3——CVE-2024-323854.3 MED11.1%
——3An issue in Kerlink Kerlink Wirnet iStation 868 KerOS v.4.3.3_20200803132042 allows a remote attacker to obtain sensitive information via a boardID and revisionID components29d