# CVE-2021-41449: Path traversal in n/a

> Remote unauthenticated attackers can access sensitive restricted files on Netgear RAX35, RAX38, and RAX40 routers via path traversal.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Dec 2021
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-h4m4-4f78-3cq7

## What is CVE-2021-41449?

CVE-2021-41449 is a high-severity path traversal vulnerability in n/a, published on 9 Dec 2021. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A path traversal attack in web interfaces of Netgear RAX35, RAX38, and RAX40 routers before v1.0.4.102, allows a remote unauthenticated attacker to gain access to sensitive restricted information, such as forbidden files of the web application, via sending a specially crafted HTTP packet.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 3 products.


Products: Netgear Rax35 Firmware, Netgear Rax38 Firmware, Netgear Rax40 Firmware.

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

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

## Is CVE-2021-41449 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2021-45493](https://insights.sbomify.com/CVE-2021-45493/): Information disclosure in n/a (high 7.6)
- [CVE-2021-38526](https://insights.sbomify.com/CVE-2021-38526/): Memory corruption in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2021-41449 is a high-severity path traversal vulnerability in n/a, published on 9 Dec 2021. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-41449 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-41449/ (Markdown: https://insights.sbomify.com/CVE-2021-41449/index.md)
```

## Sources

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

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