CVE-2025-68925VulnerabilityPublished 13 Jan 2026

CVE-2025-68925: samrocketman jervis · Improper Verification of Cryptographic Signature

Affects samrocketman jervisSource CVE Database V5

Not known to be exploited · CVSS 6.9 Medium : upgrade to 2.2 when convenient.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

6.9Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 4% 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:N/VI:L/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: None
Vulnerable system integrity: Low
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: None: There is no loss of confidentiality within the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to 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

European organizations should take the following specific mitigation steps: 1) Immediately upgrade the samrocketman jervis library to version 2.2 or later, where the vulnerability is fixed. 2) Audit all Jenkins instances to identify usage of vulnerable jervis versions, including shared pipeline libraries and Job DSL scripts. 3) Implement strict validation of JWT tokens in Jenkins pipelines, ensuring that only tokens with the expected "alg":"RS256" header are accepted. 4) Restrict access to Jenkins pipeline configuration and script repositories to trusted personnel only, minimizing the risk of malicious token injection. 5) Monitor Jenkins logs for suspicious JWT usage or failed signature validations that could indicate exploitation attempts. 6) Employ network segmentation and firewall rules to limit exposure of Jenkins servers to untrusted networks. 7) Integrate security scanning tools into CI/CD pipelines to detect unauthorized changes or malicious code injections early. 8) Educate DevOps and security teams about the risks of improper cryptographic validation and best practices for secure pipeline management. These targeted actions go beyond generic advice by focusing on the specific vulnerability mechanics and the Jenkins environment context.

Description

CVE-2025-68925 is a medium severity vulnerability in the samrocketman jervis library used for Job DSL plugin scripts and Jenkins pipeline libraries. Versions prior to 2.2 do not properly verify that the JWT header specifies the expected cryptographic algorithm "alg":"RS256". This improper verification (CWE-347) can allow attackers to bypass signature validation, potentially enabling unauthorized code execution or pipeline manipulation. The vulnerability is remotely exploitable without authentication or user interaction, with a CVSS score of 6.9. It affects Jenkins environments using vulnerable jervis versions, which are common in CI/CD pipelines. The flaw is fixed in version 2.2. European organizations relying on Jenkins automation and shared pipeline libraries should prioritize upgrading to mitigate risk.

Impact

For European organizations, the impact of CVE-2025-68925 can be significant, especially those heavily reliant on Jenkins for continuous integration and continuous deployment (CI/CD) pipelines. Exploitation could allow attackers to bypass signature verification on JWTs, leading to unauthorized execution of pipeline scripts or injection of malicious code into build processes. This compromises the integrity of software development workflows, potentially introducing backdoors or vulnerabilities into production software. Confidentiality may also be affected if sensitive pipeline configurations or credentials are exposed or manipulated. The availability of CI/CD pipelines could be disrupted if malicious actors alter or disable automated jobs. Given the vulnerability requires no authentication or user interaction, attackers can remotely exploit it, increasing the risk of widespread attacks. The absence of known exploits in the wild currently reduces immediate risk, but the medium severity score and ease of exploitation necessitate urgent mitigation. European organizations in sectors such as finance, manufacturing, and technology, which depend on secure and reliable software delivery, are particularly at risk. Failure to address this vulnerability could lead to intellectual property theft, regulatory non-compliance, and reputational damage.

CWE-347Improper Verification of Cryptographic Signature (opens in a new tab)
Base weaknessOWASP Top 10 A04:2025: Cryptographic Failures (opens in a new tab)
The product does not verify, or incorrectly verifies, the cryptographic signature for data.
OWASP Cheat Sheets
XML Security (opens in a new tab)
REST Security (opens in a new tab)
JSON Web Token for Java (opens in a new tab)
REST Assessment (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.3.2 (opens in a new tab)
V3.5.3 (opens in a new tab)
V13.2.6 (opens in a new tab)
Attack patterns
Padding Oracle Crypto Attack (opens in a new tab)
Signature Spoofing by Improper Validation (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-347

Technical details

References

Community reviews

Related threats