Export limit exceeded: 235583 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (1941 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-16511 | 1 Zephyrproject | 1 Zephyr | 2026-11-09 | 8.8 High |
| Two RTIO syscall verifiers, in subsys/rtio/rtio_syscalls.c (subsys/rtio/rtio_handlers.c before v4.3.0), did not validate user-supplied pointers before the kernel wrote through them. z_vrfy_rtio_sqe_cancel() performed no validation at all. It passed the caller's struct rtio_sqe pointer straight to z_impl_rtio_sqe_cancel(), which converts it with CONTAINER_OF to a struct rtio_iodev_sqe, ORs RTIO_SQE_CANCELED (BIT(3)) into its 16-bit flags field in supervisor mode, then loads its next pointer and repeats until that pointer is NULL. The syscall takes no RTIO context argument, so it needs no object grant: any user-mode thread on a CONFIG_USERSPACE build can set that bit in a 16-bit word at an address of its choosing in kernel memory, and the kernel continues the write along whatever pointer chain it finds at the corresponding offset. Setting chosen bits in kernel data structures, such as object permission or thread state fields, can be used to escalate privilege from user mode. z_vrfy_rtio_sqe_copy_in_get_handles() validated its RTIO context and the input SQE array, but only NULL-checked the handle out-parameter before writing a kernel SQE pointer through it, with no K_SYSCALL_MEMORY_WRITE check. A user thread that holds a granted RTIO context can therefore make the kernel store a pointer value at an arbitrary address. The fixes validate the handle out-parameter as writable, bound the cancel handle to real submission-pool storage, and require permission on the RTIO context that owns the matching pool. Without that last check a bounded handle still let any user thread cancel submissions belonging to other contexts, silently aborting their I/O. Systems built without CONFIG_USERSPACE or without CONFIG_RTIO are unaffected. | ||||
| CVE-2026-122192 | 1 Aws | 1 Firecracker | 2026-11-09 | 7.5 High |
| Improper handling of a failed memory remap in Firecracker versions 0.23.0 through 1.16.1 might allow a guest user with root privileges to read or modify Firecracker VMM process memory via balloon or virtio-mem discard requests on microVMs restored from a snapshot with the File memory backend, if the host fails to create the replacement mapping. To remediate this issue, users should upgrade to Firecracker 1.16.2 or 1.17.0 and later. | ||||
| CVE-2026-87050 | 1 Operator-foundry | 1 Operator-foundry | 2026-11-09 | 4.2 Medium |
| A flaw was found in operator-foundry. GitHub Actions and reusable workflows within the component are referenced using mutable tags (e.g., `@v0`, `@v4`) instead of fixed commit SHAs. This allows an attacker to potentially alter the code executed in the Continuous Integration (CI) pipeline through an upstream compromise or by re-pointing a tag, leading to unauthorized code execution or manipulation. | ||||
| CVE-2026-87055 | 1 Operator-sdk-builder | 1 Operator-sdk-builder | 2026-11-09 | 2.6 Low |
| A flaw was found in operator-sdk-builder. The software uses a flexible label, called a mutable tag, to identify its base container image instead of a unique, fixed identifier. This practice allows the underlying base image to change unexpectedly between builds. Such a change could introduce vulnerabilities or malicious code into the build process, posing a supply chain integrity risk. | ||||
| CVE-2026-87062 | 1 Konflux-operator-tasks | 1 Konflux-operator-tasks | 2026-11-09 | 4.2 Medium |
| A flaw was found in konflux-operator-tasks. GitHub Actions within this component are configured to use mutable tags or branches instead of specific, immutable commit SHAs. This vulnerability could allow a remote attacker to introduce malicious code into the build process if they compromise the referenced mutable tag or branch. Such a compromise could lead to unauthorized code execution or integrity issues within the affected system. | ||||
| CVE-2026-114134 | 1 Psf | 1 Black | 2026-11-09 | 8.8 High |
| Black is the uncompromising Python code formatter. Prior to 26.10.1, the Black GitHub Action with use_pyproject: true accepts tool.black.required-version from pyproject.toml without validating that it is a released Black version specifier. An attacker who can submit a pull request can change that field to a direct reference to attacker-controlled code, causing the workflow to install and execute the code in the victim repository's GitHub Actions context. This issue is fixed in version 26.10.1. | ||||
| CVE-2026-122135 | 1 Mistral | 1 Mistral-vibe | 2026-11-09 | 8.8 High |
| Mistral Vibe before 3.0.3 contains a remote code execution vulnerability that allows attackers to run commands by abusing repository-configured gpg.program during project context collection. A crafted repository setting gpg.program and log.showSignature with a signed commit makes git log execute the attacker's program at session start, before any trust prompt. | ||||
| CVE-2026-122134 | 1 Mistral | 1 Mistral-vibe | 2026-11-09 | 8.8 High |
| Mistral Vibe before 2.25.7 contains a remote code execution vulnerability that allows attackers to run commands by configuring malicious Git clean or process filter drivers in a repository. When a user opens a crafted repository, ProjectContextProvider._fetch_git_status runs git status at startup, invoking the filters and executing commands with user privileges before any trust prompt. | ||||
| CVE-2026-123854 | 1 Jetbrains | 1 Pycharm | 2026-11-08 | 5.5 Medium |
| In JetBrains PyCharm before 2026.3 code execution was possible in Safe Mode via a crafted Jupyter notebook widget module | ||||
| CVE-2026-123321 | 1 Jetbrains | 1 Webstorm | 2026-11-07 | 7.8 High |
| In JetBrains WebStorm before 2026.3, 2026.2.3 code execution via Grunt and Gulp task loading was possible in untrusted projects | ||||
| CVE-2023-5088 | 2 Qemu, Redhat | 4 Qemu, Advanced Virtualization, Enterprise Linux and 1 more | 2026-11-07 | 6.4 Medium |
| A bug in QEMU could cause a guest I/O operation otherwise addressed to an arbitrary disk offset to be targeted to offset 0 instead (potentially overwriting the VM's boot code). This could be used, for example, by L2 guests with a virtual disk (vdiskL2) stored on a virtual disk of an L1 (vdiskL1) hypervisor to read and/or write data to LBA 0 of vdiskL1, potentially gaining control of L1 at its next reboot. | ||||
| CVE-2026-123853 | 1 Jetbrains | 1 Intellij Idea | 2026-11-07 | 7.8 High |
| In JetBrains IntelliJ IDEA before 2026.3, 2026.2.2 code execution was possible in Safe Mode via project-controlled JVM options of the build process | ||||
| CVE-2026-123832 | 1 Jetbrains | 1 Clion | 2026-11-07 | 9.6 Critical |
| In JetBrains CLion before 2026.2 code execution was possible in Safe Mode via JSON compilation database | ||||
| CVE-2026-123831 | 1 Jetbrains | 1 Clion | 2026-11-07 | 9.6 Critical |
| In JetBrains CLion before 2026.2, 2026.1.4 code execution was possible in Safe Mode via Meson project settings | ||||
| CVE-2026-123325 | 1 Jetbrains | 1 Youtrack | 2026-11-07 | 7.1 High |
| In JetBrains YouTrack before 2025.3.170763, 2026.1.14150, 2026.2.19656 inclusion of untrusted remote code was possible via the plugin sandbox page | ||||
| CVE-2026-123276 | 1 Jetbrains | 1 Clion | 2026-11-07 | 7.8 High |
| In JetBrains CLion before 2026.3, 2026.2.4.1 code execution was possible in Safe Mode via a crafted GDB server debug profile | ||||
| CVE-2026-121398 | 1 Freerdp | 1 Freerdp | 2026-11-07 | 5.9 Medium |
| FreeRDP before 3.32.2 contains a cross-thread use-after-free vulnerability in the freerdp-proxy dyn-channel-dump module during session teardown. A malicious RDP target can send dynamic channel data while the front client disconnects, letting the client thread read freed ChannelData and crash the proxy process. | ||||
| CVE-2026-83493 | 2 Red Hat, Redhat | 2 Red Hat Openshift Ai (rhoai), Openshift Ai | 2026-11-06 | 9.1 Critical |
| A flaw was found in distributed-workloads. A remote attacker could exploit a vulnerability in the pull_request_target workflow by submitting a specially crafted pull request. This workflow processes untrusted code from the pull request author while operating with the base repository's sensitive secrets, such as the SNYK_TOKEN, and its default write token. Consequently, an attacker could exfiltrate these secrets, leading to unauthorized access to the Snyk integration and potential control over the repository. | ||||
| CVE-2026-123858 | 1 Jetbrains | 1 Phpstorm | 2026-11-06 | 4.4 Medium |
| In JetBrains PhpStorm before 2026.3 project files could be automatically uploaded to a deployment server from untrusted projects | ||||
| CVE-2026-93536 | 1 X.org | 3 X Server, Xorg-x11-server, Xwayland | 2026-11-06 | 5.3 Medium |
| A use after free caused by missing lifecycle management of gesture sprites in GestureBuildSprite() in X.Org X Server before 21.1.25 and XWayland before 24.1.14 could be used by authenticated X clients to crash the X server or potentially execute code. | ||||