# CVE-2022-21699: Execution with Unnecessary Privileges in ipython > An attacker can execute arbitrary code as another user on the same machine due to improper management of cross-user temporary files in IPython. - **Severity:** High 8.2 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** A user has to click or open something - **Fix available:** Yes - **Published:** 19 Jan 2022 - **Updated:** 22 Apr 2025 - **Also known as:** AZL-109526, DEBIAN-CVE-2022-21699, DLA-2896-1, DSA-5065-1, GHSA-pq7m-3gw7-gq5x, MGASA-2023-0058, PYSEC-2022-12, UBUNTU-CVE-2022-21699, openSUSE-SU-2022:10043-1, openSUSE-SU-2024:11763-1, openSUSE-SU-2024:11995-1, openSUSE-SU-2025:14718-1 ## What is CVE-2022-21699? CVE-2022-21699 is a high-severity vulnerability in Debian Debian Linux, published on 19 Jan 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. ### Official description IPython (Interactive Python) is a command shell for interactive computing in multiple programming languages, originally developed for the Python programming language. Affected versions are subject to an arbitrary code execution vulnerability achieved by not properly managing cross user temporary files. This vulnerability allows one user to run code as another on the same machine. All users are advised to upgrade. Weakness: CWE-269 (Improper Privilege Management), CWE-279 (Incorrect Execution-Assigned Permissions), CWE-250 (Execution with Unnecessary Privileges) ## Which versions are affected by CVE-2022-21699? 9 open source packages ship an affected version, including ipython. It affects 3 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `ipython` | PyPI | All versions | 6.0.0rc1, 7.16.3, 7.31.1, 8.0.1 | | `ipython` | PyPI | All versions | 5.11 | | `ipython` | PyPI | All versions | 5.11 | | `ipython` | PyPI | From 6.0.0 | 7.16.3 | | `ipython` | PyPI | From 6.0.0 | 7.16.3 | | `ipython` | PyPI | From 7.17.0 | 7.31.1 | | `ipython` | PyPI | From 7.17.0 | 7.31.1 | | `ipython` | PyPI | From 8.0.0 | 8.0.1 | | `ipython` | PyPI | From 8.0.0 | 8.0.1 | | `python-ipython` | SUSE:Package Hub 15 SP3 | All versions | 7.13.0-bp153.2.6.1 | | `python-ipython-test` | SUSE:Package Hub 15 SP3 | All versions | 7.13.0-bp153.2.6.6 | | `python-ipython` | openSUSE:Leap 15.3 | All versions | 7.13.0-bp153.2.6.1 | | `python-ipython-test` | openSUSE:Leap 15.3 | All versions | 7.13.0-bp153.2.6.6 | | `python-ipython` | openSUSE:Tumbleweed | All versions | 8.31.0-1.1 | Products: Debian Debian Linux, Fedoraproject Fedora, Ipython Ipython. ## How do I fix CVE-2022-21699? Upgrade ipython to a fixed version for your release line: 6.0.0rc1, 7.16.3, 7.31.1 or 8.0.1. ## Is CVE-2022-21699 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-21699 exists. ## Other vulnerabilities in Debian Debian Linux - [CVE-2015-3306](https://insights.sbomify.com/CVE-2015-3306/): ProFTPD Improper Access Control (critical 10.0, exploited in the wild) - [CVE-2025-49113](https://insights.sbomify.com/CVE-2025-49113/): RoundCube Webmail Deserialization of Untrusted Data (critical 9.9, exploited in the wild) - [CVE-2026-24061](https://insights.sbomify.com/CVE-2026-24061/): GNU InetUtils Argument Injection (critical 9.8, exploited in the wild) - [CVE-2025-39682](https://insights.sbomify.com/CVE-2025-39682/): Linux Kernel Improper Check for Unusual or Exceptional Conditions (critical 9.8, exploited in the wild) - [CVE-2024-9680](https://insights.sbomify.com/CVE-2024-9680/): Mozilla Firefox Use-After-Free (critical 9.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2022-21699 and fix it if it is affected. What it is: CVE-2022-21699 is a high-severity vulnerability in Debian Debian Linux, published on 19 Jan 2022. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-21699 exists. Affected packages and fixed versions: - ipython (PyPI): affected all versions; fixed in 6.0.0rc1, 7.16.3, 7.31.1, 8.0.1 - ipython (PyPI): affected all versions; fixed in 5.11 - ipython (PyPI): affected all versions; fixed in 5.11 - ipython (PyPI): affected from 6.0.0; fixed in 7.16.3 - ipython (PyPI): affected from 6.0.0; fixed in 7.16.3 - ipython (PyPI): affected from 7.17.0; fixed in 7.31.1 - ipython (PyPI): affected from 7.17.0; fixed in 7.31.1 - ipython (PyPI): affected from 8.0.0; fixed in 8.0.1 - ipython (PyPI): affected from 8.0.0; fixed in 8.0.1 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2022-21699/ (Markdown: https://insights.sbomify.com/CVE-2022-21699/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2022-21699 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-21699 - OSV: https://osv.dev/vulnerability/CVE-2022-21699 --- From sbomify Insights: https://insights.sbomify.com/CVE-2022-21699/ Summaries are generated and may contain mistakes; the official description above is the record.