Persistent account access via unrevoked JWTs
Published Feb 26, 2026 · Updated Feb 26, 2026
Insufficient session expiration in Morelitea Initiative before 0.32.4 allows remote authenticated users to retain API access with an old JWT. The backend accepts a previously issued access token until its exp claim without checking a revocation list, token identifier, or token version after logout or a password change. Possession of a captured valid JWT is required; reuse preserves access to protected account data until the token expires.
Summary
What happened
Insufficient session expiration in Morelitea Initiative before 0.32.4 allows remote authenticated users to retain API access with an old JWT. The backend accepts a previously issued access token until its exp claim without checking a revocation list, token identifier, or token version after logout or a password change. Possession of a captured valid JWT is required; reuse preserves access to protected account data until the token expires.
The record
- CVE
- CVE-2026-28275
- Published
- Feb 26, 2026
- Updated
- Feb 26, 2026
- Vendor
- Morelitea
- Product
- Initiative
- Classifications
- CWE-613, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 26, 2026CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.32.4
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-hww6-3fww-xw3h proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo