# CVE-2026-53611: Looking Glass: Remote Code Execution via Unanchored Regular Expression in BGPASPath Input Validation


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 2 Sep 2026
- **Updated:** 2 Sep 2026
- **Also known as:** GHSA-8hgf-p844-425m

## What is CVE-2026-53611?

CVE-2026-53611 is a critical vulnerability in AS203038 looking-glass, published on 2 Sep 2026. 

### Official description

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.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2026-53611?


## How do I fix CVE-2026-53611?

No fix has been published for CVE-2026-53611 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-53611 being exploited?

There is no known exploitation of CVE-2026-53611 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-53611 and fix it if it is affected.

What it is: CVE-2026-53611 is a critical vulnerability in AS203038 looking-glass, published on 2 Sep 2026. 
Exploitation: There is no known exploitation of CVE-2026-53611 in the wild and no public exploit code.

Affected product: AS203038 looking-glass. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-53611/ (Markdown: https://insights.sbomify.com/CVE-2026-53611/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-53611
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-53611
- OSV: https://osv.dev/vulnerability/CVE-2026-53611

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-53611/
Summaries are generated and may contain mistakes; the official description above is the record.