CVE-2026-74901: Improper Verification of Cryptographic Signature in jahlives openssl_encrypt
openssl_encrypt versions before 1.4.0 contain an authentication bypass vulnerability in pqc.py where AES-GCM decryption failures trigger fallback to unauthenticated AES-CTR mode. Attackers can modify ciphertext in transit to bypass integrity verification and perform bit-flipping attacks without detection.
AI Analysis
Technical Summary
The vulnerability in jahlives openssl_encrypt prior to version 1.4.0 involves improper verification of cryptographic signatures during AES-GCM decryption. When decryption fails, the code falls back to AES-CTR mode without authentication, allowing attackers to alter ciphertext and bypass integrity checks. This can lead to bit-flipping attacks that compromise data integrity without detection. The CVSS 4.0 score is 9.3, indicating a critical severity with network attack vector, low complexity, no privileges or user interaction required, and high impacts on confidentiality, integrity, and availability.
Potential Impact
Attackers can modify encrypted data in transit without detection due to the fallback to unauthenticated AES-CTR mode, resulting in a complete bypass of integrity verification. This compromises the confidentiality and integrity of the encrypted data, potentially allowing unauthorized data manipulation.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround is currently documented. Users should monitor the vendor's announcements for patches addressing this vulnerability.
CVE-2026-74901: Improper Verification of Cryptographic Signature in jahlives openssl_encrypt
Description
openssl_encrypt versions before 1.4.0 contain an authentication bypass vulnerability in pqc.py where AES-GCM decryption failures trigger fallback to unauthenticated AES-CTR mode. Attackers can modify ciphertext in transit to bypass integrity verification and perform bit-flipping attacks without detection.
CVSS v4.0
Score 9.3critical
Affected software
jahlives
openssl_encrypt
pkg:github/jahlives/openssl_encryptRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in jahlives openssl_encrypt prior to version 1.4.0 involves improper verification of cryptographic signatures during AES-GCM decryption. When decryption fails, the code falls back to AES-CTR mode without authentication, allowing attackers to alter ciphertext and bypass integrity checks. This can lead to bit-flipping attacks that compromise data integrity without detection. The CVSS 4.0 score is 9.3, indicating a critical severity with network attack vector, low complexity, no privileges or user interaction required, and high impacts on confidentiality, integrity, and availability.
Potential Impact
Attackers can modify encrypted data in transit without detection due to the fallback to unauthenticated AES-CTR mode, resulting in a complete bypass of integrity verification. This compromises the confidentiality and integrity of the encrypted data, potentially allowing unauthorized data manipulation.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround is currently documented. Users should monitor the vendor's announcements for patches addressing this vulnerability.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- VulnCheck
- Date Reserved
- 2026-08-17T10:48:45.738Z
- Cvss Version
- 4.0
- State
- PUBLISHED
Threat ID: 6a82f006bf8831d539c483f2
Added to database: 08/17/2026, 11:27:02 UTC
Last enriched: 08/24/2026, 13:27:26 UTC
Last updated: 10/01/2026, 15:31:50 UTC
Views: 79
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.