CVE-2025-68704
Published: 13 January 2026
Summary
CVE-2025-68704 is a high-severity Use of Insufficiently Random Values (CWE-330) vulnerability in Samrocketman Jervis. Its CVSS base score is 7.5 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 15.1th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
Threat & Defense at a Glance
Threat & Defense Details
Likely Mitigating ControlsAI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Key generation under controlled management uses approved random-bit sources rather than insufficiently random values.
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
Vulnerability enables remote exploitation of a public-facing Jenkins library component for sensitive data disclosure via flawed timing attack mitigation.
NVD Description
Jervis is a library for Job DSL plugin scripts and shared Jenkins pipeline libraries. Prior to 2.2, Jervis uses java.util.Random() which is not cryptographically secure for timing attack mitigation. This vulnerability is fixed in 2.2.
Deeper analysisAI
CVE-2025-68704 affects Jervis, a library used for Job DSL plugin scripts and shared Jenkins pipeline libraries. In versions prior to 2.2, Jervis relies on java.util.Random(), which is not cryptographically secure, for timing attack mitigation. This flaw, classified under CWE-330 (Use of Insufficiently Random Values), carries a CVSS v3.1 base score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N), indicating high confidentiality impact with no requirements for privileges or user interaction.
Remote attackers can exploit this vulnerability over the network with low complexity. By leveraging the predictable randomness from java.util.Random(), adversaries may conduct timing attacks to infer sensitive information processed or protected by Jervis in Jenkins environments, potentially disclosing confidential data without impacting integrity or availability.
The vulnerability is addressed in Jervis version 2.2, where the insecure random number generator is replaced. Security practitioners should upgrade to 2.2 or later, as detailed in the GitHub security advisory (GHSA-c9q6-g3hr-8gww) and the fixing commit (c3981ff71de7b0f767dfe7b37a2372cb2a51974a).
Details
- CWE(s)