CVE-2026-13758: CWE-208 Observable Timing Discrepancy in MIK CryptX
CryptX versions before 0.088_001 for Perl compare AEAD authentication tags in non-constant time in the streaming decrypt_done path. The decrypt_done($tag) form compares it against the computed tag with memNE (memcmp() != 0), which short-circuits on the first differing byte, so its run time depends on the number of matching leading bytes. This affects all five AEAD modes: GCM, CCM, ChaCha20Poly1305, EAX and OCB. The one-shot *_decrypt_verify helpers are unaffected; they verify the tag inside libtomcrypt with a constant-time comparison. The timing difference is a tag-verification oracle. An attacker who can submit many candidate tags for the same nonce, ciphertext and associated data while measuring the timing precisely enough may recover the expected tag byte by byte and forge a message that verifies.
AI Analysis
Technical Summary
CryptX versions prior to 0.088_001 for Perl perform tag verification in the streaming decrypt_done path using a memNE (memcmp() != 0) comparison that short-circuits on the first differing byte, resulting in timing discrepancies. This timing side-channel affects all five AEAD modes supported by CryptX (GCM, CCM, ChaCha20Poly1305, EAX, and OCB). An attacker able to submit multiple candidate tags for the same nonce, ciphertext, and associated data, and measure the timing precisely, can exploit this to recover the correct authentication tag byte-by-byte, enabling forgery of authenticated messages. The vulnerability does not affect the one-shot *_decrypt_verify helpers, which perform constant-time tag verification inside libtomcrypt. No vendor advisory or patch information is currently available.
Potential Impact
The vulnerability enables a tag-verification oracle via timing side-channels in the streaming decrypt_done function, potentially allowing an attacker to forge authenticated messages by recovering the expected authentication tag byte-by-byte. This compromises the integrity guarantees of AEAD encryption modes in affected CryptX versions. The one-shot verification functions remain secure. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid using the streaming decrypt_done($tag) function for AEAD tag verification in CryptX versions before 0.088_001. Prefer using the one-shot *_decrypt_verify helpers which perform constant-time verification. Monitor vendor channels for updates and patches.
CVE-2026-13758: CWE-208 Observable Timing Discrepancy in MIK CryptX
Description
CryptX versions before 0.088_001 for Perl compare AEAD authentication tags in non-constant time in the streaming decrypt_done path. The decrypt_done($tag) form compares it against the computed tag with memNE (memcmp() != 0), which short-circuits on the first differing byte, so its run time depends on the number of matching leading bytes. This affects all five AEAD modes: GCM, CCM, ChaCha20Poly1305, EAX and OCB. The one-shot *_decrypt_verify helpers are unaffected; they verify the tag inside libtomcrypt with a constant-time comparison. The timing difference is a tag-verification oracle. An attacker who can submit many candidate tags for the same nonce, ciphertext and associated data while measuring the timing precisely enough may recover the expected tag byte by byte and forge a message that verifies.
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CryptX versions prior to 0.088_001 for Perl perform tag verification in the streaming decrypt_done path using a memNE (memcmp() != 0) comparison that short-circuits on the first differing byte, resulting in timing discrepancies. This timing side-channel affects all five AEAD modes supported by CryptX (GCM, CCM, ChaCha20Poly1305, EAX, and OCB). An attacker able to submit multiple candidate tags for the same nonce, ciphertext, and associated data, and measure the timing precisely, can exploit this to recover the correct authentication tag byte-by-byte, enabling forgery of authenticated messages. The vulnerability does not affect the one-shot *_decrypt_verify helpers, which perform constant-time tag verification inside libtomcrypt. No vendor advisory or patch information is currently available.
Potential Impact
The vulnerability enables a tag-verification oracle via timing side-channels in the streaming decrypt_done function, potentially allowing an attacker to forge authenticated messages by recovering the expected authentication tag byte-by-byte. This compromises the integrity guarantees of AEAD encryption modes in affected CryptX versions. The one-shot verification functions remain secure. No known exploits in the wild have been reported.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, avoid using the streaming decrypt_done($tag) function for AEAD tag verification in CryptX versions before 0.088_001. Prefer using the one-shot *_decrypt_verify helpers which perform constant-time verification. Monitor vendor channels for updates and patches.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CPANSec
- Date Reserved
- 2026-06-29T17:50:18.724Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a42de5d27e9c79719807156
Added to database: 06/29/2026, 21:06:37 UTC
Last enriched: 06/29/2026, 21:22:12 UTC
Last updated: 06/29/2026, 22:51:45 UTC
Views: 5
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.