# CVE-2026-34485: A CLI ACL Bypass vulnerability in Nokia 1830 Global Express (GX)


- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-3hcg-f3cv-j8xc

## What is CVE-2026-34485?

CVE-2026-34485 is a high-severity vulnerability in Nokia 1830 Global Express (GX), published on 20 Oct 2026. 

### Official description

Nokia 1830 Global Express (GX) is vulnerable to a CLI ACL Bypass vulnerability where a low-privileged authenticated attacker can bypass the SSH isolation mechanism and gain access to the underlying operating system shell via a custom SSH command. This issue occurs by default in the system and is not the result of misconfiguration.

Weakness: CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2026-34485 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-34485 is a high-severity vulnerability in Nokia 1830 Global Express (GX), published on 20 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-34485 in the wild and no public exploit code.

Affected product: Nokia 1830 Global Express (GX). 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-34485/ (Markdown: https://insights.sbomify.com/CVE-2026-34485/index.md)
```

## Sources

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

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