Summary
Vulnerability
Uses java.util.Random() which is not cryptographically secure.
Workarounds
None
References
Impact
If an attacker can predict the random delays, they may still be able to perform timing attacks.
Security-sensitive operations rely on values that are predictable or insufficiently random. Typical impact: forged tokens, guessable identifiers, or broken cryptographic protocols.
CVE-2025-68704 has a CVSS score of 5.9 (High). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2.2); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Jervis will use SecureRandom for timing randomization.
Upgrade to Jervis 2.2.
Frequently Asked Questions
- What is CVE-2025-68704? CVE-2025-68704 is a high-severity use of insufficiently random values vulnerability in net.gleske:jervis (maven), affecting versions < 2.2. It is fixed in 2.2. Security-sensitive operations rely on values that are predictable or insufficiently random.
- How severe is CVE-2025-68704? CVE-2025-68704 has a CVSS score of 5.9 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of net.gleske:jervis are affected by CVE-2025-68704? net.gleske:jervis (maven) versions < 2.2 is affected.
- Is there a fix for CVE-2025-68704? Yes. CVE-2025-68704 is fixed in 2.2. Upgrade to this version or later.
- Is CVE-2025-68704 exploitable, and should I be worried? Whether CVE-2025-68704 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-68704 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-68704? Upgrade
net.gleske:jervisto 2.2 or later.