# CVE-2025-68701: Jervis has Deterministic AES IV Derivation from Passphrase

> Jenkins pipeline library uses deterministic AES IVs, potentially allowing attackers to decrypt sensitive data.

- **Severity:** High 8.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 13 Jan 2026
- **Updated:** 13 Jan 2026
- **Also known as:** GHSA-crxp-chh4-9ghp

## What is CVE-2025-68701?

CVE-2025-68701 is a high-severity vulnerability in samrocketman jervis, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Jervis is a library for Job DSL plugin scripts and shared Jenkins pipeline libraries. Prior to 2.2, Jervis uses deterministic AES IV derivation from a passphrase. This vulnerability is fixed in 2.2.

Weakness: CWE-340 (Generation of Predictable Numbers or Identifiers), CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

## Which versions are affected by CVE-2025-68701?

2 open source packages ship an affected version, including net.gleske:jervis. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `net.gleske:jervis` | Maven | All versions | 2.2 |
| `net.gleske:jervis` | Maven | All versions | 2.2 |

Products: Samrocketman Jervis.

## How do I fix CVE-2025-68701?

Upgrade net.gleske:jervis to 2.2 or later.

## Is CVE-2025-68701 being exploited?

There is no known exploitation of CVE-2025-68701 in the wild and no public exploit code.

## Other vulnerabilities in samrocketman jervis

- [CVE-2025-68698](https://insights.sbomify.com/CVE-2025-68698/): Jervis has an RSA PKCS#1 v1.5 Padding Vulnerability (high 8.7)
- [CVE-2025-68702](https://insights.sbomify.com/CVE-2025-68702/): Jervis has a SHA-256 Hex String Padding Bug (high 8.7)
- [CVE-2025-68703](https://insights.sbomify.com/CVE-2025-68703/): Jervis has a Salt for PBKDF2 derived from password (high 8.7)
- [CVE-2025-68931](https://insights.sbomify.com/CVE-2025-68931/): Jervis has AES CBC Mode Without Authentication (high 8.7)
- [CVE-2025-68704](https://insights.sbomify.com/CVE-2025-68704/): Jervis has a Weak Random for Timing Attack Mitigation (high 8.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-68701 and fix it if it is affected.

What it is: CVE-2025-68701 is a high-severity vulnerability in samrocketman jervis, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-68701 in the wild and no public exploit code.

Affected packages and fixed versions:
- net.gleske:jervis (Maven): affected all versions; fixed in 2.2
- net.gleske:jervis (Maven): affected all versions; fixed in 2.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-68701/ (Markdown: https://insights.sbomify.com/CVE-2025-68701/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-68701
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-68701
- OSV: https://osv.dev/vulnerability/CVE-2025-68701

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-68701/
Summaries are generated and may contain mistakes; the official description above is the record.