Export limit exceeded: 421036 CVEs match your query. Please refine your search to export 10,000 CVEs or fewer.
Search
Search Results (473 CVEs found)
| CVE | Vendors | Products | Updated | CVSS v3.1 |
|---|---|---|---|---|
| CVE-2026-123854 | 1 Jetbrains | 1 Pycharm | 2026-11-07 | 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-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-123849 | 1 Jetbrains | 1 Intellij Idea | 2026-11-07 | 7 High |
| In JetBrains IntelliJ IDEA before 2026.3 code execution was possible in untrusted projects via the Terraform File Watchers | ||||
| CVE-2026-123838 | 1 Jetbrains | 1 Intellij Idea | 2026-11-07 | 7.8 High |
| In JetBrains IntelliJ IDEA before 2026.3 code execution was possible in Safe Mode via UI Designer form file | ||||
| 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-123308 | 1 Jetbrains | 1 Intellij Idea | 2026-11-07 | 6.3 Medium |
| In JetBrains IntelliJ IDEA before 2026.3 code execution via the document import was possible in untrusted projects | ||||
| CVE-2026-123304 | 1 Jetbrains | 1 Intellij Idea | 2026-11-07 | 7.8 High |
| In JetBrains IntelliJ IDEA before 2026.3 code execution in untrusted projects via a configured ShellCheck path | ||||
| CVE-2026-123302 | 1 Jetbrains | 1 Intellij Idea | 2026-11-07 | 7.8 High |
| In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4, 2026.1.5.1, 2025.3.6.2 code execution was possible in untrusted projects via script engine discovery | ||||
| CVE-2026-123293 | 1 Jetbrains | 1 Intellij Idea | 2026-11-07 | 7.8 High |
| In JetBrains IntelliJ IDEA before 2026.3, 2026.2.4 code execution was possible in untrusted projects via the Terraform tool path setting | ||||
| 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-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-95649 | 1 Iris | 1 Irispowerscan | 2026-11-06 | N/A |
| IRISPowerscan insufficiently restrict the use of untrusted scripts. An authenticated user with access to script functionality can import or modify scripts that are executed by the application, potentially resulting in arbitrary code execution in the security context of the Windows user running IRISPowerscan. | ||||
| CVE-2026-64894 | 1 Johnsoncontrols | 1 Easyio Neo Iomanager And Tools Installer | 2026-11-06 | N/A |
| Inclusion of functionality from untrusted control sphere vulnerability in Johnson Controls EasyIO Neo IOManager and Tools Installer allows Malicious Software Update. This issue affects EasyIO Neo IOManager and Tools Installer: 1.1.0.0. | ||||
| CVE-2026-110802 | 2 Altair-graphql, Altairgraphql | 4 Altair-express-middleware, Altair-fastify-plugin, Altair-koa-middleware and 1 more | 2026-11-06 | 6.1 Medium |
| Altair is a GraphQL client for all platforms. From 7.2.4 until 8.5.8, packages/altair-iframe-sandbox/src/main.ts reads plugin_sandbox_opts from the iframe-sandbox query string and passes attacker-controlled scriptUrls to injectScript() in packages/altair-core/src/utils/inject.ts, which creates script elements in the page. The intended parent iframe flow places the page in an iframe with sandbox allow-scripts and without allow-same-origin, but direct navigation to a crafted iframe-sandbox URL omits that isolation and executes the supplied script in the origin serving Altair. Exploitation requires a victim to open the crafted URL, and the resulting script can access script-readable storage and make same-origin requests according to the deployment's authentication and cookie controls. This issue is fixed in version 8.5.8. | ||||
| CVE-2026-123833 | 1 Jetbrains | 1 Intellij Idea | 2026-11-06 | 3.6 Low |
| In JetBrains IntelliJ IDEA before 2026.3 database connections could be established in untrusted projects | ||||
| CVE-2026-123843 | 1 Jetbrains | 1 Intellij Idea | 2026-11-06 | 3.3 Low |
| In JetBrains IntelliJ IDEA before 2026.3 untrusted projects could trigger changes to GPG agent configuration | ||||
| 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-118386 | 1 Gitea | 1 Gitea | 2026-11-06 | 6.5 Medium |
| Workflows triggered by a pull request review were read from the commit named in the review's `commit_id`, while the fork restrictions were decided by the reviewed pull request, and the commit was not checked to belong to that pull request. A user with read access to a repository could place a commit of their own in it, through a fork pull request or an AGit push, and submit a review naming that commit on a pull request whose head branch is in the same repository. On instances with a runner serving the repository, the attacker's workflow then ran without approval, received the Actions secrets of the repository and its owner, and got a `GITEA_TOKEN` with write access to the repository. Review-triggered workflows now run on the pull request head. | ||||