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

> Attackers can bypass startup authentication in GE Vernova EnerVista UR Setup by modifying a Windows registry setting accessible to any user.

- **Severity:** High 8.0 (`CVSS:3.1/AV:L/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:** 7 Oct 2025
- **Also known as:** GHSA-pw5w-rmc5-f87r

## What is CVE-2025-27254?

CVE-2025-27254 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

CWE-282 "Improper Ownership Management" in GE Vernova EnerVista UR Setup allows Authentication Bypass. 
The software's startup authentication can be disabled by altering a Windows registry setting that any user can modify.

Weakness: CWE-282 (Improper Ownership Management)

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


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

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

## Is CVE-2025-27254 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27254 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-27254 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-27254/ (Markdown: https://insights.sbomify.com/CVE-2025-27254/index.md)
```

## Sources

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

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