CVE-2025-64097: nerves_hub_web · Weak Randomness
Affects nerves_hub_webSource CVE Database V5
Not known to be exploited · CVSS 9.5 Critical : upgrade to 2.3.0 as a priority.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2.3.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:HExploitation evidence
Disclosed: evidence found.
CVE published 22 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Upgrade nerves_hub_web to 2.3.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| nerves-hubnerves_hub_web | Affected
| Fixed in
|
Hexnerves_hub_webpkg:hex/nerves_hub_webOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
The primary and most effective mitigation is to upgrade all instances of nerves_hub_web to version 2.3.0 or later, where the vulnerability is fully addressed. Organizations should implement a rapid patch management process to identify and update all affected deployments. In environments where immediate upgrading is not possible, network-level controls should be applied to restrict access to the NervesHub server, limiting exposure to trusted IP addresses and internal networks only. Monitoring and logging of API token usage should be enhanced to detect anomalous access patterns indicative of brute-force or enumeration attempts. Additionally, organizations should audit their token management policies and ensure tokens are rotated regularly. Post-upgrade, verify that token storage uses hashing as per the fix to protect against database compromise. Conduct security assessments of the OTA update process to confirm no residual weaknesses remain. Finally, educate operational teams about the risks of token compromise and enforce strict access controls around the NervesHub management interfaces.
Description
NervesHub is a web service that allows users to manage over-the-air (OTA) firmware updates of devices in the field. A vulnerability present starting in version 1.0.0 and prior to version 2.3.0 allowed attackers to brute-force user API tokens due to the predictable format of previously issued tokens. Tokens included user-identifiable components and were not cryptographically secure, making them susceptible to guessing or enumeration. The vulnerability could have allowed unauthorized access to user accounts or API actions protected by these tokens. A fix is available in version 2.3.0 of NervesHub. This version introduces strong, cryptographically-random tokens using `:crypto.strong_rand_bytes/1`, hashing of tokens before database storage to prevent misuse even if the database is compromised, and context-aware token storage to distinguish between session and API tokens. There are no practical workarounds for this issue other than upgrading. In sensitive environments, as a temporary mitigation, firewalling access to the NervesHub server can help limit exposure until an upgrade is possible.