# CVE-2025-62710: Sakai kernel-impl: predictable PRNG used to generate server‑side encryption key in EncryptionUtilityServiceImpl

> Attackers can predict server encryption keys due to weak PRNG usage, allowing decryption of protected data in Sakai LMS.

- **Severity:** Medium 5.9 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 Oct 2025
- **Updated:** 24 Oct 2025
- **Also known as:** GHSA-gr7h-xw4f-wh86

## What is CVE-2025-62710?

CVE-2025-62710 is a medium-severity vulnerability in sakaiproject sakai, published on 22 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-337 (Predictable Seed in Pseudo-Random Number Generator (PRNG))

## Which versions are affected by CVE-2025-62710?

2 open source packages ship an affected version, including org.sakaiproject.kernel:sakai-kernel-impl. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.sakaiproject.kernel:sakai-kernel-impl` | Maven | All versions to 23.3 | None |
| `org.sakaiproject.kernel:sakai-kernel-impl` | Maven | All versions to 23.3 | None |

Products: Sakailms Sakai.

## How do I fix CVE-2025-62710?

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

## Is CVE-2025-62710 being exploited?

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

## Other vulnerabilities in sakaiproject sakai

- [CVE-2024-47876](https://insights.sbomify.com/CVE-2024-47876/): Sakai: Kernel users created with type roleview can login as a normal user (high 8.7)
- [CVE-2019-16148](https://insights.sbomify.com/CVE-2019-16148/): Cross-site scripting in Sakai (medium 6.1)
- [CVE-2026-33402](https://insights.sbomify.com/CVE-2026-33402/): SAK-52311: Sakai site-manage group titles can contain XSS content (low 1.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-62710 and fix it if it is affected.

What it is: CVE-2025-62710 is a medium-severity vulnerability in sakaiproject sakai, published on 22 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-62710 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.sakaiproject.kernel:sakai-kernel-impl (Maven): affected all versions up to 23.3; no fix listed
- org.sakaiproject.kernel:sakai-kernel-impl (Maven): affected all versions up to 23.3; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-62710/ (Markdown: https://insights.sbomify.com/CVE-2025-62710/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-62710
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-62710
- OSV: https://osv.dev/vulnerability/CVE-2025-62710

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-62710/
Summaries are generated and may contain mistakes; the official description above is the record.