CVE-2025-62710VulnerabilityPublished 22 Oct 2025Updated 24 Oct 2025

CVE-2025-62710: sakaiproject sakai · PRNG

Affects sakaiproject sakaiSource CVE Database V5

Not known to be exploited · CVSS 5.9 Medium : upgrade to 25.0 or 23.5 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

5.9Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 25.0, 23.5

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: High
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: High: A successful attack depends on conditions beyond the attacker's control. That is, a successful attack cannot be accomplished at will, but requires the attacker to invest in some measurable amount of effort in preparation or execution against the vulnerable component before a successful attack can be expected. For example, a successful attack may require an attacker to: gather knowledge about the environment in which the vulnerable target/component exists; prepare the target environment to improve exploit reliability; or inject themselves into the logical network path between the target and the resource requested by the victim in order to read and/or modify network communications (e.g., a man in the middle attack).
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 22 Oct 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade org.sakaiproject/sakai to 25.0 or 23.5.

Affected software

Product	Affected	Fixed in
Mavenorg.sakaiproject/sakai`pkg:maven/org.sakaiproject/sakai`Other threats	Affected <23.5 <25.0	Fixed in 23.5 25.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

European organizations should immediately upgrade Sakai to versions 23.5, 25.0, or later where the vulnerability is patched. If upgrading is not immediately feasible, organizations should restrict access to encrypted data exports and backups to minimize ciphertext exposure. Implement network segmentation and strict access controls around Sakai servers and storage to reduce the risk of unauthorized data access. Conduct audits to identify any exported or at-rest encrypted data protected by the vulnerable EncryptionUtilityServiceImpl and consider re-encrypting this data after patching. Additionally, monitor for unusual access patterns or attempts to obtain ciphertexts. Educate administrators about the risks of using non-cryptographically secure PRNGs for key generation and encourage the adoption of secure cryptographic libraries and best practices. Finally, integrate this vulnerability into incident response plans to ensure rapid action if exploitation is suspected.

Description

Sakai is a Collaboration and Learning Environment. Prior to versions 23.5 and 25.0, EncryptionUtilityServiceImpl initialized an AES256TextEncryptor password (serverSecretKey) using RandomStringUtils with the default java.util.Random.java.util.Random is a non‑cryptographic PRNG and can be predicted from limited state/seed information (e.g., start time window), substantially reducing the effective search space of the generated key. An attacker who can obtain ciphertexts (e.g., exported or at‑rest strings protected by this service) and approximate the PRNG seed can feasibly reconstruct the serverSecretKey and decrypt affected data. SAK-49866 is patched in Sakai 23.5, 25.0, and trunk.

Impact

For European organizations using Sakai versions prior to 23.5 or 25.0, this vulnerability poses a significant risk to the confidentiality of sensitive educational and collaboration data. Since Sakai is widely used in academic institutions and research organizations across Europe, unauthorized decryption of protected data could lead to exposure of personal information, intellectual property, and confidential communications. Although the vulnerability does not impact data integrity or availability, the breach of confidentiality could result in regulatory non-compliance under GDPR, reputational damage, and potential legal consequences. The attack requires no privileges or user interaction, increasing the risk if ciphertexts are accessible through backups, exports, or compromised storage. The high attack complexity somewhat limits exploitation but does not eliminate the threat, especially for motivated attackers with sufficient resources. Organizations relying on Sakai for critical collaboration should consider this vulnerability a priority for remediation to maintain data protection standards.

CWE-337Predictable Seed in Pseudo-Random Number Generator (PRNG) (opens in a new tab)
Variant weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
A Pseudo-Random Number Generator (PRNG) is initialized from a predictable seed, such as the process ID or system time.
Use non-predictable inputs for seed generation.
Architecture and Design · Requirements · Libraries or Frameworks
Use products or modules that conform to FIPS 140-2 to avoid obvious entropy problems, or use the more recent FIPS 140-3 if possible.
Implementation
Use a PRNG that periodically re-seeds itself using input from high-quality sources, such as hardware devices with high entropy. However, do not re-seed too frequently, or else the entropy source might block.
OWASP Cheat Sheets
Forgot Password (opens in a new tab)
Transport Layer Protection (opens in a new tab)
User Privacy Protection (opens in a new tab)
Password Storage (opens in a new tab)
Cryptographic Storage (opens in a new tab)
OWASP ASVS 4.0.3
V2.3.1 (opens in a new tab)
V2.6.2 (opens in a new tab)
V2.7.6 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 29 Oct 2025, 23:34 UTC

WeaknessesCWE-337

Technical details

References

Community reviews

Related threats