Vulnerabilities exploitable today
350,369in 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,651
New KEV · 24H4
Exploit Today ≥ 701,587
Distribution · last window
- Critical1,484
- High4,943
- Medium4,052
- Low320
Window
Severity
Flags
CVECVSSEPSSKEVRExploitTitleMod.
CVE-2026-16405——
——0Information disclosure in the Networking: WebSockets component. This vulnerability was fixed in Firefox 153 and Firefox ESR 140.13.4hCVE-2026-16371——
——0Privilege escalation in the DOM: Navigation component. This vulnerability was fixed in Firefox 153 and Firefox ESR 140.13.4hCVE-2026-16368——
——0Incorrect boundary conditions in the JavaScript: WebAssembly component. This vulnerability was fixed in Firefox 153 and Firefox ESR 140.13.4hCVE-2026-16357——
——0Incorrect boundary conditions in the Graphics component. This vulnerability was fixed in Firefox 153, Firefox ESR 115.38, and Firefox ESR 140.13.4hCVE-2026-16370——
——0Mitigation bypass in the DOM: Networking component. This vulnerability was fixed in Firefox 153.4hCVE-2026-64627——
——0Parse Server versions >= 9.0.0 before 9.10.0-alpha.4 and versions before 8.6.85 contain a schema disclosure vulnerability. When the GraphQL API is mounted with public introspection disabled (graphQLPublicIntrospection: false, the default), schema-derived 'Did you mean ...?' suggestions were still returned in GraphQL error messages produced during variable coercion, which were not covered by the introspection-hardening control (that only handled validation errors). An unauthenticated caller possessing only the public application id can iteratively recover hidden schema identifiers — including registered Cloud Code function names and Parse class and field names — by submitting queries or mutations whose variables contain near-miss enum values or input-object field names. This is a follow-up bypass of GHSA-8cph-rgr4-g5vj. The issue is fixed in 9.10.0-alpha.4 and 8.6.85.5hCVE-2026-16369——
——0Integer overflow in the JavaScript: WebAssembly component. This vulnerability was fixed in Firefox 153 and Firefox ESR 140.13.4hCVE-2026-16391——
——0Information disclosure in the Storage: IndexedDB component. This vulnerability was fixed in Firefox 153 and Firefox ESR 140.13.4hCVE-2026-16392——
——0JIT miscompilation in the JavaScript Engine: JIT component. This vulnerability was fixed in Firefox 153.4hCVE-2026-16367——
——0Sandbox escape due to invalid pointer in the Disability Access APIs component. This vulnerability was fixed in Firefox 153.4hCVE-2026-16366——
——0Privilege escalation in the DOM: Navigation component. This vulnerability was fixed in Firefox 153.4hCVE-2026-16393——
——0Incorrect boundary conditions in the Graphics: WebGPU component. This vulnerability was fixed in Firefox 153.4hCVE-2026-16394——
——0Mitigation bypass in the DOM: Security component. This vulnerability was fixed in Firefox 153.4hCVE-2026-16395——
——0Integer overflow in the Audio/Video component. This vulnerability was fixed in Firefox 153.4hCVE-2026-16365——
——0Privilege escalation in the DOM: Workers component. This vulnerability was fixed in Firefox 153.4hCVE-2026-16350——
——0Incorrect boundary conditions in the Audio/Video: cubeb component. This vulnerability was fixed in Firefox 153, Firefox ESR 115.38, and Firefox ESR 140.13.4hCVE-2026-16411——
——0Memory safety bugs present in Firefox 152. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vulnerability was fixed in Firefox 153.4hCVE-2025-66390——
——0In Microsoft Azure API Management through 2025-10-17, when self-service signup (username/password Basic Authentication) is enabled in Tenant A, an attacker can reuse the registration flow by changing the hostname or tenant identifier to Tenant B, even when Tenant B has signup disabled at the UI level. In other words, disabling signup in the UI does not disable the underlying API endpoint (which still accepts cross-tenant requests based on the Host header). NOTE: The supplier states that they evaluated the report and determined it did not cross a security boundary (i.e., the observed behavior was a configuration/state issue rather than an exploitable product vulnerability affecting tenant isolation). NOTE: The supplier evaluated this report and determined that it did not cross a security boundary (i.e., the observed behavior was a configuration/state issue rather than an exploitable product vulnerability affecting tenant isolation).3hCVE-2026-62415——
——0The Joomla extension Membership Pro prior version 4.6.2 did by default allow unauthenticated users to upload media assets.7hCVE-2026-16396——
——0Privilege escalation in WebExtensions. This vulnerability was fixed in Firefox 153 and Firefox ESR 140.13.4hCVE-2026-16397——
——0Clickjacking issue in the WebExtensions component in Firefox for Android. This vulnerability was fixed in Firefox 153.4hCVE-2026-164477.3 HIG—
——0A vulnerability has been found in D-Link DNS-320 1.0.2. Impacted is an unknown function of the file /web/jquery/uploader/multi_uploadify.php. The manipulation of the argument Filedata[] leads to unrestricted upload. Remote exploitation of the attack is possible. The exploit has been disclosed to the public and may be used.3hCVE-2026-16398——
——0Site isolation issue in the Graphics component. This vulnerability was fixed in Firefox 153.4hCVE-2026-213705.3 MED0.0%
——0Memory Corruption when validating input batch size and buffer plane count exceeds maximum allowed values.14dCVE-2026-16364——
——0Incorrect boundary conditions in the Audio/Video: Playback component. This vulnerability was fixed in Firefox 153.4hCVE-2026-16363——
——0JIT miscompilation in the JavaScript: WebAssembly component. This vulnerability was fixed in Firefox 153 and Firefox ESR 140.13.4hCVE-2026-16362——
——0Use-after-free in the WebRTC: Audio/Video component. This vulnerability was fixed in Firefox 153 and Firefox ESR 140.13.4hCVE-2026-16361——
——0Memory safety bugs present in Firefox ESR 115.37 and Firefox ESR 140.12. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code. This vulnerability was fixed in Firefox ESR 115.38 and Firefox ESR 140.13.4hCVE-2026-16359——
——0Incorrect boundary conditions in the Audio/Video: GMP component. This vulnerability was fixed in Firefox 153, Firefox ESR 115.38, and Firefox ESR 140.13.4hCVE-2026-471216.1 MED—
——0Sparkle is a software update framework for macOS. Prior to version 2.9.2, `Autoupdate/SUBinaryDeltaApply.m` enforces `relativePath.pathComponents containsObject:@".."` and rejects writes whose immediate parent directory IS itself a symbolic link, but does not detect symlinks deeper in the relative path. `Autoupdate/SPUSparkleDeltaArchive.m`'s `extractItem:` will create symlinks in the destination tree from archive content (no `..` check on the symlink target), and a subsequent `Extract` item targeting `<symlink>/foo/bar` then escapes the destination tree via `fopen(path, "wb")` because the kernel resolves the intermediate symlink during the open call. This is a defense-in-depth issue: exploitation requires a maliciously-crafted `.delta` that passes EdDSA signature verification, i.e. EdDSA private-key compromise. With the AppInstaller running as root for system-domain installs, it gives the holder of a stolen signing key arbitrary file write at root level via the delta-apply path, which is a strictly broader primitive than the "drop-in replacement bundle" install they would otherwise have. Version 2.9.2 contains a patch for the issue.3hCVE-2026-598475.9 MED—
——0A flaw was found in libssh. Incorrect AES-GCM finalization checks in builds using the OpenSSL backend can effectively remove integrity protection, allowing an in-path attacker to modify plaintext on the wire without detection.3hCVE-2026-158115.8 MED0.0%
——0A vulnerability was found in kronosnet's (version <=1.34) cryptographic configuration management. The framework does not correctly zero-out or wipe sensitive memory segments after executing changes to its cryptographic configuration. This omission leaves raw encryption keys resident in memory after the associated structures are freed. A local attacker capable of leveraging memory disclosure techniques could exploit this flaw to retrieve the active encryption key, allowing them to decrypt cluster network communications or inject malicious packets to cause severe high-availability cluster instability.11hCVE-2026-16407——
——0Mitigation bypass in the DOM: Service Workers component. This vulnerability was fixed in Firefox 153.4hCVE-2026-16356——
——0Sandbox escape due to use-after-free in the Disability Access APIs component. This vulnerability was fixed in Firefox 153, Firefox ESR 115.38, and Firefox ESR 140.13.4hCVE-2026-16408——
——0Integer overflow in the Audio/Video: Playback component. This vulnerability was fixed in Firefox 153.4hCVE-2026-82854.3 MED—
——0Improper restriction of excessive authentication attempts vulnerability in Universal Software Inc. FlexCity allows Excessive Allocation.
This issue affects FlexCity: from 5.536.0 through 11052026.4hCVE-2026-9499——
——0An out-of-bounds read (buffer over-read) vulnerability exists in QTextCodec::codecForName() in Qt. When the function is called with a QByteArray that is not NUL-terminated (for example, one created with QByteArray::fromRawData()), the codec-name matching routine reads past the end of the supplied buffer. In most cases this results in an incorrect text codec being selected; in the worst case, if the over-read reaches unmapped memory, the process crashes (denial of service). The over-read is bounded by the length of the longest codec-name candidate, and the out-of-bounds bytes are only compared internally against Qt's fixed list of codec names, so no data is disclosed to an attacker. Applications that do not pass non-NUL-terminated QByteArrays to QTextCodec::codecForName() are not exposed. The affected code resides in the Qt5Compat module from Qt 6.0.0 onward, and in Qt Core (qtbase) in Qt 4.x and Qt 5.x.3hCVE-2026-16404——
——0Spoofing issue in Firefox for Android. This vulnerability was fixed in Firefox 153.4hCVE-2026-0121—0.0%
——0——CVE-2026-16406——
——0Mitigation bypass in the Networking component. This vulnerability was fixed in Firefox 153.4h