Skip to main content
Menu
CVEs

Elecbrakes authentication bypass in command channel

Affects Elecbrakes EB2 at or below 3.0.4.2.0, VM1 below 1.3.4.2.1, and all ELBC2000 versions. Fixed in VM1 1.3.4.2.1.

CVE-2026-125273Published , updated

9.6CriticalCNA
Exploited
No known exploitation
Fix
Fixed in 1.3.4.2.1
Who is exposed
Not reported

Summary

Elecbrakes EB2, ELBC2000, and VM1 do not protect commands against replay, so an attacker on an adjacent network can capture valid commands and resend them without logging in, bypassing authentication. The last command also persists across sessions, so replayed commands can take effect again later.

Written by a model

Original description

No replay or command-integrity protection. Commands lack sequence numbers, nonces, or session tokens; captured commands can be replayed, and the last command persists across sessions.

Who should check

Teams running Elecbrakes EB2 at or below 3.0.4.2.0, Elecbrakes VM1 below 1.3.4.2.1, or Elecbrakes ELBC2000 trailer brake controllers.

“EB2 <=3.0.4.2.0 (CVE-2026-124281, CVE-2026-125273, CVE-2026-96805)”

cisa.gov

What to do

Upgrade to a fixed version: 1.3.4.2.1.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-125273 (Elecbrakes Authentication Bypass by Capture-replay), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-125273 (entry last updated 2026-11-20):
Affected:
- Elecbrakes EB2: through 3.0.4.2.0
- Elecbrakes ELBC2000: all versions
- Elecbrakes VM1: fixed in 1.3.4.2.1
Fixed versions: 1.3.4.2.1.
Conditions (all must be true for the bug to be hit):
- Affected Elecbrakes EB2 at or below 3.0.4.2.0, VM1 below 1.3.4.2.1, or ELBC2000 (all versions). (source: https://www.cisa.gov/news-events/ics-advisories/icsa-26-323-02)
- Commands lack sequence numbers, nonces, or session tokens, so captured commands can be replayed. (source: https://www.cisa.gov/news-events/ics-advisories/icsa-26-323-02)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: adjacent access, no login, no user action.
CISA KEV: CVE-2026-125273 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125273 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.cisa.gov/news-events/ics-advisories/icsa-26-323-02
- https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-323-02.json
- https://www.cve.org/CVERecord?id=CVE-2026-125273
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-125273
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-125273"}.

Affected versions

cve.now Index

10Pof 100 · provisional · methodology v3
  • Exploitation0/40No signal
  • Exposure?/25Unknown. Advisories don't say whether default setups are affected
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity9.6/10CVSS 9.6
  • No patch0/5No signal

What would change the score

  • Would score about 65 if added to CISA KEV
  • Would score about 60 if CISA's SSVC rates exploitation active
  • Would score about 32 if advisories confirm default setups are exposed

Timeline

  1. cve.now early warning

    CISA warns of flaws in Elecbrakes EB2, VM1 and ELBC2000 trailer brake controllers

    1 day
  2. CVE published
  3. First seen by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  5. Record last updated

Evidence 3

Questions about CVE-2026-125273

Is CVE-2026-125273 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: cve.now feed data

What does this mean?

Device commands lack sequence numbers, nonces, or session tokens, so captured commands can be replayed. The last command persists across sessions and can affect braking control of a trailer.

Source: cisa.gov, cve.org

Which versions are affected by CVE-2026-125273?

EB2: through 3.0.4.2.0. ELBC2000: all versions. VM1: before 1.3.4.2.1.

Source: cve.now feed data

Am I affected, and how do I check?

EB2 versions at or below 3.0.4.2.0, VM1 versions below 1.3.4.2.1, and all ELBC2000 versions are listed as affected. Compare the product model and its firmware version with these ranges.

Source: cisa.gov, cve.org

How do I fix CVE-2026-125273?

For VM1, update to 1.3.4.2.1 or later. Elecbrakes recommends EB2 3.0.4.4.3 and says to install the firmware update through the Elecbrakes app.

Source: cisa.gov, cve.org

No corrections so far. Something wrong on this page? Report an error.