# CVE-2026-10756: TRO600 contains a vulnerability that allows an authenticated attacker to bypass network access restrictions and access services intended to


- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-h7g2-j4fw-5qp6

## What is CVE-2026-10756?

CVE-2026-10756 is a high-severity vulnerability in Hitachi Energy TRO600 Series Firmware, published on 27 Oct 2026. 

### Official description

TRO600 contains a vulnerability that allows an authenticated attacker to bypass network access restrictions and access services intended to be reachable only from localhost. By leveraging port forwarding, an attacker can interact with locally bound ports and services, resulting in unauthorized access to sensitive functionality and confidential information, and causing availability impact.

Weakness: CWE-923 (Improper Restriction of Communication Channel to Intended Endpoints)

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


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

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

## Is CVE-2026-10756 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-10756 is a high-severity vulnerability in Hitachi Energy TRO600 Series Firmware, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-10756 in the wild and no public exploit code.

Affected product: Hitachi Energy TRO600 Series Firmware. 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-10756/ (Markdown: https://insights.sbomify.com/CVE-2026-10756/index.md)
```

## Sources

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

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