CVE-2026-22221
OS command injection in TP-Link Archer BE230 enables adjacent authenticated attacker to execute code.
Is CVE-2026-22221 being exploited?
Not confirmed. CVE-2026-22221 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.4% probability of exploitation in the next 30 days.
How severe is CVE-2026-22221?
CVE-2026-22221 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-22221?
Yes. A fix has been recorded for CVE-2026-22221. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-22221 affect?
CVE-2026-22221 affects TP-Link Archer BE230 v1.2 < 1.2.4 Build 20251218 rel.70420. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-22221?
Update to 1.2.4+; restrict VPN exposure; monitor for anomalies.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Adjacent authenticated attacker can run arbitrary OS commands and gain full admin control, compromising config, network security, and availability.
Immediate action required
- affected< 1.2.4 Build 20251218 rel.70420
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.