# CVE-2025-14631: Null Pointer Dereference Vulnerability in Malformed 802.11 Frame of TP-Link Archer BE400


- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 7 Jan 2026
- **Updated:** 7 Jan 2026
- **Also known as:** GHSA-9688-9jmc-xf77

## What is CVE-2025-14631?

CVE-2025-14631 is a high-severity vulnerability in TP-Link Systems Inc. Archer BE400, published on 7 Jan 2026. 

### Official description

A NULL Pointer Dereference vulnerability in TP-Link Archer BE400 V1(802.11 modules) allows 

an adjacent attacker to cause a denial-of-service (DoS) by triggering a device reboot.

This issue affects Archer BE400: xi 1.1.0 Build 20250710 rel.14914.

Weakness: CWE-476 (NULL Pointer Dereference)

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

It affects 1 product.


Products: Tp-Link Archer Be400 Firmware.

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

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

## Is CVE-2025-14631 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14631 is a high-severity vulnerability in TP-Link Systems Inc. Archer BE400, published on 7 Jan 2026. 
Exploitation: There is no known exploitation of CVE-2025-14631 in the wild and no public exploit code.

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

## Sources

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

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