# CVE-2025-27257: Security feature bypass in B30 Multilin

> Authenticated attackers can bypass client-side firmware signature checks to install modified firmware on GE Vernova UR IED devices.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **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-5v9q-jpv7-7w2m

## What is CVE-2025-27257?

CVE-2025-27257 is a medium-severity vulnerability in GE Vernova B30 Multilin, 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

Insufficient Verification of Data Authenticity vulnerability in GE Vernova UR IED family devices allows an authenticated user to install a modified firmware.
The firmware signature verification is enforced only on the client-side dedicated software Enervista UR Setup, allowing the integration check to be bypassed.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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


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

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

## Is CVE-2025-27257 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27257 is a medium-severity vulnerability in GE Vernova B30 Multilin, 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-27257 in the wild and no public exploit code.

Affected product: GE Vernova B30 Multilin. 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-27257/ (Markdown: https://insights.sbomify.com/CVE-2025-27257/index.md)
```

## Sources

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

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