Skip to content

OT/ICSHigh 8.5

CVE-2026-96805

Unauthenticated BLE command injection can let attackers control braking systems.

How scary is it?

updated 22 Nov 2026
  • Yes

    Works without logging in1

    No account and no user action needed (CVSS PR:N, UI:N).

  • No

    Reachable over the network1

    Needs access to the same local network (CVSS AV:A).

  • None known

    Public exploit code is out

    None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.

  • None known

    Attacks seen in the wild1

    None reported that we know of. CISA's SSVC assessment says exploitation: none.

  • No

    On CISA's exploited list2

    Not in the catalog as of our last sync.

Scare-o-meter

Routine patch

Serious on paper, with no sign of attacks that we know of. Patch in your normal cycle.

  1. Low signal
  2. Routine patch
  3. Act this week
  4. Drop everything

Why: our alert rule found no exploitation evidence and no easy remote attack path in the data we hold. Read from the same rule that decides our alert emails.

Are you affected? only if all are true

  1. You run one of these 3 products in an affected versionElecbrakes EB2 / Elecbrakes ELBC2000 / Elecbrakes VM1

    Elecbrakes EB2: <= 3.0.4.2.0

    Elecbrakes ELBC2000: All versions

    Elecbrakes VM1: < 1.3.4.2.1

    As published in the CVE record. A version outside these ranges is not a statement that it is unaffected: vendors sometimes understate a range, and distribution builds with backported fixes keep the upstream number.

    See the affected products table · Source 1

  2. The attacker is on the same local network

    CVSS attack vector: Adjacent (AV:A). Same subnet or link layer.

    Source 1

Read from the CVE record: affected versions and the CVSS vector. It narrows things down. It does not prove you are safe.

What to do

  1. Per the vendorUpgrade to a fixed releaseEB2 3.0.4.4.3 / VM1 1.3.4.2.1

    Elecbrakes EB2: EB2 3.0.4.4.3

    Elecbrakes VM1: VM1 1.3.4.2.1

    Fixed releases as stated by the vendor in the CVE record.

    See the affected products table · Source 1

  2. Recommendation, AI-writtenDisable BLE, isolate affected devices, apply vendor mitigations, monitor for vendor patch

    Written by a language model from the CVE record. It is not the vendor's wording: check it against the sources.

Steps marked AI were written by a language model, from the CVE record or from the linked news pages. They are not the vendor's wording: check them against the sources.

CVSS
8.5Highscored by the publisher (CNA)
Exploited in the wild
Not knownnot in CISA KEV as of our last sync
EPSS
No score yet
Fix
Fixed in EB2 3.0.4.4.3, VM1 1.3.4.2.1per the vendor
Published
20 Nov 2026analysed here 22 Nov 2026

Do first. Upgrade to a fixed release: EB2 3.0.4.4.3, VM1 1.3.4.2.1.

Summary

Impact

In-range unauthenticated BLE attacker can write to control interface to influence or trigger braking, causing safety and operational disruption.

Triage

Attack surface
Server-side
Exploitable
At runtime
Attack vector
adjacent network
Weakness
Can a WAF block it?
No. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

ProductAffected versions
Elecbrakes EB2<= 3.0.4.2.0Vendor says fixed in: EB2 3.0.4.4.3
Elecbrakes ELBC2000All versionsVendor says fixed in: not stated
Elecbrakes VM1< 1.3.4.2.1Vendor says fixed in: VM1 1.3.4.2.1

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

Products named in our analysis

  • BLE-enabled brake control units
  • Industrial braking systems
  • Vehicle ECUs with affected BLE stacks
  • OT/ICS controllers with BLE interfaces

Fix and mitigation

Action required

Immediate action required

WAF and other mitigations

Can a WAF block it? No. The attack is delivered via Bluetooth Low Energy (BLE) commands, which are not HTTP requests and thus cannot be filtered by a web application firewall.

Also consider: patch

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Not listed as of our last sync.
Public exploit code
None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
CISA SSVC
exploitation none, automatable no, technical impact partialAssessed by CISA 20 Nov 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Timeline

  1. 20 Nov 2026Published
  2. 20 Nov 2026CISA SSVC assessment: exploitation nonesame day later
  3. 20 Nov 2026CVE record last updatedsame day later
  4. 22 Nov 2026Analysed by vulneraibility.com2 days later

Common questions

Is CVE-2026-96805 being exploited?

Not confirmed. CVE-2026-96805 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked.

How severe is CVE-2026-96805?

CVE-2026-96805 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-96805?

Not known from our data. No patch reference has been recorded for CVE-2026-96805, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-96805 affect?

CVE-2026-96805 affects BLE-enabled brake control units, Industrial braking systems, Vehicle ECUs with affected BLE stacks, OT/ICS controllers with BLE interfaces. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-96805?

Disable BLE, isolate affected devices, apply vendor mitigations, monitor for vendor patch

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

2 references in the CVE record, grouped by the tags the record gives them.

Other links (2)

  • cisa.gov /news-events/ics-advisories/icsa-26-323-02
  • github.com /cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-323-02.json

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.