Post-logout access via unreclaimed server-side session
Published Mar 6, 2026 · Updated Mar 6, 2026
Session expiration failure in OliveTin before 3000.11.1 allows remote authenticated users to retain access with a logged-out session cookie. The Logout handler clears the browser cookie but does not delete the SID from shared sessionStorage or the OAuth2 registeredStates map. Exploitation requires a previously captured valid cookie; replay keeps the associated account authenticated until the session expires, by default after about one year.
Summary
What happened
Session expiration failure in OliveTin before 3000.11.1 allows remote authenticated users to retain access with a logged-out session cookie. The Logout handler clears the browser cookie but does not delete the SID from shared sessionStorage or the OAuth2 registeredStates map. Exploitation requires a previously captured valid cookie; replay keeps the associated account authenticated until the session expires, by default after about one year.
The record
- CVE
- CVE-2026-30224
- Published
- Mar 6, 2026
- Updated
- Mar 6, 2026
- Vendor
- OliveTin
- Product
- OliveTin
- Classifications
- CWE-613, CWE-384, T1550.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 6, 2026CVE publishedPublication date reported by the CVE source.
- Mar 6, 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=< 3000.11.1
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
- Vendor advisory session-replay 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