Bransys ELD is shipped with hardcoded MQTT credentials, which will grant read access to real-time data for every active device across a subset of carriers that were connected to the affected MQTT broker.
CVE-2026-77960
Score 5.3 from GitHub Security Advisory published 2026-09-18. a secondary CVSS source baseline 5.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 5.3
- EG Score
- 5.3(high)
- EG Risk
- 28(Track)EG Risk 28/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity53% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 15%
- KEV
- Not listed
Published
September 18, 2026
Last Modified
September 18, 2026
Advisory Details (2)
Auto-updated Sep 18, 2026CSAF/csaf_files/OT/white/2026/icsa-26-260-01.json at develop · cisagov/CSAF · GitHub
https://github.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-260-01.jsonBransys ELD | CISA
https://www.cisa.gov/news-events/ics-advisories/icsa-26-260-01Vendor Advisories for CVE-2026-77960(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-09-20 23:20 UTCEG score recompute
- 2026-09-20 23:19 UTCGHSA enrichment
- 2026-09-20 20:16 UTCEPSS rescore
- 2026-09-19 21:13 UTCEG score recompute
- 2026-09-19 21:13 UTCGHSA enrichment
- 2026-09-18 19:07 UTCEG score recompute
- 2026-09-18 19:07 UTCGHSA enrichment
- 2026-09-18 16:25 UTCEG score recompute
- 2026-09-18 15:54 UTCEG score recompute
- 2026-09-18 15:54 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-798
- CVE-2026-75754EG 10.0CRITICAL
- CVE-2026-18452EG 10.0CRITICAL
- CVE-2026-45336EG 10.0CRITICAL
- CVE-2026-13768EG 10.0CRITICAL
- CVE-2026-45631EG 10.0CRITICAL
- CVE-2026-42869EG 10.0CRITICAL
- CVE-2026-29128EG 10.0CRITICAL
- CVE-2026-22769EG 10.0 KEVEPSS p96CRITICAL
- CVE-2026-86464EG 9.9CRITICAL
- CVE-2026-46386EG 9.9CRITICAL
Frequently asked(5)
What is CVE-2026-77960?
When was CVE-2026-77960 disclosed?
Is CVE-2026-77960 actively exploited?
What is the CVSS score of CVE-2026-77960?
How do I remediate CVE-2026-77960?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-77960
Is Your Infrastructure Affected by CVE-2026-77960?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.