OpenSSL
CVE-2026-25726
CRITICAL
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain admin account creation time via public API
-
DeliveryNarrow PRNG seed search window using timestamp
-
ExploitBrute-force weak math/rand generator seed
-
ExecutionDerive secret_key and hash_id_salt
-
PersistForge authentication tokens
-
ImpactGain unauthorized admin access
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V11 - Cryptography Cryptographic PRNG selection
|
| Exploitation Conditions | Cloudreve instances first deployed with versions prior to V4.10.0. Attacker obtains administrator account creation time via public API endpoints to narrow PRNG seed search window, then derives weak security secrets (secret_key, hash_id_salt) to compromise authentication. Remote unauthenticated exploitation. |
| Impact | This vulnerability presents elevated risk despite high attack complexity (AC:H in CVSS vector). The attack is network-accessible (AV:N) and requires no authentication (PR:N) or user interaction (UI:N), enabling remote exploitation against any exposed Cloudreve instance. However, successful exploitation demands: (1) obtaining administrator creation timestamps through public API reconnaissance, (2) computational resources for multi-hour brute-forcing, and (3) access to known hashid values for seed validation. No public exploit code exists and CISA KEV does not list this CVE, indicating no confirmed active exploitation. The impact upon successful exploitation is severe-complete authentication bypass granting full administrative access (C:H/I:H/A:H), enabling data theft, modification, and service disruption. Real-world risk is moderate: while technically exploitable, the 3-hour computational requirement and multi-step attack chain reduce likelihood compared to simple remote code execution. Organizations running Cloudreve instances deployed before v4.10.0 should prioritize patching, as the attack complexity decreases over time with more powerful hardware and refined techniques. The persistence of weak secrets across upgrades creates a long-tail vulnerability affecting older deployments even if current versions are installed. |
| Exploit ScenarioDerived | An attacker identifies a publicly accessible Cloudreve instance and queries unauthenticated API endpoints to retrieve the administrator account creation timestamp, narrowing the PRNG seed search space to a specific timeframe. Using publicly observable hashid values from the application, the attacker runs a brute-force script on consumer-grade hardware (demonstrated to complete in under 3 hours) to test candidate seeds generated from timestamps around the creation window until finding one that reproduces the known hashids. With the recovered seed, the attacker regenerates the secret_key, forges a valid JWT for the administrator account, and authenticates to the Cloudreve instance with full administrative privileges, enabling data exfiltration, modification of stored files, creation of backdoor accounts, and complete takeover of the cloud storage system. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 31, 2026
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. No public exploit confirmed at time of analysis, though detailed attack methodology is disclosed. CVSS 8.1 (High) reflects network-accessible privilege escalation despite high attack complexity requiring cryptographic brute-forcing.
RemediationAI
Upgrade immediately to Cloudreve version 4.13.0, which includes automatic migration to regenerate the secret_key using cryptographically secure crypto/rand and invalidate legacy weak secrets. Download the patched release from https://github.com/cloudreve/cloudreve/releases/tag/4.13.0. For environments where immediate upgrade is not feasible, manually rotate secrets as a temporary mitigation: stop the Cloudreve service, access the database to locate the secret_key setting, replace its value with a cryptographically strong random string (generate via openssl rand -base64 64 or equivalent), and restart the service. Note that manual rotation will terminate all active user sessions. Organizations must address this on any instance ever initialized with pre-4.10.0 versions regardless of subsequent upgrades, as vulnerable secrets persist until explicitly regenerated. Complete advisory details at https://github.com/cloudreve/cloudreve/security/advisories/GHSA-f8xp-wvcx-p6f4.
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 3 packages in go
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Cloudreve is a self-hosted cloud storage system written in Go. The vulnerability stems from using Go's math/rand package seeded with time.Now().UnixNano() (a predictable timestamp) instead of crypto/rand for generating security-critical secrets during initial deployment. Specifically, the secret_key used for JWT signing and hash_id_salt are derived from this weak PRNG. This violates CWE-338 (Use of Cryptographically Weak Pseudo-Random Number Generator). The math/rand package is explicitly documented as unsuitable for security purposes. The seed space is constrained by the administrator account creation timestamp (publicly accessible via API), reducing brute-force complexity from theoretical billions of nanoseconds to a practical 3-hour window. Once the seed is recovered by validating against known hashids, attackers can regenerate the secret_key and craft arbitrary JWTs, bypassing authentication entirely. The vulnerable code persists across upgrades because secrets are database-persisted from initial deployment, meaning servers upgraded from pre-4.10.0 remain exploitable until secrets are manually rotated.
Know when OpenSSL gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Primary rating from NVD.
CVSS VectorNVD
Lifecycle Timeline
4DescriptionNVD
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:
- Invalidate the existing
secret_key. - Regenerate a new, cryptographically secure
secret_keyusing 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:
- Stop the Cloudreve service.
- In Cloudreve database, locate
secret_keysetting. - Replace the value with a long, random string (e.g., generated via
openssl rand -base64 64). - 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)
Executive ViewAI
Cloudreve instances running before version 4.10.0 contain a critical JWT generation flaw that enables attackers to forge authentication tokens and assume control of any user account, including administrative accounts, through cryptographic brute-forcing of the PRNG seed. This vulnerability directly threatens all Cloudreve deployments in this version range, potentially exposing sensitive file storage, user data, and administrative access without requiring any credentials or user interaction.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Restrict external network access to Cloudreve instances using firewall rules, VPN requirements, or reverse proxy authentication; (2) Disable or restrict public API endpoints that expose user creation timestamps; (3) Implement continuous monitoring for suspicious JWT usage patterns and administrative session activity; (4) Maintain offline backups of critical data stored in affected instances; (5) Prepare expedited upgrade plan to 4.10.0 as immediate priority when resource-constrained.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Affected Products (CPE)NVD
The (1) TLS and (2) DTLS implementations in OpenSSL 1.0.1 before 1.0.1g do not properly handle Heartbeat Extension packe
In order to decrypt SM2 encrypted data an application is expected to call the API function EVP_PKEY_decrypt(). Rated cri
The dtls1_reassemble_fragment function in d1_both.c in OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0
OpenSSL before 0.9.8za, 1.0.0 before 1.0.0m, and 1.0.1 before 1.0.1h does not properly restrict processing of ChangeCiph
The SSLv2 protocol, as used in OpenSSL before 1.0.1s and 1.0.2 before 1.0.2g and other products, requires a server to se
The ssl3_get_key_exchange function in s3_clnt.c in OpenSSL before 0.9.8zd, 1.0.0 before 1.0.0p, and 1.0.1 before 1.0.1k
In addition to the c_rehash shell command injection identified in CVE-2022-1292, further circumstances where the c_rehas
The TLS protocol 1.2 and earlier, when a DHE_EXPORT ciphersuite is enabled on a server but not on a client, does not pro
The SSL protocol 3.0, as used in OpenSSL through 1.0.1i and other products, uses nondeterministic CBC padding, which mak
The AES-NI implementation in OpenSSL before 1.0.1t and 1.0.2 before 1.0.2h does not consider memory allocation during a
The X509_verify_cert function in crypto/x509/x509_vfy.c in OpenSSL 1.0.1n, 1.0.1o, 1.0.2b, and 1.0.2c does not properly
A buffer overrun can be triggered in X.509 certificate verification, specifically in name constraint checking. Rated hig
Same technique Privilege Escalation
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Linux Enterprise Server 16.1 | Affected |
| SUSE Linux Enterprise Server for SAP applications 16.1 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP5 | Affected |
| SUSE Linux Enterprise Module for Package Hub 15 SP6 | Affected |
| openSUSE Leap 15.5 | Affected |
| openSUSE Leap 15.6 | Affected |
GHSA-f8xp-wvcx-p6f4
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB