Most recent entries from all

EUVD-2026-280255

2026-10-07T15:15:55.156216+00:00

EUVD-2026-280255

fkie_cve-2026-25726

2026-10-07T15:15:55.156261+00:00

Cloudreve is a self-hosted file management and sharing system. Prior to version 4.13.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. This issue has been patched in version 4.13.0.

GHSA-f8xp-wvcx-p6f4 — Cloudreve is vulnerable to Account Takeover via Weak Cryptographic Token Generation (Insecure PRNG Seeding)

2026-10-07T15:15:55.156311+00:00

Affected: Go: github.com/cloudreve/Cloudreve/v4

### 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…