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,382
- High8,758
- Medium6,800
- Low731
Filters
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-529567.5 HIG29.5%
——9In the Linux kernel, the following vulnerability has been resolved:
libceph: Fix potential out-of-bounds access in __ceph_x_decrypt()
In __ceph_x_decrypt(), a part of the buffer p is interpreted as a
ceph_x_encrypt_header, and the magic field of this struct is accessed.
This happens without any guarantee that the buffer is large enough to
hold this struct. The function parameter ciphertext_len represents the
length of the ciphertext to decrypt and is guaranteed to be at most the
remaining size of the allocated buffer p. However, this value is not
necessarily greater than sizeof(ceph_x_encrypt_header). E.g., a message
frame of type FRAME_TAG_AUTH_REPLY_MORE, that is just as long to hold
the ciphertext at its end with a ciphertext_len of 8 or less, can
trigger an out-of-bounds memory access when accessing hdr->magic.
This patch fixes the issue by adding a check to ensure that the
decrypted plaintext in the buffer is large enough to represent at least
the ceph_x_encrypt_header.66dCVE-2018-15000—29.5%
——9——CVE-2025-48246—29.5%
——9——CVE-2025-12865—29.5%
——9——CVE-2024-30181—29.5%
——9——CVE-2024-30444—29.5%
——9——CVE-2023-5233—29.5%
——9——CVE-2024-55024—29.5%
——9——CVE-2024-30452—29.5%
——9——CVE-2025-13244—29.5%
——9——CVE-2024-20377—29.5%
——9——CVE-2024-52967—29.5%
——9——CVE-2020-5833—29.5%
——9——CVE-2023-5232—29.5%
——9——CVE-2026-4676—29.5%
——9——CVE-2017-10709—29.5%
——9——CVE-2008-7316—29.5%
——9——CVE-2010-0791—29.5%
——9——CVE-2004-2335—29.5%
——9——CVE-1999-1382—29.5%
——9——CVE-2024-29813—29.5%
——9——CVE-2025-50229—29.5%
——9——CVE-2025-12298—29.5%
——9——CVE-2013-4161—29.5%
——9——CVE-2025-42878—29.5%
——9——CVE-2025-60540—29.5%
——9——CVE-2025-49294—29.5%
——9——CVE-2024-24455—29.5%
——9——CVE-2025-22855—29.5%
——9——CVE-2024-29815—29.5%
——9——CVE-2006-1284—29.5%
——9——CVE-2013-5740—29.5%
——9——CVE-2026-73374—29.5%
——9A stored cross-site scripting (XSS) vulnerability existed in Vulnerability-Lookup in the render_tag_badges Jinja filter used to display reference tags associated with vulnerability records.
Values from containers.cna.references[].tags[] were directly interpolated into HTML badge elements and the resulting string was wrapped in markupsafe.Markup. Because Markup marks the generated content as safe, Jinja's automatic HTML escaping was bypassed.
An authenticated user with permissions to create or modify vulnerability records, such as a user holding the vulnerability:create or vulnerability:modify permission, could submit a crafted reference tag through the CNA API containing arbitrary HTML or JavaScript-capable markup.
The malicious value would subsequently be stored as part of the vulnerability record. When another user visited the corresponding public /cve/<id> or /vuln/<id> page, the crafted tag would be rendered as HTML in the viewer's browser. This could result in JavaScript execution in the security context of the Vulnerability-Lookup application.
Successful exploitation could allow an attacker to perform actions in the context of a victim, access information available to the victim's browser session, or modify page content. As the affected vulnerability pages can be accessed publicly, exploitation may affect users who are not authenticated.
The issue was corrected by applying markupsafe.escape() to each reference tag before inserting it into the HTML badge markup, while retaining Markup only for the static HTML scaffolding.23dCVE-2025-0953—29.5%
——9——CVE-2025-3319—29.5%
——9——CVE-2025-10374—29.5%
——9——CVE-2017-6267—29.5%
——9——CVE-2025-2239—29.5%
——9——CVE-2014-1257—29.5%
——9——CVE-2026-39498—29.5%
——9——