Export limit exceeded: 335011 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 335011 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (335011 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-27904 | 1 Isaacs | 1 Minimatch | 2026-02-26 | 7.5 High |
| minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Prior to version 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.4, nested `*()` extglobs produce regexps with nested unbounded quantifiers (e.g. `(?:(?:a|b)*)*`), which exhibit catastrophic backtracking in V8. With a 12-byte pattern `*(*(*(a|b)))` and an 18-byte non-matching input, `minimatch()` stalls for over 7 seconds. Adding a single nesting level or a few input characters pushes this to minutes. This is the most severe finding: it is triggered by the default `minimatch()` API with no special options, and the minimum viable pattern is only 12 bytes. The same issue affects `+()` extglobs equally. Versions 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.4 fix the issue. | ||||
| CVE-2026-27903 | 1 Isaacs | 1 Minimatch | 2026-02-26 | 7.5 High |
| minimatch is a minimal matching utility for converting glob expressions into JavaScript RegExp objects. Prior to version 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.3, `matchOne()` performs unbounded recursive backtracking when a glob pattern contains multiple non-adjacent `**` (GLOBSTAR) segments and the input path does not match. The time complexity is O(C(n, k)) -- binomial -- where `n` is the number of path segments and `k` is the number of globstars. With k=11 and n=30, a call to the default `minimatch()` API stalls for roughly 5 seconds. With k=13, it exceeds 15 seconds. No memoization or call budget exists to bound this behavior. Any application where an attacker can influence the glob pattern passed to `minimatch()` is vulnerable. The realistic attack surface includes build tools and task runners that accept user-supplied glob arguments (ESLint, Webpack, Rollup config), multi-tenant systems where one tenant configures glob-based rules that run in a shared process, admin or developer interfaces that accept ignore-rule or filter configuration as globs, and CI/CD pipelines that evaluate user-submitted config files containing glob patterns. An attacker who can place a crafted pattern into any of these paths can stall the Node.js event loop for tens of seconds per invocation. The pattern is 56 bytes for a 5-second stall and does not require authentication in contexts where pattern input is part of the feature. Versions 10.2.3, 9.0.7, 8.0.6, 7.4.8, 6.2.2, 5.1.8, 4.2.5, and 3.1.3 fix the issue. | ||||
| CVE-2025-53627 | 2 Google, Meshtastic | 3 Android, Firmware, Meshtastic Firmware | 2026-02-26 | 5.3 Medium |
| Meshtastic is an open source mesh networking solution. The Meshtastic firmware (starting from version 2.5) introduces asymmetric encryption (PKI) for direct messages, but when the `pki_encrypted` flag is missing, the firmware silently falls back to legacy AES-256-CTR channel encryption. This was an intentional decision to maintain backwards compatibility. However, the end-user applications, like Web app, iOS/Android app, and applications built on top of Meshtastic using the SDK, did not have a way to differentiate between end-to-end encrypted DMs and the legacy DMs. This creates a downgrade attack path where adversaries who know a shared channel key can craft and inject spoofed direct messages that are displayed as if they were PKC encrypted. Users are not given any feedback of whether a direct message was decrypted with PKI or with legacy symmetric encryption, undermining the expected security guarantees of the PKI rollout. Version 2.7.15 fixes this issue. | ||||
| CVE-2025-20645 | 2 Google, Mediatek | 15 Android, Mt6765, Mt6768 and 12 more | 2026-02-26 | 7.8 High |
| In KeyInstall, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege if a malicious actor has already obtained the System privilege. User interaction is not needed for exploitation. Patch ID: ALPS09475476; Issue ID: MSV-2599. | ||||
| CVE-2025-20646 | 1 Mediatek | 6 Mt6890, Mt7915, Mt7916 and 3 more | 2026-02-26 | 9.8 Critical |
| In wlan AP FW, there is a possible out of bounds write due to improper input validation. This could lead to remote escalation of privilege with no additional execution privileges needed. User interaction is not needed for exploitation. Patch ID: WCNCR00389074; Issue ID: MSV-1803. | ||||
| CVE-2025-20650 | 5 Google, Linuxfoundation, Mediatek and 2 more | 25 Android, Yocto, Mt2737 and 22 more | 2026-02-26 | 6.8 Medium |
| In da, there is a possible out of bounds write due to a missing bounds check. This could lead to local escalation of privilege, if an attacker has physical access to the device, with no additional execution privileges needed. User interaction is needed for exploitation. Patch ID: ALPS09291294; Issue ID: MSV-2061. | ||||
| CVE-2024-45580 | 2026-02-26 | 7.8 High | ||
| Memory corruption while handling multuple IOCTL calls from userspace for remote invocation. | ||||
| CVE-2024-49836 | 2026-02-26 | 7.8 High | ||
| Memory corruption may occur during the synchronization of the camera`s frame processing pipeline. | ||||
| CVE-2024-53011 | 1 Qualcomm | 166 Fastconnect 6700, Fastconnect 6700 Firmware, Fastconnect 6900 and 163 more | 2026-02-26 | 7.9 High |
| Information disclosure may occur due to improper permission and access controls to Video Analytics engine. | ||||
| CVE-2024-53012 | 2026-02-26 | 7.8 High | ||
| Memory corruption may occur due to improper input validation in clock device. | ||||
| CVE-2024-53014 | 1 Qualcomm | 502 215, 215 Firmware, 315 5g Iot Modem and 499 more | 2026-02-26 | 7.8 High |
| Memory corruption may occur while validating ports and channels in Audio driver. | ||||
| CVE-2024-53022 | 1 Qualcomm | 46 Qam8255p, Qam8255p Firmware, Qam8295p and 43 more | 2026-02-26 | 7.8 High |
| Memory corruption may occur during communication between primary and guest VM. | ||||
| CVE-2024-53023 | 1 Qualcomm | 206 Ar8035, Ar8035 Firmware, Fastconnect 6900 and 203 more | 2026-02-26 | 7.8 High |
| Memory corruption may occur while accessing a variable during extended back to back tests. | ||||
| CVE-2024-53024 | 1 Qualcomm | 332 Ar8035, Ar8035 Firmware, Csra6620 and 329 more | 2026-02-26 | 7.8 High |
| Memory corruption in display driver while detaching a device. | ||||
| CVE-2024-53028 | 2026-02-26 | 7.8 High | ||
| Memory corruption may occur while processing message from frontend during allocation. | ||||
| CVE-2024-53029 | 2026-02-26 | 7.8 High | ||
| Memory corruption while reading a value from a buffer controlled by the Guest Virtual Machine. | ||||
| CVE-2024-53030 | 1 Qualcomm | 88 Msm8996au, Msm8996au Firmware, Qam8255p and 85 more | 2026-02-26 | 7.8 High |
| Memory corruption while processing input message passed from FE driver. | ||||
| CVE-2024-53031 | 1 Qualcomm | 52 Qam8255p, Qam8255p Firmware, Qam8295p and 49 more | 2026-02-26 | 7.8 High |
| Memory corruption while reading a type value from a buffer controlled by the Guest Virtual Machine. | ||||
| CVE-2024-53032 | 1 Qualcomm | 52 Qam8255p, Qam8255p Firmware, Qam8295p and 49 more | 2026-02-26 | 7.8 High |
| Memory corruption may occur in keyboard virtual device due to guest VM interaction. | ||||
| CVE-2024-53033 | 1 Qualcomm | 16 Fastconnect 6900, Fastconnect 6900 Firmware, Fastconnect 7800 and 13 more | 2026-02-26 | 7.8 High |
| Memory corruption while doing Escape call when user provides valid kernel address in the place of valid user buffer address. | ||||