CVE-2026-9537: CWE-208 Observable Timing Discrepancy in JBERGER Mojo::JWT
Mojo::JWT versions before 1.02 for Perl verify HMAC signatures with a non-constant-time string comparison. The decode() method compares the supplied signature to the recomputed HMAC with Perl's eq operator, which stops at the first differing byte, so the comparison time varies with the number of matching leading bytes. A caller that decodes attacker supplied tokens leaks the expected signature through this timing variation, which can be aggregated over many requests to recover the signature and forge a token.
AI Analysis
Technical Summary
Mojo::JWT versions prior to 1.02 verify HMAC signatures using Perl's eq operator, which performs a byte-by-byte comparison and returns false at the first differing byte. This results in variable comparison times depending on the number of matching leading bytes, creating a timing side-channel (CWE-208). An attacker who can supply tokens to the decode() method can measure these timing variations to infer the correct signature incrementally, potentially allowing token forgery. The vulnerability affects all versions before 1.02. There is no vendor advisory or patch information available at this time.
Potential Impact
An attacker able to send attacker-controlled tokens to the decode() method can exploit timing discrepancies to recover the HMAC signature used for token verification. This can lead to token forgery, allowing unauthorized actions or privilege escalation within systems relying on Mojo::JWT for authentication or integrity checks. The vulnerability does not impact confidentiality or availability directly but compromises integrity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider implementing constant-time comparison functions for HMAC verification or avoid using vulnerable versions of Mojo::JWT. Monitoring vendor channels for updates is recommended.
CVE-2026-9537: CWE-208 Observable Timing Discrepancy in JBERGER Mojo::JWT
Description
Mojo::JWT versions before 1.02 for Perl verify HMAC signatures with a non-constant-time string comparison. The decode() method compares the supplied signature to the recomputed HMAC with Perl's eq operator, which stops at the first differing byte, so the comparison time varies with the number of matching leading bytes. A caller that decodes attacker supplied tokens leaks the expected signature through this timing variation, which can be aggregated over many requests to recover the signature and forge a token.
CVSS v3.1
Score 5.3medium
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
Mojo::JWT versions prior to 1.02 verify HMAC signatures using Perl's eq operator, which performs a byte-by-byte comparison and returns false at the first differing byte. This results in variable comparison times depending on the number of matching leading bytes, creating a timing side-channel (CWE-208). An attacker who can supply tokens to the decode() method can measure these timing variations to infer the correct signature incrementally, potentially allowing token forgery. The vulnerability affects all versions before 1.02. There is no vendor advisory or patch information available at this time.
Potential Impact
An attacker able to send attacker-controlled tokens to the decode() method can exploit timing discrepancies to recover the HMAC signature used for token verification. This can lead to token forgery, allowing unauthorized actions or privilege escalation within systems relying on Mojo::JWT for authentication or integrity checks. The vulnerability does not impact confidentiality or availability directly but compromises integrity.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider implementing constant-time comparison functions for HMAC verification or avoid using vulnerable versions of Mojo::JWT. Monitoring vendor channels for updates is recommended.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- CPANSec
- Date Reserved
- 2026-05-25T20:46:44.842Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a5b5eb82d1edb114c7fb6cb
Added to database: 07/18/2026, 11:08:40 UTC
Last enriched: 07/25/2026, 22:43:37 UTC
Last updated: 08/31/2026, 10:52:11 UTC
Views: 77
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.