Pocket ID: The client credentials grant allows any OIDC client to obtain tokens for arbitrary audiences
CVE-2026-62662GHSA-q4xm-p75h-h9p3
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-20260622164202-8158452b3730), 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.
Affected packages
Go github.com/pocket-id/pocket-id/backend
- Affected
- < 0.0.0-20260622164202-8158452b3730
- Fixed in
- 0.0.0-20260622164202-8158452b3730
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-q4xm-p75h-h9p3 lists affected ranges: Go github.com/pocket-id/pocket-id/backend >=0 <0.0.0-20260622164202-8158452b3730
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-q4xm-p75h-h9p3 lists affected ranges: Go github.com/pocket-id/pocket-id/backend >=0 <0.0.0-20260622164202-8158452b3730 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.7 · CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N
- EPSS
- CVE-2026-62662: 0.27% estimated exploitation activity in the next 30 days; percentile 18.65 (FIRST EPSS, 2026-11-10). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary The client credentials grant (`grant_type=client_credentials`) does not validate the resource parameter before embedding it as the aud claim in the issued JWT. Any authenticated OIDC client can obtain a Pocket ID-signed access token claiming authorization for any arbitrary audience, including other registered OIDC clients. There is no check that the requested audience is a registered resource server, and no check that the requesting client has been granted permission to access it.
Details In `backend/internal/service/oidc_service.go`, `createTokenFromClientCredentials` accepts the resource parameter from the token request and places it directly into the `aud` claim of the issued JWT without validation: ```golang audClaim := client.ID if input.Resource != "" { audClaim = input.Resource // no validation performed } accessToken, err := s.jwtService.GenerateOAuthAccessToken(dummyUser, audClaim) ``` The only guard in this function is `verifyClientCredentialsInternal`, which…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from osv record GHSA-q4xm-p75h-h9p3
- Revision 1 · created ·
Published from ghsa record GHSA-q4xm-p75h-h9p3
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-62662 Advisory: Pocket ID: The client credentials grant allows any OIDC client to obtain tokens for arbitrary audiences IDs: CVE-2026-62662, GHSA-q4xm-p75h-h9p3 Record: https://patchnext.com/advisories/cve-2026-62662 (revision 2, source checked 10 Nov 2026, 06:45 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.7) 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-20260622164202-8158452b3730. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/pocket-id/pocket-id/backend: affected < 0.0.0-20260622164202-8158452b3730; fixed in 0.0.0-20260622164202-8158452b3730 ## 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://github.com/advisories/GHSA-q4xm-p75h-h9p3 (GitHub-reviewed advisory GHSA-q4xm-p75h-h9p3 lists affected ranges: Go github.com/pocket-id/pocket-id/backend >=0 <0.0.0-20260622164202-8158452b3730) - Verified: https://osv.dev/vulnerability/GHSA-q4xm-p75h-h9p3 (OSV record GHSA-q4xm-p75h-h9p3 lists affected ranges: Go github.com/pocket-id/pocket-id/backend >=0 <0.0.0-20260622164202-8158452b3730 (fixed)) Commands are suggestions: review each one before running it.
Loading voting…