CVE-2026-125275
Received Received - Intake

Infinite Loop in NervesHub Web via TLS Certificate Verification

Vulnerability report for CVE-2026-125275, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-17

Last updated on: 2026-11-17

Assigner: EEF

Description

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in device certificate verification in nerves-hub nerves_hub_web allows an unauthenticated remote attacker to cause a denial of service via a TLS client certificate whose CA is not registered. When a client certificate chains to a root in the device endpoint's trust store but no CA in the chain is registered in NervesHub, NervesHub.SSL.decide/2 refuses it with the reason :unknown_ca. Erlang/OTP ssl reads that reason as a missing trust anchor, looks for an alternative root, finds the same root and validates again without end. The handshake process queries the database on each pass and keeps running after the client disconnects, until the node restarts. The device endpoint trusts the public roots from CAStore unless DEVICE_SSL_CACERTFILE is set, so a client certificate from a public CA whose chain allows client authentication is sufficient. A chain that ends at a root outside the trust store is refused once. This issue affects nerves_hub: from 1.0.0 before 2.5.4.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-17
Last Modified
2026-11-17
Generated
2026-11-17
AI Q&A
2026-11-17
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
nerves-hub nerves_hub_web From 1.0.0 (inc) to 2.5.4 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-835 The product contains an iteration or loop with an exit condition that cannot be reached, i.e., an infinite loop.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is an Infinite Loop vulnerability in NervesHub, an IoT device management platform. When a device presents a TLS client certificate signed by an unregistered Certificate Authority (CA), the system incorrectly interprets the rejection reason as :unknown_ca. This causes the Erlang/OTP SSL module to repeatedly search for a trust anchor, creating an infinite loop of database queries and handshake attempts. The process continues even after the client disconnects, consuming system resources until the node restarts.

Detection Guidance

Monitor for TLS handshake loops by checking for persistent Erlang/OTP SSL processes consuming high CPU or database resources. Use system monitoring tools like 'htop' or 'ps' to identify unusual process activity. Check logs for repeated 'unknown_ca' errors in TLS handshake attempts.

Impact Analysis

An unauthenticated remote attacker can exploit this to cause a denial of service by triggering the infinite loop. Each malicious connection spawns a persistent process that consumes CPU, memory, and database resources. This can saturate system capacity, making NervesHub unavailable for legitimate devices and users until the node is restarted. The impact is limited to system availability.

Compliance Impact

This vulnerability primarily impacts system availability due to resource exhaustion from infinite TLS handshake loops. While it does not directly violate GDPR or HIPAA, it could indirectly affect compliance by disrupting services that handle personal health or user data. Unavailability of systems may lead to breaches of service-level agreements or data processing timelines required by these regulations.

Mitigation Strategies
  • Upgrade NervesHub to version 2.5.4 or later to apply the fix for the infinite loop issue.
  • Set the DEVICE_SSL_CACERTFILE environment variable to a bundle excluding public roots or device-signing roots as a temporary workaround.
  • Restart affected nodes to terminate any stuck handshake processes causing resource exhaustion.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-125275. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...