CVE-2026-86149: Tenda CP3 NetCheckPing.cpp os command injection
A weakness has been identified in Tenda CP3 27.5.57.101. This issue affects some unknown processing of the file Net/NetCheckPing.cpp. This manipulation of the argument interface_name/host causes os command injection. The attack can be initiated remotely.
Security readout for executives and security teams
Plain-English summary
A remote attacker with high privileges may be able to make a Tenda CP3 running firmware 27.5.57.101 execute operating-system commands. Successful abuse could compromise the device and potentially affect connected systems. The available sources do not establish active exploitation or identify a vendor patch.
Executive priority
Treat confirmed affected devices as urgent remediation candidates, especially if internet-exposed or connected to sensitive networks. Prioritize isolation, administrative-access review, and vendor guidance. Critical technical impact justifies rapid action, although required high privileges and absent exploitation evidence reduce immediate likelihood.
Technical view
CVE-2026-86149 is an OS command-injection weakness in unknown processing within Net/NetCheckPing.cpp. Manipulation of interface_name or host can reach an operating-system command context. It is remotely reachable, requires high privileges, and needs no user interaction. The supplied CVSS 4.0 score is 9.4, with high confidentiality, integrity, and availability impacts.
Likely exposure
Confirmed scope is limited to Tenda CP3 firmware 27.5.57.101. Risk is greatest where affected devices and the vulnerable privileged functionality are reachable from untrusted networks or compromised administrative accounts. The bundle does not identify other affected versions, deployment defaults, or the exact exposed interface.
Exploitation context
The attack can be initiated remotely but requires high privileges. The bundle reports no CISA KEV listing and provides no evidence of active exploitation. Its CVSS exploit-maturity value is unspecified, so exploit availability and real-world activity should be treated as unknown.
Researcher notes
The public bundle leaves the request path, authentication boundary, vulnerable code flow, product defaults, patch status, and exploit availability unresolved. Assessment should preserve the distinction between remote reachability and high required privileges. Do not infer broader version exposure from the wildcard firmware CPE without additional vendor or CVE evidence.
Mitigation direction
Identify and prioritize Tenda CP3 devices running firmware 27.5.57.101.
Restrict device management and privileged functionality to trusted networks and authorized administrators.
Remove direct internet exposure and segment affected devices from sensitive systems.
Check Tenda guidance for corrected firmware or official mitigation; no patch is named in the bundle.
Monitor affected devices for unexpected command execution, configuration changes, or outbound connections.
Validation and detection
Verify each CP3 device's exact firmware version against 27.5.57.101.
Confirm affected devices are not directly reachable from untrusted networks.
Review administrative access controls, account activity, and privileged interface exposure.
Inspect device and network logs for anomalous processes, configuration changes, or communications.
After remediation, confirm firmware versions and repeat exposure and access-control checks.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-77: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
4CVSS vectors
6Timeline events
1ADP providers
6Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
4 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-77 · source CWE mapping
Improper Neutralization of Special Elements used in a Command ('Command Injection')
Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.