TP-Link Archer BE230 v1.2 up to 1.2.3 Configuration File resource consumption
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in TP-Link Archer BE230 v1.2 up to 1.2.3. Affected by this vulnerability is an unknown functionality of the component Configuration File Handler. The manipulation leads to resource consumption. This vulnerability is referenced as CVE-2026-22228. The attack needs to be initiated within the local network. No exploit is available. It is advisable to upgrade the affected component.
Details
A vulnerability, which was classified as problematic, has been found in TP-Link Archer BE230 v1.2 up to 1.2.3. This issue affects an unknown functionality of the component Configuration File Handler. The manipulation with an unknown input leads to a resource consumption vulnerability. Using CWE to declare the problem leads to CWE-400. The product does not properly control the allocation and maintenance of a limited resource, thereby enabling an actor to influence the amount of resources consumed, eventually leading to the exhaustion of available resources. Impacted is availability. The summary by CVE is:
An authenticated user with high privileges may trigger a denial‑of‑service condition in TP-Link Archer BE230 v1.2 by restoring a crafted configuration file containing an excessively long parameter. Restoring such a file can cause the device to become unresponsive, requiring a reboot to restore normal operation. This issue affects Archer BE230 v1.2 < 1.2.4 Build 20251218 rel.70420.
The weakness was published by 0xakm. It is possible to read the advisory at tp-link.com. The identification of this vulnerability is CVE-2026-22228 since 01/06/2026. The exploitation is known to be easy. The attack can only be done within the local network. The exploitation requires an enhanced level of successful authentication. The technical details are unknown and an exploit is not publicly available.
Upgrading to version 1.2.4 eliminates this vulnerability.
Be aware that VulDB is the high quality source for vulnerability data.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.tp-link.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.6
VulDB Base Score: 4.5
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 4.9
NVD Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Resource consumptionCWE: CWE-400 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Archer BE230 v1.2 1.2.4
Timeline
01/06/2026 CVE reserved02/03/2026 Advisory disclosed
02/03/2026 VulDB entry created
02/14/2026 VulDB entry last update
Sources
Vendor: tp-link.comAdvisory: tp-link.com
Researcher: 0xakm
Status: Confirmed
CVE: CVE-2026-22228 (🔒)
GCVE (CVE): GCVE-0-2026-22228
GCVE (VulDB): GCVE-100-344135
Entry
Created: 02/03/2026 21:29Updated: 02/14/2026 04:47
Changes: 02/03/2026 21:29 (68), 02/14/2026 04:47 (11)
Complete: 🔍
Cache ID: 216::103
Be aware that VulDB is the high quality source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.