# CVE-2022-46609: Supply chain in n/a

> Attackers can execute code, escalate privileges, and steal sensitive data via a backdoor in the request package dependency.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Dec 2022
- **Updated:** 22 Apr 2025
- **Also known as:** GHSA-j5rg-4wj9-7v6m

## What is CVE-2022-46609?

CVE-2022-46609 is a critical vulnerability in n/a, published on 14 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Python3-RESTfulAPI commit d9907f14e9e25dcdb54f5b22252b0e9452e3970e and e772e0beee284c50946e94c54a1d43071ca78b74 was discovered to contain a code execution backdoor via the request package. This vulnerability allows attackers to access sensitive user information and digital currency keys, as well as escalate privileges.

## Which versions are affected by CVE-2022-46609?

It affects 1 product.


Products: Python3-Restfulapi Project Python3-Restfulapi.

## How do I fix CVE-2022-46609?

No fix has been published for CVE-2022-46609 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-46609 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-46609 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-46609 and fix it if it is affected.

What it is: CVE-2022-46609 is a critical vulnerability in n/a, published on 14 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-46609 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

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-46609/ (Markdown: https://insights.sbomify.com/CVE-2022-46609/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-46609
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-46609
- OSV: https://osv.dev/vulnerability/CVE-2022-46609

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-46609/
Summaries are generated and may contain mistakes; the official description above is the record.