Integrity-check failures via truncated leading-zero SHA-256 digests
Published Jan 13, 2026 · Updated Jan 13, 2026
Cryptographic hash generation in Jervis before 2.2 allows remote attackers to cause integrity-check failures via crafted inputs. SecurityIO.sha256Sum converts the 32-byte digest through BigInteger and pads the result to only 32 rather than 64 hexadecimal characters, dropping required leading zeros. The issue affects consumers that call this method directly and rely on fixed-length hash strings, causing comparisons involving leading-zero digests to fail.
Summary
What happened
Cryptographic hash generation in Jervis before 2.2 allows remote attackers to cause integrity-check failures via crafted inputs. SecurityIO.sha256Sum converts the 32-byte digest through BigInteger and pads the result to only 32 rather than 64 hexadecimal characters, dropping required leading zeros. The issue affects consumers that call this method directly and rely on fixed-length hash strings, causing comparisons involving leading-zero digests to fail.
The record
- CVE
- CVE-2025-68702
- Published
- Jan 13, 2026
- Updated
- Jan 13, 2026
- Vendor
- Sam Gleske
- Product
- Jervis
- Classifications
- CWE-327
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 13, 2026CVE publishedPublication date reported by the CVE source.
- Jan 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo