Vulnerability in github.com/pocket-id/pocket-id/backend (CVE-2026-43983)
Summary
Vulnerability in github.com/pocket-id/pocket-id/backend (CVE-2026-43983). Confidential information can be exposed externally. Exploitable via createTokenFromRefreshToken. Mitigation: upgrade to 0.0.0-20260419162744-978ac87deffe or later.
Original description
The description as published by the source.
OIDC Refresh Token Flow Bypasses Authorization Revocation, Account Disabling, and Group Restrictions
Summary
The createTokenFromRefreshToken function (oidc_service.go:451) validates the refresh token's cryptographic integrity but does not re-validate the user's current authorization state before issuing new tokens. This allows three bypasses:
-
Authorization revocation bypass: After a user revokes an OIDC client's authorization, the client can continue refreshing tokens indefinitely because
RevokeAuthorizedClientdoes not delete associated refresh tokens, and the refresh flow does not check if the authorization record still exists. -
Disabled user bypass: After an admin disables a user account, pre-existing refresh tokens continue to work because the OIDC token endpoint does not check
user.Disabled. Session-based access is properly blocked by auth middleware, but the OIDC refresh path bypasses it entirely. -
Group restriction bypass: After removing a user from an OIDC client's allowed user groups, the refresh token continues to work because
createTokenFromRefreshTokendoes not callIsUserGroupAllowedToAuthorize.
Each refresh rotates the token with a fresh 30-day expiry, enabling perpetual access.
Target
- Repository: pocket-id/pocket-id
- Version: HEAD (626adbf), also affects v2.5.0 and all versions with refresh token support
Root Cause
createTokenFromRefreshToken (oidc_service.go:451-547) performs the following checks o…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-43983 has been found in github.com/pocket-id/pocket-id/backend.
Attackers can target a specific entry point like createTokenFromRefreshToken over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade github.com/pocket-id/pocket-id/backend to 0.0.0-20260419162744-978ac87deffe or later.
If unsure, ask your IT team or search "github.com/pocket-id/pocket-id/backend CVE-2026-43983" on the vendor's site.
CVE-2026-43983 (github.com/pocket-id/pocket-id/backend) — CWE-285 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: createTokenFromRefreshToken / RevokeAuthorizedClient / user.Disabled / IsUserGroupAllowedToAuthorize
Patched: 0.0.0-20260419162744-978ac87deffe — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-285) exists in github.com/pocket-id/pocket-id/backend. Attackers reach the vulnerable code path via createTokenFromRefreshToken.
Check the vendor advisory for the affected versions of github.com/pocket-id/pocket-id/backend. Attack surface: createTokenFromRefreshToken / RevokeAuthorizedClient / user.Disabled / IsUserGroupAllowedToAuthorize.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 0.0.0-20260419162744-978ac87deffe.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/pocket-id/pocket-id/backend' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/pocket-id/pocket-id/backend' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/pocket-id/pocket-id/backendを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/pocket-id/pocket-id/backend to 0.0.0-20260419162744-978ac87deffeステージング環境で 0.0.0-20260419162744-978ac87deffe に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com