HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorKeep agent security open: sponsor a project, place a banner, or fund a security initiative.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 71396 use of hard coded credentials in bendix ec80
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Medium · CVSS 5.4CVE-2026-71396

Use of Hard-coded Credentials in Bendix EC80 Brake ECUCVE-2026-71396

Answer in brief

CVE-2026-71396 records a Medium severity (CVSS 5.4) vulnerability in Use of Hard-coded Credentials in Bendix EC80 Brake ECU. The current sources do not mark it as known exploited. The current feed maps Bendix/EC80ESP 2nd CAN (generic), Bendix/EC80ESP+ 2nd CAN (generic), Bendix/EC80ESP 4S/4M (generic), Bendix/EC80ESP 6S/6M (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Aug 27, 2026Updated Aug 31, 2026Source checked Oct 12, 2026First seen by HOL Aug 27, 2026Material review Aug 31, 2026
Upstream Advisory

Key facts

Risk
Medium · CVSS 5.4
Exploitation
Not marked as known exploited
Affected software
11 mapped packages or products
Fix availability
Not reported

Why this deserves its current priority

CVSS is 5.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps Bendix/EC80ESP 2nd CAN (generic), Bendix/EC80ESP+ 2nd CAN (generic), Bendix/EC80ESP 4S/4M (generic), Bendix/EC80ESP 6S/6M (generic) and additional mapped packages. Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
Bendix/EC80ESP 2nd CANgenericZ266494Not reported
Bendix/EC80ESP+ 2nd CANgenericZ228999Not reported
Bendix/EC80ESP 4S/4MgenericZ286098Not reported
Bendix/EC80ESP 6S/6MgenericZ266494Not reported
Bendix/EC80ESP+ 6S/6MgenericZ228999Not reported
Bendix/EC80ESP CAN GatewaygenericZ266494Not reported
Bendix/EC80ESP+ Integrated TPMSgenericZ228999Not reported
Bendix/EC80ESP+ J1708genericZ228999Not reported
Bendix/EC80ESP PLCgenericZ266494Not reported
Bendix/EC80ESP PLCgenericZ286098Not reported
Bendix/EC80ESP+ PLCgenericZ228999Not reported

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for Bendix/EC80ESP 2nd CAN, Bendix/EC80ESP+ 2nd CAN, Bendix/EC80ESP 4S/4M.
  2. 2Review the reported fix. Source-reported solution: Bendix recommends users update their firmware to the most recent firmware version releases. Users that need more help should contact Bendix directly at [email protected]. * EC80ESP+ J1708: Users should update their firmware to version Z300822. * EC80ESP+ 6S/6M: Users  should update their firmware to version Z300822. * EC80ESP+ PLC: Users  should update their firmware to version Z300822. * EC80ESP+ 2nd CAN: Users should update their firmware to version Z300822. * EC80ESP+ Integrated TPMS: Users should update their firmware to version Z300822. * EC80ESP 6S/6M: Users should update their firmware to version Z302578. * EC80ESP PLC: Users should update their firmware to version Z302578. * EC80ESP 2nd CAN: Users should update their firmware to version Z302578. * EC80ESP CAN Gateway: Users should update their firmware to version Z302578. * EC80ESP 4S/4M: Users should update their firmware to version Z302579. * EC80ESP PLC: Users should update their firmware to version Z302579.

Evidence timeline and material changes

  1. Published upstream

    Aug 27, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  2. Source modified

    Aug 31, 2026

    Evidence: source:cvelist:source_dates:source-dates:record

  3. First seen by HOL

    Aug 27, 2026

Sources and claim methodology

  • GitHub security advisorygithub.com
  • CISA Known Exploited Vulnerabilities catalogcisa.gov
Upstream source description

Bendix EC80 Brake ECU uses hard-coded credentials, which could allow an attacker to disable automatic traction control.

Quoted source text, attributed separately from HOL analysis.

Related CVEs

  • Plaintext Database Password Exposure in GV-E-Map Server V18.2.0AAlso CWE-798
  • pH7Builder before 18.6.0 Hard-Coded API Key Bypass via Host HeaderAlso CWE-798
  • Channel tokens and organization API key exposed in API responsesSame generic ecosystem
  • zhayujie CowAgent Streaming Tool-Call Argument json.loads allocation of resourcesSame generic ecosystem
  • zhayujie CowAgent Markdown Rendering Markdown.tsx denial of serviceSame generic ecosystem
  • Appwrite Browser Screenshot Service Get.php PublicHostname server-side request forgerySame generic ecosystem

Record context

Vulnerability class
Secret Exfiltration
EPSS
Not reported
CWE IDs
CWE-798
Source
CVE List V5
Source checked
Oct 12, 2026
References
2 linked sources
Open source record