Brake Check: Hijacking Trailer Brakes over Bluetooth
Comments on “Brake Check: Hijacking Trailer Brakes over Bluetooth”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Element Digital researchers Patrick Forck and Jeremy McCarthy report that Elecbrakes trailer brake controllers accepted a four-byte Bluetooth write that applied the brakes at any force, with no pairing or authentication. Their testing used their own hardware. CISA's advisory lists three CVEs, the headline one rated CVSS 9.6. A firmware fix for the EB2 and VM1 shipped in July, but the older ELBC 2000 has none. The firmware update channel also uses CRC checks, not signatures. Several figures come only from the researchers and Elecbrakes.
Why it ranked
No. 20 of 118 with a score of 0.71. The panel rated it highest on new information (0.94) and substantiated (0.90), lowest on audience breadth (0.43). Placed No. 20, No. 11 by score alone: the eighth Security story of the day (−0.080). The placement terms move stories; they are not part of the score.
- AI judgeJudge 2claude-haiku-5-5
- Detailed, well-substantiated IoT security disclosure with CVEs and reproducible method; safety-critical and new, though the audience is narrower than general software builders and the piece is long on coordination narrative.
- AI judgeJudge 3gpt-5.6-luna
- A deeply evidenced disclosure details unauthenticated Bluetooth control of safety-critical trailer brakes, exploit mechanics, remediation, residual exposure, and disclosure-process lessons. It is highly relevant to security and connected-hardware builders, though hardware scope limits breadth.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.71total under rubric v2.3
- Significance0.68
- Reader interest0.87
- Audience breadth0.43
- Practical relevance0.74
- Substantiated0.90
- Technical depth0.86
- New information0.94
- Counts against: Promotional0.03
- Counts against: Overclaim0.20
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.59 | 0.60 | 0.86 | 0.68 | 0.27 | +0.24 | +0.164 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.81 | 0.85 | 0.94 | 0.87 | 0.13 | +0.26 | +0.225 |
| Audience breadthHow many people who build technology does it concern? | 0.37 | 0.50 | 0.42 | 0.43 | 0.13 | +0.13 | +0.056 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.82 | 0.60 | 0.79 | 0.74 | 0.23 | +0.22 | +0.162 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.94 | 0.85 | 0.90 | 0.90 | 0.09 | +0.05 | +0.045 |
| Technical depthHow technically substantive is it? | 0.99 | 0.70 | 0.88 | 0.86 | 0.29 | +0.05 | +0.043 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.91 | 0.90 | 1.00 | 0.94 | 0.10 | +0.05 | +0.047 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.04 | 0.05 | 0.01 | 0.03 | 0.04 | −0.19 | −0.006 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.21 | 0.20 | 0.18 | 0.20 | 0.03 | −0.11 | −0.022 |
| Sum of contributions | +0.715 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.715 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-21/20/"><img src="https://rubric.hrih.si/badge/2026-11-21/20.svg" alt="Ranked #20 on Rubric, 21 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 1 matches source · 6 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
Matches sourceNumber
CISA's advisory, published 19 November, covers three CVEs including CVE-2026-96805, which is rated CVSS 9.6 (Critical).
The cited source says the same thing.
The article says “CISA’s advisory, published on 19 November, covers three CVEs - CVE-2026-96805 (CVSS 9.6, Critical), CVE-2026-125273 and CVE-2026-124281”
The source says “3.1 | 9.6 | CRITICAL | CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/C:L/I:H/A:H”
Source cited by the article: cisa.gov/news-events/ics-advisories/icsa-26-323-02
Couldn’t checkQuote
CISA described the headline CVE as missing authentication for critical functions, which may allow an attacker to remotely activate, modulate and release trailer brakes at arbitrary force levels without authentication.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “The affected product is missing authentication for critical functions, which may allow an attacker to remotely activate, modulate, and release trailer brakes at arbitrary force levels”
The source says No passage could be compared.
Source cited by the article: cisa.gov/news-events/ics-advisories/icsa-26-323-02
No source givenDate
Elecbrakes shipped a firmware fix for the EB2 and VM1 on 6 July 2026, seven weeks after the 18 May 2026 disclosure.
The article gives no link or citation for it.
The article says “Elecbrakes shipped a firmware fix for the EB2 and VM1 on 6 July 2026, seven weeks later”
The source says No source to compare with.
No source givenCausal conclusion
Any Bluetooth device in range of an Elecbrakes trailer brake controller could apply the trailer's brakes at any force without pairing, a PIN or authentication, using four bytes.
The article gives no link or citation for it.
The article says “Any phone or laptop within Bluetooth range of an Elecbrakes trailer brake controller could apply that trailer’s brakes - at any force, at highway speed - without pairing, a PIN,…”
The source says No source to compare with.
No source givenNumber
The decompiled Elecbrakes app revealed 47 GATT characteristics across four services, while the app only shows 42 of them.
The article gives no link or citation for it.
The article says “47 characteristics across four services, commands sent as plain unencrypted byte arrays, no checksums, no sequence numbers”
The source says No source to compare with.
No source givenNumber
The ELBC 2000, the older Elecbrakes model, has the same vulnerability and has no fix as of publication, according to Elecbrakes.
The article gives no link or citation for it.
The article says “At the end of October their engineering team confirmed it has the same vulnerability”
The source says No source to compare with.
No source givenNumber
By late October, Elecbrakes' figures showed about 60% of daily active EB2 and VM1 users were on the latest firmware.
The article gives no link or citation for it.
The article says “its own figures showed about 60% of daily active EB2 and VM1 users were on the latest firmware”
The source says No source to compare with.
No source givenNumber
Elecbrakes went 53 days without a word on the case, passing CISA's 45-day silence threshold at the end of September.
The article gives no link or citation for it.
The article says “From mid-August, Elecbrakes went 53 days without a word on the case or by email, which took it past the 45-day mark at the end of September”
The source says No source to compare with.
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 3 pts, not on front page
Recorded for context only, checked 21 Nov 2026, 05:47 UTC. It played no part in the ranking.