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

Critical 9.5 Published Updated

Attackers can brute-force predictable API tokens to gain unauthorized access to user accounts and manage firmware updates.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
None listed

What is CVE-2025-64097?

CVE-2025-64097 is a critical authentication bypass vulnerability in nerves-hub nerves_hub_web, published on 22 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official 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.

Weakness: CWE-330

Which versions are affected by CVE-2025-64097?

It affects 1 product.

Products include Nerves-Hub Nerveshub.

How do I fix CVE-2025-64097?

No fix has been published for CVE-2025-64097 yet. Limit exposure of the affected software until one is available.

Upgrade, and rotate credentials and sessions that may have been exposed. More about Authentication bypass.

Is CVE-2025-64097 being exploited?

There is no known exploitation of CVE-2025-64097 in the wild and no public exploit code.

Sources

Also known as GHSA-m9vj-776q-vc8m.

Is CVE-2025-64097 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free