Ciphertext manipulation via unauthenticated AES-CBC
Published Jan 13, 2026 · Updated Jan 13, 2026
Cryptographic integrity failure in Sam Gleske Jervis before 2.2 allows remote attackers to manipulate encrypted data. SecurityIO uses AES/CBC/PKCS5Padding without authenticating ciphertext, allowing modified blocks to reach padding processing. Exploitation requires a consumer to expose these methods to attacker-controlled ciphertext; Jervis itself verifies a SHA-256 checksum over local-only token storage before decryption.
Summary
What happened
Cryptographic integrity failure in Sam Gleske Jervis before 2.2 allows remote attackers to manipulate encrypted data. SecurityIO uses AES/CBC/PKCS5Padding without authenticating ciphertext, allowing modified blocks to reach padding processing. Exploitation requires a consumer to expose these methods to attacker-controlled ciphertext; Jervis itself verifies a SHA-256 checksum over local-only token storage before decryption.
The record
- CVE
- CVE-2025-68931
- Published
- Jan 13, 2026
- Updated
- Jan 13, 2026
- Vendor
- Sam Gleske
- Product
- Jervis
- Classifications
- CWE-327, CWE-287, T1565
- 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