Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Command injection prevention
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | This vulnerability presents CRITICAL real-world risk across multiple risk frameworks: (1) CVSS 9.8 with AV:N/AC:L/PR:N/UI:N indicates maximum severity—any networked system can exploit without authentication or user interaction; (2) CWE-77 command injection is among the most reliably exploitable vulnerability classes with near-100% technical feasibility; (3) Absence of documented KEV/CISA status or public POC does not reduce risk—Blink router firmware is frequently reverse-engineered and command injection flaws are trivially discoverable; (4) EPSS score (if available) would likely exceed 95% given the attack vector and exploit simplicity; (5) SSVC framework analysis: Exploitation is PROBABLE (command injection in web-facing functions), automatable (script-based), with TOTAL technical impact (unauthenticated RCE = complete device compromise); (6) Attack surface is broad: any Blink router with internet-facing management interface or accessible on local networks. Real-world priority is URGENT—patch immediately. This is not a theoretical high-CVSS issue; it is practically exploitable and likely already discovered by threat actors. |
| Exploit ScenarioDerived | An attacker on the same network as a Blink router (or via WAN if remote management is enabled) crafts an HTTP request to the router's web interface targeting the DNS configuration endpoint. The request includes malicious payloads in the dns1 parameter, such as: |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 14, 2026
Multiple Blink router models (8 distinct firmware versions across product lines) contain unauthenticated command injection vulnerabilities in the DNS configuration function (bs_SetDNSInfo), allowing remote attackers to execute arbitrary system commands with no authentication required. The CVSS 9.8 rating reflects the critical nature: network-exploitable, no privilege escalation needed, and complete compromise of confidentiality, integrity, and availability. While no KEV or public POC is documented in standard vulnerability databases as of this analysis, the combination of network accessibility and lack of authentication requirements makes this a high-priority threat for all affected Blink router owners.
RemediationAI
Immediate actions: (1) Contact Blink support to obtain patched firmware versions for each affected model—do not assume firmware versions exist yet if not publicly announced; (2) If patches are available, perform immediate firmware updates on all affected routers via the web interface (Administration > Firmware Upgrade) or automatic update mechanisms; (3) Interim mitigations if patches unavailable: (a) Restrict router management interface access to trusted IPs via firewall rules or ACLs; (b) Disable remote management features if enabled (disable UPnP, disable WAN-side access to web interface); (c) Ensure strong administrative credentials (change default passwords immediately); (d) Segment router from critical network assets using VLAN isolation; (e) Monitor firewall logs for suspicious DNS configuration requests (POST to /dns_config or similar endpoints); (4) For all users: check Blink's official support page and security bulletin for patched firmware versions and deployment timeline. Do not delay—this is critical.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The vulnerability resides in the bs_SetDNSInfo function, which processes DNS configuration parameters (dns1 and dns2) without proper input validation or sanitization. This is a classic CWE-77 (Improper Neutralization of Special Elements used in a Command) case where user-supplied input is concatenated directly into shell commands executed via system calls. The affected routers span multiple product lines (BL-WR9000, BL-AC2100, BL-X10, BL-LTE300, BL-F1200, BL-X26 variants) and hardware revisions, suggesting a common vulnerable codebase shared across Blink's router firmware. CPE identifiers would typically be structured as cpe:2.3:o:blink:*:firmware_version or cpe:2.3:h:blink:product_model for these embedded systems. The dns1/dns2 parameters are network-accessible via the router's web interface or API endpoints, requiring no authentication per the CVSS vector (PR:N), making exploitation trivial for any network-adjacent attacker.
Know when Bl Ac2100 Az3 Firmware gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
Blink routers BL-WR9000 V2.4.9 , BL-AC2100_AZ3 V1.0.4, BL-X10_AC8 v1.0.5 , BL-LTE300 v1.2.3, BL-F1200_AT1 v1.0.0, BL-X26_AC8 v1.2.8, BLAC450M_AE4 v4.0.0 and BL-X26_DA3 v1.2.7 were discovered to contain multiple command injection vulnerabilities via the dns1 and dns2 parameters in the bs_SetDNSInfo function.
Executive ViewAI
A critical remote code execution vulnerability affects multiple Blink router models, allowing unauthenticated attackers to execute arbitrary commands through DNS configuration parameters. Organizations using these routers face immediate risk of network compromise, data theft, and unauthorized access to connected systems.
Implement network Access Control Lists (ACLs) to restrict access to router management interfaces; deploy WAF rules to filter malicious DNS parameter inputs containing command injection patterns (backticks, semicolons, pipes, command substitution syntax); disable DNS configuration modification through web/API interfaces; segment router management traffic on isolated VLANs; implement DNS query logging and monitoring for anomalous activity; consider temporary replacement with patched router models or alternative vendors until vendor patch is released.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
More in Bl Ac2100 Az3 Firmware
View allCritical remote command injection vulnerability affecting multiple Blink router models through the bs_SetSSIDHide functi
A command injection vulnerability (CVSS 9.8). Risk factors: public PoC available.
A critical unauthenticated remote command injection vulnerability exists in multiple Blink router models through the 'ma
A command injection vulnerability (CVSS 9.8). Risk factors: public PoC available.
EUVD-2025-18262
NVD
CVE.org
EPSS
GitHub
Exploit-DB