CVE-2025-68701: Jervis Package Suffers from Deterministic AES IV Derivation Vulnerability

net.gleske:jervis Updated 14 Jan 2026

Summary

13/01/2026
Yes i
High
8.7

CVE-2025-68701: Jervis has Deterministic AES IV Derivation from Passphrase. Affects net.gleske:jervis versions < 2.2. Fixed in 2.2. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Jervis is an open-source automation tool designed to facilitate continuous integration and deployment processes. It leverages various technologies to streamline workflows and enhance productivity. However, it has been identified to have a security flaw related to its encryption mechanism, specifically concerning the deterministic generation of Initialization Vectors (IVs) when encrypting data with a passphrase.

Vulnerability Detail

The vulnerability arises from the deterministic nature of the AES IV derivation in the Jervis package. When the same passphrase is used with the same plaintext, it results in the same ciphertext due to IV reuse. This predictability significantly reduces the security of the encryption scheme, making it susceptible to pattern analysis and potential decryption by unauthorized parties. The impact is considered high for consumers directly using these methods, despite being classified as low for internal uses.

How To Fix

Latest published version: 2.4 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

There are no effective workarounds available for this vulnerability. The best course of action is to upgrade to the patched version of Jervis.

Conclusion

The Jervis package has a significant vulnerability related to deterministic AES IV derivation, which can lead to severe security risks. Users are strongly advised to upgrade to version 2.2 or later to ensure the integrity of their encryption processes. Regular monitoring for vulnerabilities using tools like Vulert can further enhance security.

See every vulnerability recorded for net.gleske:jervis →

Share this vulnerability

FAQ

The vulnerability is related to deterministic AES IV derivation, leading to predictable ciphertext when the same passphrase and plaintext are used.

If your application uses Jervis for encryption, it may be at risk of data exposure due to the predictability of the encryption scheme.

The CVSS score for this vulnerability is 8.7, indicating a high level of severity, particularly for applications directly utilizing the affected methods.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground without any signup.

While there are no workarounds, it is crucial to plan for an upgrade to mitigate the risk associated with this vulnerability.

Related vulnerabilities

Recent vulnerabilities recorded for net.gleske:jervis.

How To Fix

Latest published version: 2.4 as of 22 Oct 2026

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

2.2

This is the first release that contains the fix.

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback