# CVE-2025-46626: Weak cryptography in n/a

> Attackers can decrypt, replay, or forge traffic to the management service due to static AES keys and IVs, compromising router security.

- **Severity:** High 7.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 May 2025
- **Updated:** 2 May 2025
- **Also known as:** GHSA-gc4p-7qxx-hhrw

## What is CVE-2025-46626?

CVE-2025-46626 is a high-severity vulnerability in n/a, published on 1 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Reuse of a static AES key and initialization vector for encrypted traffic to the 'ate' management service of the Tenda RX2 Pro 16.03.30.14 allows an attacker to decrypt, replay, and/or forge traffic to the service.

Weakness: CWE-326 (Inadequate Encryption Strength)

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

It affects 1 product.


Products: Tenda Rx2 Pro Firmware.

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

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

## Is CVE-2025-46626 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-46625](https://insights.sbomify.com/CVE-2025-46625/): Command injection in n/a (high 8.8)
- [CVE-2025-46627](https://insights.sbomify.com/CVE-2025-46627/): Hardcoded credentials in n/a (high 8.2)
- [CVE-2025-46633](https://insights.sbomify.com/CVE-2025-46633/): Information disclosure in n/a (high 8.2)
- [CVE-2025-46634](https://insights.sbomify.com/CVE-2025-46634/): Information disclosure in n/a (high 8.2)
- [CVE-2025-46628](https://insights.sbomify.com/CVE-2025-46628/): Command injection in n/a (high 7.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-46626 is a high-severity vulnerability in n/a, published on 1 May 2025. 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-2025-46626 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-2025-46626/ (Markdown: https://insights.sbomify.com/CVE-2025-46626/index.md)
```

## Sources

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

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