CVE-2026-25726

HIGH
2026-03-31 https://github.com/cloudreve/cloudreve GHSA-f8xp-wvcx-p6f4
8.1
CVSS 3.1
Share

CVSS Vector

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

3
Patch Released
Apr 01, 2026 - 02:30 nvd
Patch available
Analysis Generated
Mar 31, 2026 - 22:32 vuln.today
CVE Published
Mar 31, 2026 - 22:31 nvd
HIGH 8.1

Description

### Impact This vulnerability affects **Cloudreve** instances that were **first deployed/initialized** with versions prior to V4.10.0. The application uses the weak pseudo-random number generator `math/rand` seeded with `time.Now().UnixNano()` to generate critical security secrets, including the `secret_key`, and `hash_id_salt`. These secrets are generated upon first startup and persisted in the database. An attacker can exploit this by obtaining the administrator's account creation time (via public API endpoints) to narrow the search window for the PRNG seed, and use known hashid to validate the seed. By brute-forcing the seed (demonstrated to take <3 hours on general consumer PC), an attacker can predict the `secret_key`. This allows them to forge valid JSON Web Tokens (JWTs) for any user, including administrators, leading to full account takeover and privilege escalation. **Note**: Servers running V4.10.0+ are still vulnerable if they were originally installed using an older version, as the weak secrets persist in the configuration. ### Patches The issue has been addressed in version 4.13.0. This patch introduces a migration mechanism that automatically: 1. Invalidate the existing `secret_key`. 2. Regenerate a new, cryptographically secure `secret_key` using crypto/rand. Users should upgrade to 4.13.0 immediately. ### Workarounds If an immediate upgrade is not possible, administrators must manually rotate the critical secrets in the configuration file to invalidate potential exploits: 1. Stop the Cloudreve service. 2. In Cloudreve database, locate `secret_key` setting. 3. Replace the value with a long, random string (e.g., generated via `openssl rand -base64 64`). 4. Restart the Cloudreve service. _Note: This will log out all currently active users._ ### Resources * Vulnerable Code (Seeding): https://github.com/cloudreve/cloudreve/blob/87d48ac4a7acbc68064c2b9cb23793ac97f4392d/pkg/util/common.go#L21C1-L23C2 * Vulnerable Code (Usage): https://github.com/cloudreve/cloudreve/blob/87d48ac4a7acbc68064c2b9cb23793ac97f4392d/inventory/setting.go#L591 * [Go Documentation (math/rand)](https://pkg.go.dev/math/rand)

Analysis

Weak pseudo-random number generation in Cloudreve enables JWT forgery and complete account takeover on instances initialized before v4.10.0. Attackers can brute-force the PRNG seed (achievable in under 3 hours on consumer hardware) by obtaining administrator creation timestamps via public APIs and validating against known hashids, then forge valid JWTs for any user including administrators. …

Sign in for full analysis, threat intelligence, and remediation guidance.

Remediation

Within 24 hours: Identify all Cloudreve instances in your environment and determine current version (check /admin or package metadata for version < 4.10.0). Within 7 days: Isolate affected instances from external network access or restrict API endpoints that expose administrator creation timestamps; implement network-level authentication (VPN/IP whitelist) for all Cloudreve access. …

Sign in for detailed remediation steps.

Priority Score

41
Low Medium High Critical
KEV: 0
EPSS: +0.0
CVSS: +40
POC: 0

Share

CVE-2026-25726 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy