Skip to content
Connect AISign inSign up free
CVE-2025-640979.5CriticalCWE-330

CVE-2025-64097: NervesHub has Insufficient Token Entropy that Allows Authentication Bypass via Brute Force

nerves-hub · nerves_hub_web

Affected: nerves-hub nerves_hub_web · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.5%probability of exploitation in the next 30 days
41st percentile
050100

Higher than 41% of scored CVEs

9.5CriticalCVSS 4.0
LowCrit.

DescriptionCVE.org

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.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • nerves-hub · nerves_hub_web>= 1.0.0, < 2.3.0

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Published
January 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2025-64097 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References