# CVE-2025-1727: End-of-Train and Head-of-Train Remote Linking Protocol Weak Authentication

> Attackers can bypass weak authentication in railway brake protocols using SDR to issue unauthorized brake commands, causing operational disruption.

- **Severity:** High 7.2 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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 Jul 2025
- **Updated:** 11 Jul 2025
- **Also known as:** GHSA-q5w3-wqpr-96vw

## What is CVE-2025-1727?

CVE-2025-1727 is a high-severity authentication bypass vulnerability in End-of-Train and Head-of-Train remote linking protocol, published on 10 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The protocol used for remote linking over RF for End-of-Train and 
Head-of-Train (also known as a FRED) relies on a BCH checksum for packet
 creation. It is possible to create these EoT and HoT packets with a 
software defined radio and issue brake control commands to the EoT 
device, disrupting operations or potentially overwhelming the brake 
systems.

Weakness: CWE-1390 (Weak Authentication)

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


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

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

## Is CVE-2025-1727 being exploited?

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

Public exploit code:

- Rail-OT-Protector (ROP) — free, open-source cybersecurity scanning tool for rail and transit OT/SCADA networks. PowerShell + Bash scanners for CVE-2025-1727, RailSafe legacy API, ICS protocol exposure, and remote access risk. (github_poc): https://github.com/spinfosecurity/Rail-OT-Protector

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1727 is a high-severity authentication bypass vulnerability in End-of-Train and Head-of-Train remote linking protocol, published on 10 Jul 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-1727 in the wild and no public exploit code.

Affected product: End-of-Train and Head-of-Train remote linking protocol. 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-1727/ (Markdown: https://insights.sbomify.com/CVE-2025-1727/index.md)
```

## Sources

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

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