CVE-2026-55250: CWE-294: Authentication Bypass by Capture-replay in macropay-solutions maravel-framework
CVE-2026-55250 is a high-severity token replay vulnerability in macropay-solutions maravel-framework versions prior to 10.74.0. The issue arises from a lifecycle mismatch between stateless token validation and a caching layer that truncates token blacklist lifespans from 14 days to 2 hours. This allows blacklisted tokens to be accepted after cache eviction or flush, enabling token replay attacks. The vulnerability is due to architectural assumptions in the tymon/jwt-auth package used for API token authentication. Maravel 10.74.0 introduced a partial fix by backporting a new tagged cache implementation, but no direct patch fully resolves the issue without configuration changes. Users must apply a workaround to decouple token identifiers from the tagging cache to preserve the full blacklist lifespan.
AI Analysis
Technical Summary
Maravel framework versions before 10.74.0 suffer from a token replay vulnerability caused by a structural lifecycle mismatch between stateless token validation and a high-performance relational caching layer. The tymon/jwt-auth package uses cache tags to manage a 14-day token blacklist, but a global cache TTL cap of 2 hours truncates blacklist entries prematurely. Additionally, cache tag flushes reset internal version pointers, invalidating blacklist records instantly. As a result, tokens that should be blacklisted remain valid for up to 14 days, enabling replay attacks. This flaw stems from architectural assumptions in tymon/jwt-auth rather than a core framework defect. Version 10.74.0 backports a fixed tagged cache from 20.x but requires users to apply a configuration workaround to decouple token blacklist storage from the tagging subsystem, ensuring tokens retain their full 14-day blacklist lifespan.
Potential Impact
The vulnerability allows attackers to reuse blacklisted JWT tokens after cache eviction or flush events, bypassing authentication controls. This can lead to unauthorized access to APIs protected by the maravel-framework using tymon/jwt-auth for token authentication. The tokens remain cryptographically valid for up to 14 days despite being blacklisted, enabling widespread token replay attacks. This undermines the security of applications relying on token blacklisting for session invalidation or logout enforcement.
Mitigation Recommendations
No official patch or direct framework upgrade fully resolves this issue as it originates from architectural assumptions in the tymon/jwt-auth package. Users should apply the documented workaround by configuring the system to decouple token blacklist entries from the relational tagging cache. Specifically, token identifiers must be stored as flat, un-tagged key-value pairs in the primary cache keyspace to preserve their full 14-day lifecycle. Additionally, ensure cache memory is sized to prevent premature evictions that delete blacklist entries early. Monitor vendor advisories for any future official fixes.
CVE-2026-55250: CWE-294: Authentication Bypass by Capture-replay in macropay-solutions maravel-framework
Description
CVE-2026-55250 is a high-severity token replay vulnerability in macropay-solutions maravel-framework versions prior to 10.74.0. The issue arises from a lifecycle mismatch between stateless token validation and a caching layer that truncates token blacklist lifespans from 14 days to 2 hours. This allows blacklisted tokens to be accepted after cache eviction or flush, enabling token replay attacks. The vulnerability is due to architectural assumptions in the tymon/jwt-auth package used for API token authentication. Maravel 10.74.0 introduced a partial fix by backporting a new tagged cache implementation, but no direct patch fully resolves the issue without configuration changes. Users must apply a workaround to decouple token identifiers from the tagging cache to preserve the full blacklist lifespan.
CVSS v4.0
Score 8.7high
Affected software
pkg:composer/macropay-solutions/maravel-frameworkRun 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
Maravel framework versions before 10.74.0 suffer from a token replay vulnerability caused by a structural lifecycle mismatch between stateless token validation and a high-performance relational caching layer. The tymon/jwt-auth package uses cache tags to manage a 14-day token blacklist, but a global cache TTL cap of 2 hours truncates blacklist entries prematurely. Additionally, cache tag flushes reset internal version pointers, invalidating blacklist records instantly. As a result, tokens that should be blacklisted remain valid for up to 14 days, enabling replay attacks. This flaw stems from architectural assumptions in tymon/jwt-auth rather than a core framework defect. Version 10.74.0 backports a fixed tagged cache from 20.x but requires users to apply a configuration workaround to decouple token blacklist storage from the tagging subsystem, ensuring tokens retain their full 14-day blacklist lifespan.
Potential Impact
The vulnerability allows attackers to reuse blacklisted JWT tokens after cache eviction or flush events, bypassing authentication controls. This can lead to unauthorized access to APIs protected by the maravel-framework using tymon/jwt-auth for token authentication. The tokens remain cryptographically valid for up to 14 days despite being blacklisted, enabling widespread token replay attacks. This undermines the security of applications relying on token blacklisting for session invalidation or logout enforcement.
Mitigation Recommendations
No official patch or direct framework upgrade fully resolves this issue as it originates from architectural assumptions in the tymon/jwt-auth package. Users should apply the documented workaround by configuring the system to decouple token blacklist entries from the relational tagging cache. Specifically, token identifiers must be stored as flat, un-tagged key-value pairs in the primary cache keyspace to preserve their full 14-day lifecycle. Additionally, ensure cache memory is sized to prevent premature evictions that delete blacklist entries early. Monitor vendor advisories for any future official fixes.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-06-16T16:44:00.625Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6aa08abdacd9273b494d73c8
Added to database: 09/08/2026, 22:22:53 UTC
Last enriched: 09/08/2026, 22:37:05 UTC
Last updated: 09/08/2026, 22:52:55 UTC
Views: 7
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.