CVE-2026-62662Pocket ID: Client credentials grant allows any OIDC client to obtain tokens for arbitrary audiences
- 7.7HighCVSS base score
- 0.27%Exploitation in 30 daysEPSS · top 81% of all CVEs
- NoKnown exploitednot in CISA's KEV catalog
- YesPublic exploitsa reference or SSVC says so
Description
Pocket ID is an OIDC provider that allows users to authenticate with their passkeys to services. From 1.11.0 until 2.10.0, createTokenFromClientCredentials in backend/internal/service/oidc_service.go accepts the client-controlled resource parameter and embeds it directly in the access token aud claim without validating that the audience is registered or that the requesting client may access it. Any authenticated OIDC client can therefore obtain a Pocket ID-signed token naming another client or an arbitrary audience. The /api/oidc/introspect endpoint cannot distinguish the unauthorized token because it treats a token as active when the introspecting client's identifier matches the attacker-selected audience. In deployments where resource servers trust Pocket ID access tokens for service-to-service authorization, this bypasses audience-based access controls and can permit unauthorized data access or actions; deployments that do not use these tokens for resource-server authorization have no immediate exploitable impact. This issue is fixed in version 2.10.0.
Public exploit
An exploit or proof of concept is public: anyone can try it against an unpatched system. A reference of the record is tagged as an exploit. CISA's SSVC rates its exploitation: a proof of concept is public.
Show the exploits1
References tagged exploit1 reference
- https://github.com/pocket-id/pocket-id/security/advisories/GHSA-q4xm-p75h-h9p3 (opens in a new tab)x_refsource_CONFIRMexploit
Timeline
ID reserved
By GitHub_M
- 4 months later
· 4 months later
Published
- 5 days later
· 5 days later
Public exploit appeared
A proof of concept or exploit was published
Changes after publication (a new score, a public exploit, EPSS crossing 1, 10 or 50 %, leaving KEV) are kept since November 2026; earlier ones are not known.
Scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| GitHub_MCNA (assigner) | 3.0 | High7.7 | CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N |
| NVDNVD · Deferred | 3.0 | High7.7 | CVSS:3.0/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:N |
- EPSS (exploitation in 30 days)
- 0.27% · top 81% of all CVEs (18 Nov 2026)
- CISA SSVC
- Exploitation: poc · Automatable: no · Technical impact: total
The list uses the assigner's score when there is one, then CISA's, then NVD's: High 7.7.
Affected products
Affected packages
From reviewed advisories of the GitHub Advisory Database.
- Gogithub.com/pocket-id/pocket-id/backendGHSA-q4xm-p75h-h9p3 (opens in a new tab)
References
References4
- https://github.com/pocket-id/pocket-id/security/advisories/GHSA-q4xm-p75h-h9p3 (opens in a new tab)x_refsource_CONFIRMexploit
- https://github.com/pocket-id/pocket-id/pull/1520 (opens in a new tab)x_refsource_MISC
- https://github.com/pocket-id/pocket-id/commit/8158452b37304115c97c61c3a56082ce938ce6f0 (opens in a new tab)x_refsource_MISC
- https://github.com/pocket-id/pocket-id/releases/tag/v2.10.0 (opens in a new tab)x_refsource_MISC
Sources
The same CVE in the primary databases and aggregators, to check against.
- CVE.org record (opens in a new tab)
- CVE List JSON (GitHub) (opens in a new tab)
- NVD (opens in a new tab)
- FIRST EPSS (opens in a new tab)
- EUVD EUVD-2026-117171 (opens in a new tab)
- OSV.dev (opens in a new tab)
- GitHub Advisory GHSA-q4xm-p75h-h9p3 (opens in a new tab)
- CIRCL Vulnerability-Lookup (opens in a new tab)
Badge for a README or a ticket
[](https://cveledger.app/cve/CVE-2026-62662)Record last updated .