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

> Attackers can bypass firewall rules and send malicious network traffic via TCP port forwarding due to missing IP and port validation in GE Vernova IEDs.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:L`)
- **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-j5vp-q6vg-25mf

## What is CVE-2025-27253?

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

A CWE-15 "External Control of System or Configuration Setting" in GE Vernova UR IED family devices from version 7.0 up to 8.60 allows an attacker to provide input that establishes a TCP connection through a port forwarding. The lack of the IP address and port validation may allow the attacker to bypass firewall rules or to send malicious traffic in the network.

Weakness: CWE-15 (External Control of System or Configuration Setting)

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


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

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

## Is CVE-2025-27253 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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