LiveActive security incident?Get immediate response
CVE Record

CVE-2026-35868: A Command Injection vulnerability exists in the bs_SetLimitCli_info function within the libshare.so library...

A Command Injection vulnerability exists in the bs_SetLimitCli_info function within the libshare.so library of LB-link Router AC2100_AZ3 V1.0.4. This flaw occurs due to insufficient validation and sanitization of user-supplied input before it is passed to a system-level command execution context. An attacker can exploit this vulnerability by injecting specially crafted shell metacharacters or payloads into the vulnerable parameter, resulting in the execution of arbitrary operating system commands.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

LB-link AC2100_AZ3 router firmware V1.0.4 reportedly accepts unsafe input that can reach an operating-system command context. A remote attacker may therefore take control of the router, steal information, alter configuration, or disrupt service. The supplied sources do not identify a vendor patch.

Executive priority

Treat confirmed V1.0.4 deployments as urgent, prioritising internet-reachable or externally accessible routers. Immediately reduce exposure while seeking authoritative vendor remediation. Because compromise could affect all three security objectives, unsupported devices without an effective fix should enter accelerated replacement planning.

Technical view

The flaw is described in bs_SetLimitCli_info within libshare.so. Insufficient input validation allows shell metacharacters in user-controlled data to enter a system-command execution context. CVSS 3.1 rates it 9.8: network-accessible, low complexity, no privileges or user interaction, with high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is limited to LB-link AC2100_AZ3 devices running V1.0.4, based on the narrative evidence. Risk is greatest where an untrusted network can reach the service path invoking the vulnerable function. The supplied material does not identify the affected endpoint, default configuration, or whether WAN access is enabled.

Exploitation context

The vulnerability is not listed as CISA KEV in the supplied bundle, and no cited source establishes active exploitation. Its CVSS vector indicates remote, unauthenticated, low-complexity exploitation without user interaction, making reachable affected devices attractive targets. Public technical disclosure exists, but prevalence and operational exploitation remain unconfirmed.

Researcher notes

Product and version are explicit in the CVE narrative, although the structured affected-product fields are recorded as n/a and provide no CPE. The exact parameter, calling endpoint, firmware variants, authentication path, patch status, and exploitation telemetry are absent. Validate exposure without assuming that every service using libshare.so reaches the vulnerable function.

Mitigation direction

  • Check LB-Link security guidance and firmware availability; the supplied sources do not identify a patch.
  • Restrict affected routers from untrusted networks and limit management access to trusted administrative systems.
  • Segment affected devices to reduce access to sensitive internal services if compromise occurs.
  • Replace affected hardware if no supported remediation becomes available and exposure cannot be adequately contained.

Validation and detection

  • Inventory LB-link AC2100_AZ3 devices and confirm whether firmware V1.0.4 is installed.
  • Determine which reachable service paths invoke bs_SetLimitCli_info; the supplied sources do not name the endpoint.
  • Review router and perimeter logs for unexpected input, configuration changes, command activity, or outbound connections.
  • After remediation, confirm the vulnerable firmware is absent and network restrictions remain effective.
Prepared
Confidence
medium
Sources
3

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 · low confidence lookup

CWE-20: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

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.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-35868 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

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.

1CVSS vectors
3Timeline events
1ADP providers
2Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total

CVSS vector scores

1 official score

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.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9CISA-ADP

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-35868Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. CVE publishedCVE Program

    The CVE record was published.

  3. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
cvssV3_1other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-20 · source CWE mapping

Improper Input Validation

Improper Input Validation represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.