Export limit exceeded: 417877 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 417877 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 417877 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (417877 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2024-5617 | 1 Wso2 | 6 Api Manager, Identity Server, Wso2 Api Manager and 3 more | 2026-11-02 | 4.8 Medium |
| The account lock feature fails to correctly enforce account lockouts on the primary user store when users with identical usernames exist in both primary and secondary user stores. This occurs because the lock condition is only applied to the secondary user store account in such scenarios, allowing continued authentication attempts against the primary user store account. This functional flaw enables brute force attacks. By systematically attempting different passwords against the primary user store account, an attacker can potentially gain unauthorized access to sensitive information or accounts, as the intended account lockout mechanism does not prevent repeated login attempts. | ||||
| CVE-2026-102560 | 3 Gnome, Libsoup, Redhat | 6 Libsoup, Libsoup, Enterprise Linux and 3 more | 2026-11-02 | 8.6 High |
| A flaw was found in libsoup. When the permessage-deflate WebSocket extension compresses a very large outgoing message, truncated size calculations used for GByteArray growth could wrap, causing zlib to write past the allocated buffer and resulting in a heap buffer overflow. | ||||
| CVE-2026-102559 | 3 Gnome, Libsoup, Redhat | 10 Libsoup, Libsoup, Enterprise Linux and 7 more | 2026-11-02 | 8.6 High |
| A flaw was found in libsoup. When constructing a masked WebSocket client frame for a very large outgoing payload, size values passed to GByteArray allocation APIs could be truncated while the masking routine still used the full length, causing a heap buffer overflow. | ||||
| CVE-2026-102558 | 3 Gnome, Libsoup, Redhat | 10 Libsoup, Libsoup, Enterprise Linux and 7 more | 2026-11-02 | 8.6 High |
| A flaw was found in libsoup. When max-incoming-payload-size is unlimited (0), SoupWebsocketConnection could grow its incoming GByteArray based on an attacker-controlled frame length until the length wrapped, causing a heap buffer overflow while reading frame data. | ||||
| CVE-2026-102557 | 3 Gnome, Libsoup, Redhat | 10 Libsoup, Libsoup, Enterprise Linux and 7 more | 2026-11-02 | 8.6 High |
| A flaw was found in libsoup. When reassembling fragmented WebSocket messages into a GByteArray, libsoup did not adequately cap total message size against the limits of the underlying buffer type. A remote peer could send fragments that caused size truncation while the implementation still used the full length, leading to heap corruption or a crash. | ||||
| CVE-2026-102556 | 3 Gnome, Libsoup, Redhat | 10 Libsoup, Libsoup, Enterprise Linux and 7 more | 2026-11-02 | 8.6 High |
| A flaw was found in libsoup. When handling an incoming WebSocket Pong frame, SoupWebsocketConnection emitted the ::pong signal with a GByteArray pointer even though the signal is declared to pass a GBytes. Applications connecting a handler that follows the documented GBytes API can trigger heap corruption or a crash upon receiving a crafted Pong. | ||||
| CVE-2026-102555 | 3 Gnome, Libsoup, Redhat | 4 Libsoup, Libsoup, Enterprise Linux and 1 more | 2026-11-02 | 8.2 High |
| A flaw was found in libsoup. The soup_uri_decode_data_uri() function incorrectly treated base64 data-URI payloads as NUL-terminated strings when calling g_base64_decode_inplace(). If the percent-decoded payload contained embedded NUL bytes, the decoded length could remain uninitialized and be used as the size of the returned GBytes. This can lead to an out-of-bounds read or application crash when processing a crafted data URI. | ||||
| CVE-2026-101173 | 1 Huawei | 1 Harmonyos | 2026-11-02 | 6.5 Medium |
| DoS vulnerability in the DSoftBus module. Impact: Successful exploitation of this vulnerability may affect availability. | ||||
| CVE-2026-101177 | 1 Huawei | 2 Emui, Harmonyos | 2026-11-02 | 3.7 Low |
| Permission control vulnerability in the Optimizer module. Impact: Successful exploitation of this vulnerability may affect service confidentiality. | ||||
| CVE-2026-101178 | 1 Huawei | 2 Emui, Harmonyos | 2026-11-02 | 6.6 Medium |
| Permission control vulnerability in the autofill service module. Impact: Successful exploitation of this vulnerability may affect service confidentiality. | ||||
| CVE-2026-101184 | 1 Huawei | 2 Emui, Harmonyos | 2026-11-02 | 5.5 Medium |
| Permission control vulnerability in the Bluetooth module. Impact: Successful exploitation of this vulnerability may affect availability. | ||||
| CVE-2026-111089 | 1 Apache | 1 Wicket | 2026-11-02 | N/A |
| Apache Wicket reads texts from the application's resource bundles — a localized label, a css class name — and writes some of them into the JavaScript and the markup it generates for a component. Those texts are placed inside single-quoted JavaScript string literals and inside quoted attribute values without being escaped for that context, so a text containing a quote ends the literal or the attribute, and what follows is parsed as script or as markup in the application's origin when the page loads. A resource bundle entry is authored for the application and does not say where the framework will write it. The same key is read by the framework into element text, where Wicket escapes it, and into the contexts below, where it did not. A text containing an apostrophe, which is ordinary in several languages, is enough to break the page; a text under the influence of another party is enough to run script. In org.apache.wicket:wicket-core, org.apache.wicket.markup.html.form.upload.MultiFileUploadField writes the org.apache.wicket.mfu.delete message into a JavaScript string literal, and org.apache.wicket.markup.html.form.Form writes the hidden-fields css class into the class attribute of the container it renders for its hidden fields; on 8.0.0 through 8.19.0 and 9.0.0 through 9.24.0 Form#appendDefaultButtonField writes the same css class into a second container. In org.apache.wicket:wicket-extensions, UploadProgressBar writes its UploadProgressBar.starting text into a JavaScript string literal, FilterForm writes the hidden-fields css class into the class attribute of its hidden input markup, and on 9.0.0 through 9.24.0 and 10.0.0 through 10.11.0 TrapFocusBehavior writes its current css class into a JavaScript string literal. The Content-Security-Policy that Apache Wicket 9.x and 10.x send by default does not prevent the JavaScript cases: the generated script is written into a script element carrying the per-response nonce, so the injected code is part of a script the policy admits. It does prevent an inline event handler injected through the attribute cases. This issue affects Apache Wicket: from 8.0.0 through 8.19.0, from 9.0.0 through 9.24.0, from 10.0.0 through 10.11.0. Users of Apache Wicket 7.x or older, which are no longer supported, should upgrade to a supported version. Users are recommended to upgrade to version 8.20.0, 9.25.0 or 10.12.0, which fix the issue. | ||||
| CVE-2025-11969 | 1 Wso2 | 11 Api Control Plane, Api Manager, Wso2 Api Control Plane and 8 more | 2026-11-02 | 9.4 Critical |
| The System REST APIs do not correctly enforce access control mechanisms, allowing users with lower privilege roles to execute administrative actions that should be restricted. This weakness permits unauthorized operations on the affected product. Successful exploitation could enable a malicious actor to perform unauthorized administrative operations, including executing administrative functions. APIs exposed through the WSO2 API Manager's API Gateway are not affected by this vulnerability. | ||||
| CVE-2026-101172 | 1 Huawei | 1 Harmonyos | 2026-11-02 | 6.2 Medium |
| Permission control vulnerability in the graphics module. Impact: Successful exploitation of this vulnerability may affect confidentiality. | ||||
| CVE-2026-101170 | 1 Huawei | 1 Harmonyos | 2026-11-02 | 4 Medium |
| DoS vulnerability in the file parsing module. Impact: Successful exploitation of this vulnerability may affect availability. | ||||
| CVE-2026-101171 | 1 Huawei | 1 Harmonyos | 2026-11-02 | 3.6 Low |
| Permission control vulnerability in the background task management module. Impact: Successful exploitation of this vulnerability may affect service integrity. | ||||
| CVE-2026-101175 | 1 Huawei | 1 Harmonyos | 2026-11-02 | 4.3 Medium |
| Null pointer dereference vulnerability in the ArkWeb module. Impact: Successful exploitation of this vulnerability may affect availability. | ||||
| CVE-2026-101179 | 1 Huawei | 1 Harmonyos | 2026-11-02 | 4.7 Medium |
| Buffer overflow vulnerability in the file preview module. Impact: Successful exploitation of this vulnerability may affect availability. | ||||
| CVE-2026-101180 | 1 Huawei | 1 Harmonyos | 2026-11-02 | 4.3 Medium |
| DoS vulnerability in the file parsing module. Impact: Successful exploitation of this vulnerability may affect availability. | ||||
| CVE-2026-101181 | 1 Huawei | 1 Harmonyos | 2026-11-02 | 5.5 Medium |
| Permission control vulnerability in the WLAN module. Impact: Successful exploitation of this vulnerability may affect service confidentiality. | ||||