CVE-2025-1727 affects the RF remote-linking protocol used between Head-of-Train (HoT/FRED) and End-of-Train (EoT) devices. According to the provided content, the protocol relies on a BCH checksum for packet creation/integrity, and this is insufficient as a security control. An attacker can use a software-defined radio to craft valid-looking HoT/EoT packets and transmit brake control commands to the EoT device. The issue is therefore a lack of cryptographic authentication/integrity protection in a safety-relevant wireless control protocol, allowing forged command packets to be accepted by the target device.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
16 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.