VulnerabilityPublished 13 Jan 2026

CVE-2025-68704: samrocketman jervis · Weak Randomness

Affects samrocketman jervisSource CVE Database V5

Not known to be exploited · CVSS 8.2 High : upgrade to 2.2 soon.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 4.0 base score

8.2High

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

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

CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: High
Attack Requirements: None
Privileges Required: None
User Interaction: None
Vulnerable system confidentiality: High
Vulnerable system integrity: None
Vulnerable system availability: None
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

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

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, 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: The successful attack depends on the evasion or circumvention of security-enhancing techniques in place that would otherwise hinder the attack. These include: Evasion of exploit mitigation techniques, for example, circumvention of address space randomization (ASLR) or data execution prevention (DEP) must be performed for the attack to be successful; Obtaining target-specific secrets. The attacker must gather some target-specific secret before the attack can be successful. A secret is any piece of information that cannot be obtained through any amount of reconnaissance. To obtain the secret the attacker must perform additional attacks or break otherwise secure measures (e.g. knowledge of a secret key may be needed to break a crypto channel). This operation must be performed for each attacked target.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files of the vulnerable system to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: High: There is a total loss of confidentiality, resulting in all information within the Vulnerable System being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact. For example, an attacker steals the administrator's password, or private encryption keys of a web server.
Vulnerable system integrity: None: There is no loss of integrity within the Vulnerable System.
Vulnerable system availability: None: There is no impact to availability within the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 13 Jan 2026
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 26 Oct 2026.

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 or the CVSS exploit maturity 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 jervis and samrocketman/jervis to 2.2.

Affected software

Product	Affected	Fixed in
samrocketmanjervis	Affected <2.2	Fixed in 2.2
GitHubsamrocketman/jervis`pkg:github/samrocketman/jervis`Other threats	Affected <2.2	Fixed in 2.2

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

AI-suggested

Upgrade Jervis to version 2.2 or later immediately to ensure the use of cryptographically secure random number generators.
Audit all Jenkins pipeline scripts and Job DSL plugins that depend on Jervis to identify and remediate any reliance on insecure randomness.
Implement runtime monitoring and anomaly detection for Jenkins pipelines to detect unusual timing patterns or behavior indicative of exploitation attempts.
Enforce strict access controls and network segmentation around Jenkins servers to reduce exposure to network-based attacks.
Integrate cryptographic best practices into CI/CD pipeline development, including the use of secure random functions and regular security code reviews.
Maintain up-to-date backups and incident response plans tailored to CI/CD infrastructure compromise scenarios.
Engage in threat intelligence sharing within industry groups to stay informed about emerging exploits targeting Jenkins and related tooling.

Description

CVE-2025-68704 is a high-severity vulnerability affecting versions of the Jervis library prior to 2.2. The issue stems from the use of java.util. Random(), which is not cryptographically secure, leading to insufficient randomness in critical operations. This weakness can enable timing attacks that compromise the integrity of Jenkins pipeline scripts relying on Jervis. The vulnerability does not require authentication or user interaction but has a high attack complexity, limiting exploitation ease. European organizations using Jenkins with Jervis versions below 2.2 are at risk, especially those in sectors relying heavily on CI/CD pipelines. The vulnerability has no known exploits in the wild yet, but patching to version 2.

Impact

For European organizations, the vulnerability threatens the integrity and confidentiality of automated CI/CD pipelines that use Jervis versions below 2.2. Exploitation could allow attackers to predict or manipulate random values used in pipeline scripts, potentially leading to unauthorized code execution, bypass of security checks, or injection of malicious artifacts into software builds. This undermines trust in software supply chains and could result in widespread operational disruption, data breaches, or compliance violations. Sectors such as finance, manufacturing, telecommunications, and government agencies that heavily depend on Jenkins for continuous integration and deployment are particularly at risk. The high CVSS score reflects the potential for significant damage despite the high attack complexity. The absence of known exploits suggests a window of opportunity for proactive mitigation before active exploitation occurs. Failure to address this vulnerability could expose European critical infrastructure and enterprises to advanced persistent threats targeting software development pipelines.

CWE-330Use of Insufficiently Random Values (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses insufficiently random numbers or values in a security context that depends on unpredictable numbers.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design
Use a well-vetted algorithm that is currently considered to be strong by experts in the field, and select well-tested implementations with adequate length seeds.
Implementation
Consider a PRNG that re-seeds itself as needed from high quality pseudo-random output sources, such as hardware devices.
Architecture and Design · Requirements · Libraries or Frameworks
Use products or modules that conform to FIPS 140-2 to avoid obvious entropy problems. Consult FIPS 140-2 Annex C ("Approved Random Number Generators").
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)
Attack patterns
Signature Spoofing by Key Recreation (opens in a new tab)
Session Credential Falsification through Prediction (opens in a new tab)
Brute Force (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 21 Jan 2026, 02:59 UTC

WeaknessesCWE-330

Technical details

References

Community reviews

Related threats