CVE-2025-68703 — jervis
Fix: samrocketman/jervis@c3981ffCVE-2025-68703 is a CWE-326 vulnerability in net.gleske:jervis. A fix is available for net.gleske:jervis — see the affected versions and patch details below.
Jervis has a Salt for PBKDF2 derived from password
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-68703.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
net.gleske:jervisReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Vulnerability
The salt is derived from sha256Sum(passphrase). Two encryption operations with the same password will have the same derived key.
Impact
Pre-computation attacks.
Severity is considered low for internal uses of this library and high for consumers of this library.
Patches
Jervis will generate a random salt for each password and store it alongside the ciphertext.
Upgrade to Jervis 2.2.
Workarounds
None
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | net.gleske:jervis | all versions | 2.2net.gleske:jervis:2.2 |
Affected Products
jervissamrocketmanDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for net.gleske:jervis, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update net.gleske:jervis to 2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-68703 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2025-68703 in your dependencies?
Find it across Maven, including transitive dependencies.