# CVE-2026-102812: Hardcoded AES-128 Key and Fixed IV in Configuration Backup Encryption in TP-Link RE305 and Archer C7


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-xgv8-3vj8-53q7

## What is CVE-2026-102812?

CVE-2026-102812 is a medium-severity vulnerability in TP-Link Systems Inc. Archer C7 v5, published on 27 Oct 2026. 

### Official description

A hard-coded
cryptographic key vulnerability exists in the user-configuration backup
mechanism of TP-Link RE305 V3 and Archer C7 V5. A fixed AES-128 key and
initialization vector are embedded in the firmware configuration-management
component. An attacker who obtains an affected configuration backup file may
extract the cryptographic material from the firmware and use it to decrypt the
backup. 

Successful
exploitation may disclose sensitive configuration information contained in a
backup file, including administrator passwords and Wi-Fi credentials.

Weakness: CWE-321 (Use of Hard-coded Cryptographic Key)

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


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

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

## Is CVE-2026-102812 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-102812 is a medium-severity vulnerability in TP-Link Systems Inc. Archer C7 v5, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-102812 in the wild and no public exploit code.

Affected product: TP-Link Systems Inc. Archer C7 v5. 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-102812/ (Markdown: https://insights.sbomify.com/CVE-2026-102812/index.md)
```

## Sources

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

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