Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.5amended

Pocket ID: OIDC refresh token flow bypasses authorization revocation, account disabling, and group restrictions

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

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/pocket-id/pocket-id/backend 0.0.0-20260419162744-978ac87deffe), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
8.5 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-43983: 0.25% estimated exploitation activity in the next 30 days; percentile 16.13 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

OIDC Refresh Token Flow Bypasses Authorization Revocation, Account Disabling, and Group Restrictions Summary The createTokenFromRefreshToken function (oidcservice.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: 1. Authorization revocation bypass: After a user revokes an OIDC client's authorization, the client can continue refreshing tokens indefinitely because RevokeAuthorizedClient does not delete associated refresh tokens, and the refresh flow does not check if the authorization record still exists. 2. 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. 3. Group restriction bypass: After removing a user from an OIDC client's…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 4 · amended ·

    Amended from ghsa record GHSA-w6p7-2fxx-4f44

  2. Revision 3 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 2 · amended ·

    Amended from osv record GO-2026-6119

  4. Revision 1 · created ·

    Published from osv record GHSA-w6p7-2fxx-4f44

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-43983

Advisory: Pocket ID: OIDC refresh token flow bypasses authorization revocation, account disabling, and group restrictions
IDs: CVE-2026-43983, GHSA-w6p7-2fxx-4f44
Record: https://patchnext.com/advisories/cve-2026-43983 (revision 4, source checked 26 Oct 2026, 15:27 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/pocket-id/pocket-id/backend 0.0.0-20260419162744-978ac87deffe. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/pocket-id/pocket-id/backend: affected < 0.0.0-20260419162744-978ac87deffe; fixed in 0.0.0-20260419162744-978ac87deffe

## Suggested inspection (read-only)
- Go github.com/pocket-id/pocket-id/backend: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/pocket-id/pocket-id/backend.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-w6p7-2fxx-4f44 (OSV record GHSA-w6p7-2fxx-4f44 lists affected ranges: Go github.com/pocket-id/pocket-id/backend >=0 <0.0.0-20260419162744-978ac87deffe (fixed))
- Verified: https://osv.dev/vulnerability/GO-2026-6119 (OSV record GO-2026-6119 lists affected ranges: Go github.com/pocket-id/pocket-id/backend >=0 <0.0.0-20260419162744-978ac87deffe (fixed))
- Verified: https://github.com/advisories/GHSA-w6p7-2fxx-4f44 (GitHub-reviewed advisory GHSA-w6p7-2fxx-4f44 lists affected ranges: Go github.com/pocket-id/pocket-id/backend >=0 <0.0.0-20260419162744-978ac87deffe)

Commands are suggestions: review each one before running it.

Loading voting…