NervesHub 2.5.4 Stops Persistent TLS Handshake Loops

P1 — VALIDATE AND UPDATEHigh · 8.2 (CVSS v3.1)EXPLOITATION: NOT STATED

Quick Answer

Upgrade NervesHub to 2.5.4 and restart affected nodes to clear stuck handshakes. Review the device endpoint trust store and registered CAs.

Confirm Scope And Apply The Supported Remediation

What to do now: Record NervesHub and Erlang/OTP builds, device TLS endpoints, DEVICE_SSL_CACERTFILE configuration, trusted roots, registered CAs and device-node/database load. The supplied certificate must chain to a root trusted by the device endpoint while its CA is unregistered. Arbitrary self-signed certificates outside that trust store do not trigger the loop. OTP behavior was confirmed in 28.3, 29.0 and 29.1; older releases were not checked. Deploy 2.5.4. Restart nodes with persistent handshakes. If an upgrade must wait, follow the project workaround using a dedicated trust bundle with neither public roots nor roots signing device certificates, and validate registered-device connectivity before rollout. Verify that an unregistered certificate is rejected once and that its handshake process ends. Check registered-device connections, database query volume and scheduler load. Retain version, trust-store, load and rollout evidence.

Open the authoritative advisory

Last verified: 2026-11-17 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scopeNervesHub device TLS endpoint
AdvisoryGHSA-8j48-4mg5-7v6v
CVECVE-2026-125275
Authoritative release date2026-11-17T02:08:53Z — original authoritative release time in UTC.
Authority revision dateNo separate material advisory revision is confirmed.
Affected versionsNervesHub 1.0.0 through versions before 2.5.4. The default public-root exposure starts at 2.0.0; the condition requires a chain reaching a trusted root with no registered CA in that chain.
Fixed versionNervesHub 2.5.4; restart affected nodes to end already-stuck handshakes
CVSS base score8.2 (CVSS v3.1)
CVSS severityHigh
Exploitation statusThe cited authority does not confirm exploitation in the wild.; no exploitation claim is inferred.

What Changed

A rejected device certificate can trigger repeated certificate validation and database queries that continue after disconnect. Multiple connections can exhaust device-node and shared database capacity.

What To Validate Now

  1. Inventory. Record NervesHub and Erlang/OTP builds, device TLS endpoints, DEVICE_SSL_CACERTFILE configuration, trusted roots, registered CAs and device-node/database load.
  2. Establish applicability. The supplied certificate must chain to a root trusted by the device endpoint while its CA is unregistered. Arbitrary self-signed certificates outside that trust store do not trigger the loop. OTP behavior was confirmed in 28.3, 29.0 and 29.1; older releases were not checked.
  3. Remediate. Deploy 2.5.4. Restart nodes with persistent handshakes. If an upgrade must wait, follow the project workaround using a dedicated trust bundle with neither public roots nor roots signing device certificates, and validate registered-device connectivity before rollout.
  4. Validate. Verify that an unregistered certificate is rejected once and that its handshake process ends. Check registered-device connections, database query volume and scheduler load. Retain version, trust-store, load and rollout evidence.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Trust-store changes affect device connectivity and require a staged test. The advisory reports resource exhaustion observed in production but does not confirm malicious exploitation in the wild.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.