OS Command Injection in LB-LINK router AC1900_AZ2 (CVE-2026-35867)
Summary
OS command injection in LB-LINK router AC1900_AZ2 (CVE-2026-35867). Risk of unauthorized operations or information disclosure. Exploitable via POST /goform/set_LimitClient_cfg.
Original description
The description as published by the source.
A Command Injection vulnerability exists in the bs_SetLimitCli_info function within the libshare.so library of the LB-LINK router AC1900_AZ2 V1.0.2 via shell metacharacters, if the device is deployed in a scenario where an actor is able to make a "POST /goform/set_LimitClient_cfg" call but does not already have administrative access to the device.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-35867 has been found in LB-LINK router AC1900_AZ2.
Attackers can target a specific entry point like POST /goform/set_LimitClient_cfg over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "LB-LINK router AC1900_AZ2 CVE-2026-35867" on the vendor's site.
CVE-2026-35867 (LB-LINK router AC1900_AZ2) — CWE-78 / CVSS v3 3.1
Attack vector: adjacent-network / no user interaction
Attack surface: POST /goform/set_LimitClient_cfg
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
OS command injection (CWE-78) exists in LB-LINK router AC1900_AZ2. Attackers reach the vulnerable code path via POST /goform/set_LimitClient_cfg.
Check the vendor advisory for the affected versions of LB-LINK router AC1900_AZ2. Attack surface: POST /goform/set_LimitClient_cfg.
Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /goform/set_LimitClient_cfg requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで LB-LINK router AC1900_AZ2 を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'POST /goform/set_LimitClient_cfg' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /goform/set_LimitClient_cfgへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /goform/set_LimitClient_cfg on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
References
- web github.com
- web nvd.nist.gov
- web github.com