CVE-2026-41244: CWE-208: Observable Timing Discrepancy in notamitgamer mojic
CVE-2026-41244 is a timing discrepancy vulnerability in the notamitgamer mojic CLI tool versions prior to 2. 1. 4. The issue arises because the CipherEngine uses a standard equality operator (! ==) to verify the HMAC-SHA256 integrity seal during decryption, which creates an observable timing difference. This timing discrepancy (CWE-208) could allow an attacker to bypass the file integrity check via a timing attack. The vulnerability has a medium severity with a CVSS score of 4. 7 and is fixed in version 2. 1. 4.
AI Analysis
Technical Summary
The vulnerability in mojic (a CLI tool that transforms C code into emoji streams) exists because the CipherEngine compares the HMAC-SHA256 integrity seal using a standard equality operator (!==) instead of a constant-time comparison. This leads to an observable timing discrepancy (CWE-208) during the decryption phase, potentially enabling an attacker to bypass integrity verification by measuring response times. Versions prior to 2.1.4 are affected. The issue is resolved in version 2.1.4.
Potential Impact
An attacker with local access could exploit the timing discrepancy to bypass the file integrity check, potentially allowing tampered or maliciously altered files to be accepted as valid. There is no impact on confidentiality or availability reported. The medium CVSS score reflects the integrity impact with limited attack vector (local) and high attack complexity.
Mitigation Recommendations
Upgrade mojic to version 2.1.4 or later, where the vulnerability is fixed by using a proper constant-time comparison for the HMAC-SHA256 integrity check. Since the vendor advisory confirms the fix in 2.1.4, applying this update fully mitigates the issue. No other mitigations are specifically indicated.
CVE-2026-41244: CWE-208: Observable Timing Discrepancy in notamitgamer mojic
Description
CVE-2026-41244 is a timing discrepancy vulnerability in the notamitgamer mojic CLI tool versions prior to 2. 1. 4. The issue arises because the CipherEngine uses a standard equality operator (! ==) to verify the HMAC-SHA256 integrity seal during decryption, which creates an observable timing difference. This timing discrepancy (CWE-208) could allow an attacker to bypass the file integrity check via a timing attack. The vulnerability has a medium severity with a CVSS score of 4. 7 and is fixed in version 2. 1. 4.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in mojic (a CLI tool that transforms C code into emoji streams) exists because the CipherEngine compares the HMAC-SHA256 integrity seal using a standard equality operator (!==) instead of a constant-time comparison. This leads to an observable timing discrepancy (CWE-208) during the decryption phase, potentially enabling an attacker to bypass integrity verification by measuring response times. Versions prior to 2.1.4 are affected. The issue is resolved in version 2.1.4.
Potential Impact
An attacker with local access could exploit the timing discrepancy to bypass the file integrity check, potentially allowing tampered or maliciously altered files to be accepted as valid. There is no impact on confidentiality or availability reported. The medium CVSS score reflects the integrity impact with limited attack vector (local) and high attack complexity.
Mitigation Recommendations
Upgrade mojic to version 2.1.4 or later, where the vulnerability is fixed by using a proper constant-time comparison for the HMAC-SHA256 integrity check. Since the vendor advisory confirms the fix in 2.1.4, applying this update fully mitigates the issue. No other mitigations are specifically indicated.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-04-18T03:47:03.135Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 69ebd11387115cfb686f0be5
Added to database: 4/24/2026, 8:22:43 PM
Last enriched: 4/24/2026, 8:36:00 PM
Last updated: 4/24/2026, 9:26:54 PM
Views: 4
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.
External Links
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.