CVE-2026-22228VulnerabilityPublished 3 Feb 2026Updated 4 Feb 2026

CVE-2026-22228: TP-Link Systems Archer BE230 v1.2 · Uncontrolled Resource Consumption

Affects TP-Link Systems Archer BE230 v1.2Source CVE Database V5

Not known to be exploited · CVSS 6.8 Medium : upgrade to 1.2.4 Build 20251218 rel.70420 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.8Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 1.2.4 Build 20251218 rel.70420

CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:L

Attack Vector: Adjacent
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: None
Vulnerable system integrity: None
Vulnerable system availability: High
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: Low

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Adjacent: The vulnerable system is bound to a protocol stack, but the attack is limited at the protocol level to a logically adjacent topology. This can mean an attack must be launched from the same shared proximity (e.g., Bluetooth, NFC, or IEEE 802.11) or logical network (e.g., local IP subnet), or from within a secure or otherwise limited administrative domain (e.g., MPLS, secure VPN within an administrative network zone).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: High: There is a total loss of availability, resulting in the attacker being able to fully deny access to resources in the Vulnerable System; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the Vulnerable System (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Subsequent System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Subsequent System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 3 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade TP-Link Systems Archer BE230 v1.2 to 1.2.4 Build 20251218 rel.70420.

Affected software

Product	Affected	Fixed in
TP-Link Systems Inc.Archer BE230 v1.2	Affected =0	Fixed in 1.2.4 Build 20251218 rel.70420

AI-suggested

European organizations should immediately verify the firmware version of all TP-Link Archer BE230 v1.2 devices and upgrade to version 1.2.4 Build 20251218 rel.70420 or later once available. If you cannot patch yet, restrict administrative access to trusted personnel only and enforce strong authentication mechanisms to prevent unauthorized high-privilege access. Implement network segmentation to isolate management interfaces from general user networks and monitor for unusual configuration restore activities. Regularly audit configuration backups and validate their integrity before restoration to prevent malicious or malformed files from being used. Employ logging and alerting on configuration changes and administrative actions to detect potential exploitation attempts early. Additionally, consider deploying intrusion detection systems capable of identifying anomalous traffic patterns or resource exhaustion symptoms on these devices. Establish incident response procedures to quickly reboot affected devices and restore service if exploitation occurs.

Description

CVE-2026-22228 is a medium-severity vulnerability in TP-Link Archer BE230 v1.2 routers that allows an authenticated user with high privileges to cause a denial-of-service (DoS) by restoring a crafted configuration file containing an excessively long parameter. This triggers uncontrolled resource consumption, rendering the device unresponsive and requiring a reboot. The vulnerability affects versions prior to 1.2.4 Build 20251218 rel.70420 and does not require user interaction but does require privileged authentication. There are no known exploits in the wild yet. The issue impacts device availability but not confidentiality or integrity directly. European organizations using this router model should prioritize patching or upgrading to mitigate potential service disruptions.

Impact

For European organizations, the primary impact is on network availability and operational continuity. A successful exploitation results in a denial-of-service condition, causing network outages or degraded performance until the device is rebooted. This can disrupt business operations, especially for organizations relying on these routers for critical connectivity or remote access. The requirement for high-privilege authentication limits the attack surface but insider threats or compromised administrative credentials could enable exploitation. The vulnerability does not compromise data confidentiality or integrity directly but may be used as part of a multi-stage attack to disrupt services or facilitate lateral movement. Organizations in sectors such as telecommunications, government, and critical infrastructure using TP-Link Archer BE230 devices are particularly vulnerable to operational disruptions. The lack of known exploits reduces immediate risk but does not eliminate the threat, especially as threat actors may develop exploits over time.

CWE-400Uncontrolled Resource Consumption (opens in a new tab)
Class weaknessLikelihood of exploit: High
The product does not properly control the allocation and maintenance of a limited resource.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Design throttling mechanisms into the system architecture. The best protection is to limit the amount of resources that an unauthorized user can cause to be expended. A strong authentication and access control model will help prevent such attacks from occurring in the first place.
Architecture and Design
Mitigation of resource exhaustion attacks requires that the target system either: recognizes the attack and denies that user further access for a given amount of time, or; uniformly throttles all requests in order to make it more difficult to consume resources more quickly than they can again be freed.
Architecture and Design
Ensure that protocols have specific limits of scale placed on them.
OWASP Cheat Sheets
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V12.1.1 (opens in a new tab)
Attack patterns
XML Ping of the Death (opens in a new tab)
Regular Expression Exponential Blowup (opens in a new tab)
Sustained Client Engagement (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 11 Feb 2026, 11:49 UTC

WeaknessesCWE-400

Technical details

References

Community reviews

Related threats