# CVE-2026-4619: Path traversal in Aterm WX3600HP

> An attacker can overwrite arbitrary files on NEC Aterm WX3600HP routers via network access due to a path traversal vulnerability.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2026
- **Updated:** 10 Apr 2026
- **Also known as:** GHSA-73jj-x3w6-c78g

## What is CVE-2026-4619?

CVE-2026-4619 is a medium-severity path traversal vulnerability in NEC Platforms, Ltd. Aterm WX3600HP, published on 27 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Path Traversal vulnerability in NEC Platforms, Ltd. Aterm Series allows a attacker to wtite over any file via network.

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

## Which versions are affected by CVE-2026-4619?

It affects 1 product.


Products: Nec Aterm Wx3600hp Firmware.

## How do I fix CVE-2026-4619?

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

## Is CVE-2026-4619 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4619 and fix it if it is affected.

What it is: CVE-2026-4619 is a medium-severity path traversal vulnerability in NEC Platforms, Ltd. Aterm WX3600HP, published on 27 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-4619 in the wild and no public exploit code.

Affected product: NEC Platforms, Ltd. Aterm WX3600HP. 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-2026-4619/ (Markdown: https://insights.sbomify.com/CVE-2026-4619/index.md)
```

## Sources

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

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