# CVE-2022-40486: Code injection in n/a

> Authenticated attackers can execute arbitrary code on TP-Link Archer AX10 routers by uploading a crafted backup file.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Sep 2022
- **Updated:** 21 May 2025
- **Also known as:** GHSA-6jfx-5cxr-8qxw

## What is CVE-2022-40486?

CVE-2022-40486 is a high-severity code injection vulnerability in n/a, published on 28 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

TP Link Archer AX10 V1 Firmware Version 1.3.1 Build 20220401 Rel. 57450(5553) was discovered to allow authenticated attackers to execute arbitrary code via a crafted backup file.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Tp-Link Archer Ax10 V1 Firmware.

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

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

## Is CVE-2022-40486 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-41450](https://insights.sbomify.com/CVE-2021-41450/): Other in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-40486 is a high-severity code injection vulnerability in n/a, published on 28 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2022-40486 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-40486/ (Markdown: https://insights.sbomify.com/CVE-2022-40486/index.md)
```

## Sources

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

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