CVE-2026-53611: Looking Glass: Remote Code Execution via Unanchored Regular Expression in BGPASPath Input Validation
Looking Glass is a modern, stateless network-diagnostic platform — a single self-contained Go binary that fronts a fleet of routers over SSH and exposes ping / traceroute / BGP lookups through a gRPC (ConnectRPC) API, an embedded SvelteKit web UI, and a lg-cli client. Prior to version 1.3.5, there is an OS Command Injection vulnerability resulting from an unanchored regular expression in the input validation layer. This issue has been patched in version 1.3.5.
Security readout for executives and security teams
Plain-English summary
A flaw in Looking Glass before version 1.3.5 can let an unauthenticated remote attacker turn specially crafted BGP AS-path input into operating-system commands. Successful exploitation could expose data, alter the service or connected environment, and interrupt availability. The vendor patched the issue in version 1.3.5.
Executive priority
Treat this as an emergency patching item for reachable deployments. Identify owners immediately, upgrade exposed systems first, and require confirmation of version and network exposure. Investigate suspicious activity if telemetry is available, while recognizing the provided sources contain no evidence of active exploitation.
Technical view
CVE-2026-53611 is a CWE-78 OS command-injection vulnerability caused by an unanchored regular expression in BGPASPath input validation. The CVSS 3.1 assessment is 9.8: network-accessible, low complexity, no privileges or user interaction required, with high confidentiality, integrity, and availability impact. Versions earlier than 1.3.5 are affected.
Likely exposure
Exposure exists where AS203038 Looking Glass versions below 1.3.5 accept attacker-reachable BGP lookup requests. Internet-facing or otherwise untrusted-network-accessible deployments warrant the fastest review. The supplied sources do not establish how many vulnerable installations are publicly reachable.
Exploitation context
The supplied record does not identify known active exploitation, and the CVE is not marked as CISA KEV. However, its unauthenticated network attack path, low stated complexity, and potential command execution make vulnerable reachable instances attractive targets. Absence from KEV does not prove exploitation has not occurred.
Researcher notes
The root cause is described as unanchored-regex validation of BGPASPath input leading to CWE-78 command injection. The public bundle establishes affected versions and the fixed release, but provides no deployment prevalence, exploitation observations, or compromise indicators. Validation should therefore focus on version, reachability, and locally available telemetry without attempting exploitation.
Mitigation direction
Upgrade AS203038 Looking Glass to version 1.3.5 or later.
Prioritize externally reachable and untrusted-network-accessible instances.
Restrict access to trusted networks while upgrades are pending.
Consult the vendor advisory and release notes before deployment.
Validation and detection
Inventory Looking Glass instances and record their deployed versions.
Confirm every instance runs version 1.3.5 or later.
Determine whether BGP lookup functionality is reachable from untrusted networks.
Review available application and host telemetry for suspicious requests or unexpected command execution.
Verify temporary network restrictions remain effective until upgrades finish.
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-78: 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.
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.
1CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: 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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-78 · source CWE mapping
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.