# CVE-2025-27256: Auth bypass in EnerVista UR Setup

> Missing SSH authentication in GE Vernova Enervista UR Setup allows attackers to perform man-in-the-middle attacks on the network.

- **Severity:** High 8.3 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Mar 2025
- **Updated:** 12 Mar 2025
- **Also known as:** GHSA-gjhg-f944-56m2

## What is CVE-2025-27256?

CVE-2025-27256 is a high-severity authentication bypass vulnerability in GE Vernova EnerVista UR Setup, published on 10 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Missing Authentication for Critical Function vulnerability in GE Vernova Enervista UR Setup application allows Authentication Bypass due to a missing SSH server authentication. Since the client connection is not authenticated, an attacker may perform a man-in-the-middle attack on the network.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2025-27256?


## How do I fix CVE-2025-27256?

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

## Is CVE-2025-27256 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-27256 and fix it if it is affected.

What it is: CVE-2025-27256 is a high-severity authentication bypass vulnerability in GE Vernova EnerVista UR Setup, published on 10 Mar 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27256 in the wild and no public exploit code.

Affected product: GE Vernova EnerVista UR Setup. 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-2025-27256/ (Markdown: https://insights.sbomify.com/CVE-2025-27256/index.md)
```

## Sources

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

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