Export limit exceeded: 427961 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 427961 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Export limit exceeded: 427961 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (427961 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-127100 | 3 Red Hat, Redhat, Sssd | 6 Enterprise Linux, Enterprise Linux, Openshift and 3 more | 2026-11-13 | 5.5 Medium |
| A flaw was found in SSSD's PAM responder on builds with the JSON PAM extension enabled. A local attacker can submit a crafted authentication request containing a non-string OAuth2 code value. Missing JSON type validation leads to a NULL pointer dereference, terminating the PAM responder and disrupting SSSD-backed authentication. | ||||
| CVE-2026-2950 | 1 Lodash | 5 Lodash, Lodash-amd, Lodash-es and 2 more | 2026-11-13 | 6.5 Medium |
| The _.unset and _.omit functions in Lodash are vulnerable to prototype pollution. The fix for CVE-2025-13465 only guards against string key members, so an attacker can bypass the check by passing array-wrapped path segments. This allows deletion of properties from built-in prototypes such as Object.prototype, Number.prototype, and String.prototype. The issue permits deletion of prototype properties but does not allow overwriting their original behavior. The issue is patched from 4.18.0 to 4.18.1 depending on the package: lodash, lodash-es, and lodash-amd in 4.18.1, and the standalone lodash.unset and lodash.omit packages in 4.18.0. | ||||
| CVE-2026-43626 | 2026-11-13 | N/A | ||
| This CVE ID has been rejected or withdrawn by its CVE Numbering Authority, replacedby CVE-2026-70640. | ||||
| CVE-2026-126895 | 1 Google | 1 Chrome | 2026-11-13 | 8.8 High |
| Use after free in CSS in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Critical) | ||||
| CVE-2026-126859 | 1 Google | 1 Chrome | 2026-11-13 | 9.6 Critical |
| Link following in FileSystem in Google Chrome prior to 157.0.8103.78 allowed a remote attacker leveraging social engineering to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-126887 | 1 Google | 1 Chrome | 2026-11-13 | 8.8 High |
| Use after free in Animation in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-126878 | 1 Google | 1 Chrome | 2026-11-13 | 4.3 Medium |
| Information leak in Core in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-126853 | 1 Google | 1 Chrome | 2026-11-13 | 3.1 Low |
| Uninitialized resource in Skia in Google Chrome prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to read memory outside the sandbox via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-126862 | 1 Google | 2 Android, Chrome | 2026-11-13 | 7.7 High |
| Improper input validation in Core in Google Chrome on on Android prior to 157.0.8103.78 allowed a local attacker to bypass web origin policy via a co-installed app. (Chromium security severity: High) | ||||
| CVE-2026-126907 | 2 Google, Microsoft | 2 Chrome, Windows | 2026-11-13 | 3.1 Low |
| Uninitialized resource in Media in Google Chrome on on Windows prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to potentially read memory outside the sandbox via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-126891 | 1 Google | 1 Chrome | 2026-11-13 | 4.3 Medium |
| Use after free in V8 in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to read memory inside the sandbox via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-126866 | 1 Google | 1 Chrome | 2026-11-13 | 8.8 High |
| Incorrect authorization in Extensions in Google Chrome prior to 157.0.8103.78 allowed a remote attacker leveraging social engineering to execute arbitrary code inside the sandbox via a crafted Chrome extension. (Chromium security severity: High) | ||||
| CVE-2026-126882 | 1 Google | 1 Chrome | 2026-11-13 | 3.1 Low |
| Information leak in Skia in Google Chrome prior to 157.0.8103.78 allowed a remote attacker who had compromised the renderer process to leak cross-origin data via a crafted HTML page. (Chromium security severity: High) | ||||
| CVE-2026-123282 | 1 Jetbrains | 1 Datalore | 2026-11-13 | 7.4 High |
| In JetBrains Datalore before 2026.4 missing expiration validation of account tokens allowed a new authenticated session | ||||
| CVE-2026-123281 | 1 Jetbrains | 1 Datalore | 2026-11-13 | 7.5 High |
| In JetBrains Datalore before 2026.4 notebook code could execute commands in the sidecar container via the mount broker | ||||
| CVE-2026-123280 | 1 Jetbrains | 1 Datalore | 2026-11-13 | 8.1 High |
| In JetBrains Datalore before 2026.2.4 unauthenticated users could execute code via published interactive reports | ||||
| CVE-2026-123279 | 1 Jetbrains | 1 Datalore | 2026-11-13 | 9 Critical |
| In JetBrains Datalore before 2026.4 code execution was possible in a notebook's computation by view-only collaborators | ||||
| CVE-2026-123284 | 1 Jetbrains | 1 Datalore | 2026-11-13 | 6.5 Medium |
| In JetBrains Datalore before 2026.4 improper authorisation on workspace moves allowed view-only collaborators to modify shared content | ||||
| CVE-2026-17140 | 1 Ibm | 1 Api Connect | 2026-11-13 | 3.3 Low |
| IBM API Connect 10.0.8.0 through 10.0.8.12 and 12.1.0.0 through 12.1.1.2 could allow a remote authenticated attacker to execute arbitrary code due to improper control of generation of code. Input supplied by a user can influence code generated by the product, which could lead to code execution. | ||||
| CVE-2026-126933 | 1 Diced | 1 Zipline | 2026-11-13 | 4.3 Medium |
| Zipline 4.0.0 before 4.8.0 contains an upload filter bypass vulnerability that allows users with upload access to store blocked file types due to extension format mismatch. The upload and partial handlers compare dotted, case-sensitive extensions against undotted disabledExtensions entries, letting authenticated or permitted unauthenticated folder uploaders bypass administrator restrictions. | ||||