# CVE-2026-43983: Pocket ID improper authorization in OIDC refresh token flow

Source: https://junglewise.ai/threats/cve-2026-43983-pocket-id-improper-authorization-in-oidc-refresh-token-flow  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-05-12. Updated: 2026-07-28  
License: CC BY 4.0 with a link back

CVE-2026-43983 · Severity: high · CVSS 8.1 · Published 2026-05-12

Pocket ID, an identity provider, contains a flaw where OIDC refresh tokens remain valid even after a user's access is revoked or their account is disabled by an administrator. This means a former employee or a revoked application could maintain persistent, unauthorized access to sensitive corporate services and personal data for up to 30 days at a time, indefinitely extending this window through token rotation. The 'kill switch' intended to immediately terminate access fails to affect these existing background tokens.

Technologies: [github.com/pocket-id/pocket-id/backend (Go)](https://junglewise.ai/threats/technologies/github-com-pocket-id-pocket-id-backend), [Pocket-Id Pocket Id](https://junglewise.ai/threats/technologies/pocket-id). Vendors: [Go](https://junglewise.ai/threats/vendors/go), [Pocket-Id](https://junglewise.ai/threats/vendors/pocket-id).

## Quick answers

**Is CVE-2026-43983 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-43983 being exploited in the wild.

**How severe is CVE-2026-43983?** High severity, with a CVSS score of 8.1, published 12 May 2026.

**Which products and versions are affected?** github.com/pocket-id/pocket-id/backend (Go) < 0.0.0-20260419162744-978ac87deffe, SEMVER:introduced=0,fixed=0.0.0-20260419162744-978ac87deffe; Pocket-Id Pocket Id < 0.0.0-20260419162744-978ac87deffe, < 2.6.0.

**Is there a fix for CVE-2026-43983?** Yes. github.com/pocket-id/pocket-id/backend (Go): upgrade to 0.0.0-20260419162744-978ac87deffe or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-43983 attacked?** It is attacked over the network, in a hosted service.

**Am I affected by CVE-2026-43983?** Check whether you run github.com/pocket-id/pocket-id/backend (Go) or Pocket-Id Pocket Id at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## How to fix

- github.com/pocket-id/pocket-id/backend (Go): upgrade to 0.0.0-20260419162744-978ac87deffe or later

  ```sh
  go get github.com/pocket-id/pocket-id/backend@v0.0.0-20260419162744-978ac87deffe
  ```


## Technical details

The `createTokenFromRefreshToken` function in `oidc_service.go` validates the cryptographic signature and expiration of refresh tokens but fails to verify the current status of the associated user and authorization record. Specifically, it does not check if the `user.Disabled` flag is set, if the `UserAuthorizedOidcClient` record still exists (revocation check), or if the user still meets group membership requirements via `IsUserGroupAllowedToAuthorize`. Because each successful refresh issues a new 30-day token, an attacker with an existing refresh token can maintain perpetual access despite administrative actions. The vulnerability is exacerbated by the fact that `RevokeAuthorizedClient` does not delete associated refresh tokens in the database. A patch is available in version 0.0.0-20260419162744-978ac87deffe.

## Affected products

- pocket-id Pocket ID < 0.0.0-20260419162744-978ac87deffe

## Identifiers

- CVE-2026-43983
- GHSA-w6p7-2fxx-4f44
- GO-2026-6119

## Timeline

- 2026-04-19: patched: Fix merged into main branch
- 2026-04-26: advisory: GitHub Advisory published

## References

- [https://api.github.com/users/kodareef5](https://api.github.com/users/kodareef5)
- [https://github.com/kodareef5](https://github.com/kodareef5)
- [https://api.github.com/users/kodareef5/gists%7B/gist_id%7D](https://api.github.com/users/kodareef5/gists%7B/gist_id%7D)
- [https://api.github.com/users/kodareef5/repos](https://api.github.com/users/kodareef5/repos)
- [https://avatars.githubusercontent.com/u/261977334?v=4](https://avatars.githubusercontent.com/u/261977334?v=4)
- [https://api.github.com/users/kodareef5/events%7B/privacy%7D](https://api.github.com/users/kodareef5/events%7B/privacy%7D)

## Related threats

- [Pocket ID OIDC audience validation bypass](https://junglewise.ai/threats/cve-2026-62662-pocket-id-is-an-oidc-provider-that-allows-users-to-authenticate)
- [Pocket ID email verification token privilege escalation](https://junglewise.ai/threats/cve-2026-115770-pocket-id-is-an-oidc-provider-that-allows-users-to-authenticate)
- [Pocket-ID open redirect in OIDC authorize page with prompt=none](https://junglewise.ai/threats/cve-2026-55834-pocket-id-open-redirect-in-oidc-authorize-page-with-prompt-none)
- [GO-2026-6117 - Pocket ID has a reauthentication bypass via one-time access token login , passkey step-up requirement…](https://junglewise.ai/threats/go-2026-6117-pocket-id-has-a-reauthentication-bypass-via-one-time-97f49b16)
- [Pocket ID reauthentication bypass via JWT freshness check fallback](https://junglewise.ai/threats/pocket-id-reauthentication-bypass-via-jwt-freshness-check-fallback-515ed392)