# CVE-2026-5270: Authentication Bypass in Navigator and Blue Planet Products

> Unauthenticated attackers can bypass authentication and audit logging in Ciena Navigator and Blue Planet products by manipulating HTTP requests.

- **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
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** GHSA-rp4h-q5qj-wrcr

## What is CVE-2026-5270?

CVE-2026-5270 is a critical authentication bypass vulnerability in Blue Planet Inventory, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authentication bypass vulnerability exists in certain releases of Ciena Navigator Network Control Suite (NCS), Manage Control Plan (MCP), and Blue Planet products. The issue is caused by improper handling of HTTP request paths and headers, which allows an unauthenticated attacker to manipulate requests in a manner that bypasses authentication and associated audit logging controls.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-5270 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-5270 is a critical authentication bypass vulnerability in Blue Planet Inventory, published on 14 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-5270 in the wild and no public exploit code.

Affected product: Blue Planet Inventory. 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-5270/ (Markdown: https://insights.sbomify.com/CVE-2026-5270/index.md)
```

## Sources

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

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