/

CVE-2026-76133

Severity:

CRITICAL RISK

(9.8)

Broken Crypto (CWE-327) in Ebyte Authentication Flow

CVE-2026-76133

Deferred

Vulnerability type

Category:

Use of Broken or Risky Cryptographic Algorithm

CWE:

CWE-327

Impact:

Authentication Bypass and Unauthorized Access

Severity:

CRITICAL RISK

(9.8)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

An affected Ebyte product uses a deprecated hashing algorithm in an authentication-related operation, weakening the protection provided by the authentication exchange. If an attacker can manipulate or predict that exchange, the weakness may facilitate unauthorized access; the CVSS base score is 9.8 (Critical).

Affected context

The vulnerability occurs in Ebyte product functionality that relies on a deprecated hashing algorithm during authentication. Risk is greatest where authentication inputs, messages, or protocol exchanges can be influenced, replayed, or predicted by an attacker, and where the resulting hash provides insufficient assurance for identity or message validation.

Exploit preconditions

  • Attack surface: An authentication interface or protocol exchange involving the affected Ebyte product
  • Required access: The ability to interact with, observe, manipulate, or predict relevant authentication data
  • Trigger point: Processing or validating the authentication exchange with the deprecated hashing construction
  • Why exploitation is possible: The weak cryptographic construction may allow authentication data to be forged, reused, or otherwise accepted with less assurance than intended

Why this happens

The underlying issue is the use of a deprecated or insufficiently secure hashing algorithm in an authentication-related security decision. This maps to CWE-327: Use of a Broken or Risky Cryptographic Algorithm, where a cryptographic primitive no longer provides adequate resistance or assurance for its intended purpose. The insecure pattern is relying on a weak hash as a standalone authentication control or as part of a construction that does not provide appropriate integrity, freshness, and verifier protection.

Potential impact

  • An attacker may bypass authentication controls
  • Unauthorized users could gain access to protected product functions
  • Authentication tokens or messages could be forged or improperly validated
  • Account, device, or operational data could be exposed or modified
  • Compromised access could support further activity against connected systems

General mitigation guidance

Mitigation generally focuses on removing deprecated cryptographic dependencies from authentication decisions and reducing trust in attacker-influenced exchange data.

Common defensive patterns include:

  • Use modern, standardized authentication and message-integrity constructions appropriate to the protocol
  • Avoid using a deprecated hash as a password verifier, authentication token validator, or standalone integrity control
  • Bind authentication messages to the intended identity, session, context, and freshness value
  • Require strong, independently generated secrets and protect them with least-privilege access controls
  • Provide secure-by-default cryptographic configuration and prevent fallback to weak algorithms
  • Preserve compatibility only through explicitly controlled, temporary negotiation paths with policy enforcement

How teams detect issues like this

Organizations commonly detect this class of issue through:

  • Static analysis rules identifying deprecated hash APIs in authentication, token, and protocol-validation code
  • Software inventory and cryptographic policy scans that flag weak algorithms and insecure fallback behavior
  • Code review checks for hashes used without proper keying, freshness, domain separation, or protocol binding
  • Runtime and gateway telemetry showing unexpected authentication failures, repeated exchanges, downgrade attempts, or replay-like activity
  • Policy enforcement that blocks disallowed algorithms in product configuration and deployment pipelines

Automated security review tools may help identify cryptographic API misuse, but findings should be validated against the complete authentication design.

Sources

SourceLink
github.comgithub.com/cisagov/CSAF/blob/develop/csaf_files/OT/white/2026/icsa-26-237-06.json
cisa.govcisa.gov/news-events/ics-advisories/icsa-26-237-06

Frequently asked

questions

It may be remotely exploitable when the affected authentication interface is network-accessible and an attacker can manipulate, observe, or predict relevant authentication exchanges. The exact scope depends on the product's deployment and protocol controls.

Not necessarily. An attacker may only need access to the authentication endpoint or exchange; however, network segmentation, client authentication, and protocol protections can change the required access level.

Replace the deprecated hashing construction with a modern, protocol-appropriate authentication and integrity mechanism, while binding exchanges to the correct identity, session, and freshness context.

Maintain an approved cryptographic policy, prohibit deprecated algorithms in authentication code and configuration, review protocol designs for replay and forgery resistance, and continuously scan source code and deployed configurations.

Find out what's already
exploitable in your codebase.