CVE-2025-68701VulnerabilityPublished 13 Jan 2026

CVE-2025-68701: samrocketman jervis · Weak Cryptography

Affects samrocketman jervisSource CVE Database V5

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

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

8.7High

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% 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:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Attack Vector: Network
Attack Complexity: Low
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: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
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 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 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

The primary and most effective mitigation is to upgrade the Jervis library to version 2.2 or later, where the deterministic IV derivation flaw is corrected. Organizations should audit their Jenkins environments to identify usage of Jervis and verify the version in use. Additionally, security teams should review all cryptographic implementations within Jenkins pipelines to ensure adherence to best practices, including the use of random, unique IVs for AES encryption and secure key management. Implementing monitoring and alerting for unusual access patterns or data exfiltration attempts related to Jenkins pipelines is advisable. Where upgrading is not immediately possible, organizations should consider isolating Jenkins environments, restricting network access, and applying compensating controls such as encrypting sensitive data at rest with external tools that use secure cryptography. Finally, educating DevOps and security teams about cryptographic hygiene and secure pipeline design will help prevent similar issues.

Description

CVE-2025-68701 is a high-severity cryptographic vulnerability in the Jervis library used for Jenkins Job DSL and shared pipeline scripts. Versions prior to 2.2 use a deterministic AES initialization vector (IV) derived from a passphrase, which weakens encryption by making ciphertext patterns predictable and susceptible to cryptanalysis. This flaw allows attackers to potentially recover sensitive data or compromise the confidentiality of encrypted information without requiring authentication or user interaction. The vulnerability has a CVSS 4.0 base score of 8.7, indicating a network-exploitable issue with high impact on confidentiality. The issue is fixed in Jervis version 2.2. European organizations relying on Jenkins automation with Jervis versions before 2.

Impact

For European organizations, this vulnerability threatens the confidentiality of sensitive data processed or stored within Jenkins pipelines that utilize the Jervis library versions prior to 2.2. Organizations in sectors such as software development, financial services, critical infrastructure, and government agencies that rely heavily on Jenkins for continuous integration and deployment could face data leakage or exposure of secrets like credentials, API keys, or proprietary code. The deterministic IV could allow attackers to decrypt or infer encrypted data, leading to intellectual property theft, compliance violations (e.g., GDPR), and erosion of trust. Since Jenkins is widely used across Europe, the risk is amplified in countries with large IT and DevOps communities. Although no active exploits are known, the ease of exploitation (no authentication or user interaction required) and network accessibility make this a pressing concern. The vulnerability does not affect integrity or availability directly but compromises confidentiality, which can have cascading effects on organizational security posture and regulatory compliance.

CWE-327Use of a Broken or Risky Cryptographic Algorithm (opens in a new tab)
Class weaknessLikelihood of exploit: HighOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses a broken or risky cryptographic algorithm or protocol.
Architecture and Design · Libraries or Frameworks
When there is a need to store or transmit sensitive data, use strong, up-to-date cryptographic algorithms to encrypt that data. Select a well-vetted algorithm that is currently considered to be strong by experts in the field, and use well-tested implementations.
Architecture and Design
Ensure that the design allows one cryptographic algorithm to be replaced with another in the next generation or version. Where possible, use wrappers to make the interfaces uniform. This will make it easier to upgrade to stronger algorithms.
Architecture and Design
Carefully manage and protect cryptographic keys (see CWE-320). If the keys can be guessed or stolen, then the strength of the cryptography itself is irrelevant.
OWASP Cheat Sheets
Cryptographic Storage (opens in a new tab)
Key Management (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)
OWASP ASVS 4.0.3
V8.3.7 (opens in a new tab)
V2.9.3 (opens in a new tab)
V6.2.2 (opens in a new tab)
Attack patterns
Encryption Brute Forcing (opens in a new tab)
Creating a Rogue Certification Authority Certificate (opens in a new tab)
Signature Spoof (opens in a new tab)
Signature Spoofing by Improper Validation (opens in a new tab)
Cryptanalysis of Cellular Encryption (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-340Generation of Predictable Numbers or Identifiers (opens in a new tab)
Class weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product uses a scheme that generates numbers or identifiers that are more predictable than required.
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 21 Jan 2026, 02:58 UTC

WeaknessesCWE-327, CWE-340

Technical details

References

Community reviews

Related threats