Persistent OIDC access via stale refresh tokens
Published May 12, 2026 · Updated May 12, 2026
Improper authorization in Pocket ID before 2.6.0 allows remote authenticated users to retain OIDC access with stale refresh tokens. createTokenFromRefreshToken verifies token integrity, expiry, and client ownership but omits checks for account disabling, revoked client authorization, and current group eligibility. A valid refresh token and client credentials from earlier authorized access are required; successful refreshes issue new access and identity tokens containing user claims.
Summary
What happened
Improper authorization in Pocket ID before 2.6.0 allows remote authenticated users to retain OIDC access with stale refresh tokens. createTokenFromRefreshToken verifies token integrity, expiry, and client ownership but omits checks for account disabling, revoked client authorization, and current group eligibility. A valid refresh token and client credentials from earlier authorized access are required; successful refreshes issue new access and identity tokens containing user claims.
The record
- CVE
- CVE-2026-43983
- Published
- May 12, 2026
- Updated
- May 12, 2026
- Vendor
- Pocket ID
- Product
- Pocket ID
- Classifications
- CWE-613, CWE-285, T1550.001
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 12, 2026CVE publishedPublication date reported by the CVE source.
- May 12, 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=< 2.6.0
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
- Verified live stale-refresh-token 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