CVE-2026-125275 json
A device certificate whose CA isn't registered can keep a TLS handshake running forever
published 2d ago modified 3h ago also EUVD-2026-126831 , GHSA-8j48-4mg5-7v6v
Unreviewed: the maintainers' own advisory
Published by the maintainers on their GitHub repository nerves-hub/nerves_hub_web. GitHub has not reviewed it into the GitHub Advisory Database, so the affected packages and versions are the maintainers' word. Read the full advisory on GitHub.
- cvss
- 8.2
- version 4.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 33%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- nerves-hub nerves_hub_web 2.5.4
Is CVE-2026-125275 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- yesterday
Exploit prediction
0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-18).
Exploits and checks
- github.com https://github.com/nerves-hub/nerves_hub_web/security/advisories/GHSA-8j48-4mg5-7v6v referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 8.2 | CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N |
Affected products
- nerves-hub nerves_hub_web
Classification
- Weakness
-
- CWE-835 Loop with Unreachable Exit Condition
References
-
github.com
/nerves-hub/nerves_hub_web/commit/a49fb8875f3aab40062881028ef4e406d985aaa9
related
-
github.com
/nerves-hub/nerves_hub_web/commit/064e78cc189dd9b87748746f44179632a52ddf58
patch
-
github.com
/nerves-hub/nerves_hub_web/security/advisories/GHSA-8j48-4mg5-7v6v
vendor-advisory, related, exploit, advisory
-
cna.erlef.org
/cves/CVE-2026-125275.html
related
-
osv.dev
/vulnerability/EEF-CVE-2026-125275
related
Sources
- CVE List CVE-2026-125275
- NVD CVE-2026-125275
- Maintainer advisory GHSA-8j48-4mg5-7v6v
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
The maintainers of nerves-hub/nerves_hub_web published their own advisory on GitHub. Reviewed sources take precedence over it.