# CVE-2025-32409: Path traversal in SuperNote A6 X2 Nomad

> Attackers can achieve remote code execution on Ratta SuperNote tablets by sending a malicious firmware image to a specific TCP port.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 7 Apr 2025
- **Updated:** 8 Apr 2025
- **Also known as:** GHSA-gc6q-4496-9jf2

## What is CVE-2025-32409?

CVE-2025-32409 is a high-severity path traversal vulnerability in Ratta SuperNote A6 X2 Nomad, published on 7 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ratta SuperNote A6 X2 Nomad before December 2024 allows remote code execution because an arbitrary firmware image (signed with debug keys) can be sent to TCP port 60002, and placed into the correct image-update location as a consequence of both directory traversal and unintended handling of concurrency.

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2025-32409?


## How do I fix CVE-2025-32409?

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

## Is CVE-2025-32409 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-32409 and fix it if it is affected.

What it is: CVE-2025-32409 is a high-severity path traversal vulnerability in Ratta SuperNote A6 X2 Nomad, published on 7 Apr 2025. 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-2025-32409 exists.

Affected product: Ratta SuperNote A6 X2 Nomad. 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-2025-32409/ (Markdown: https://insights.sbomify.com/CVE-2025-32409/index.md)
```

## Sources

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

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