# CVE-2021-41451: Misconfiguration in n/a

> A remote attacker can exploit HTTP misconfiguration to poison caches, potentially altering content served to users of the TP-Link AX10v1 router.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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:** 17 Dec 2021
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-x67c-x34f-8f4w

## What is CVE-2021-41451?

CVE-2021-41451 is a high-severity vulnerability in n/a, published on 17 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A misconfiguration in HTTP/1.0 and HTTP/1.1 of the web interface in TP-Link AX10v1 before V1_211117 allows a remote unauthenticated attacker to send a specially crafted HTTP request and receive a misconfigured HTTP/0.9 response, potentially leading into a cache poisoning attack.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

## Which versions are affected by CVE-2021-41451?

It affects 1 product.


Products: Tp-Link Archer Ax10 Firmware.

## How do I fix CVE-2021-41451?

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

## Is CVE-2021-41451 being exploited?

There is no known exploitation of CVE-2021-41451 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-34832](https://insights.sbomify.com/CVE-2023-34832/): Memory corruption in n/a (critical 9.8)
- [CVE-2021-40288](https://insights.sbomify.com/CVE-2021-40288/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2021-41451 and fix it if it is affected.

What it is: CVE-2021-41451 is a high-severity vulnerability in n/a, published on 17 Dec 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-41451 in the wild and no public exploit code.

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

## Sources

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

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