CVE-2026-62662

HIGHPre-NVD 7.77.7
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 7.7 from GitHub Security Advisory (severity: HIGH) published 2026-11-09. A secondary CVSS source baseline 7.7; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Elevated

Also known asEUVD-2026-117171 (ENISA EUVD) · GHSA-q4xm-p75h-h9p3 (GitHub Security Advisories)Source: ENISA EUVD

7.7EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 7.7Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
7.7
EG Score
7.7HIGHhigh confidence
EG Risk
51
EG Risk 51/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity77% × 45%
Impact severity (EG Severity): CVSS 7.7 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.3%
EPSS %ILE
18th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.7): severity, escalated by confirmed exploitation. This CVE's 7.7 is its impact severity (EG Severity), not escalated.

EG Severity
7.7 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.3% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-12). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

November 4, 2026

Last Modified

November 12, 2026

Advisory Details (3)

Auto-updated Nov 4, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_release.
GitHub release Patch Available

v2.10.0

Patch available: pocket-id/pocket-id v2.10.0

https://github.com/pocket-id/pocket-id/releases/tag/v2.10.0
GitHub pull request

refactor: use fosite for OAuth 2.0 logic

Fix merged in pocket-id/pocket-id PR #1520 on 2026-06-22 — awaiting tagged release

https://github.com/pocket-id/pocket-id/pull/1520
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Client credentials grant allows any OIDC client to obtain tokens for arbitrary audiences · Advisory · pocket-id/pocket-id · GitHub

https://github.com/pocket-id/pocket-id/security/advisories/GHSA-q4xm-p75h-h9p3

Vendor Advisories for CVE-2026-62662(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/pocket-id/pocket-id/backend @ 0.0.0-20260622164202-8158452b3730 (fixes < 0.0.0-20260622164202-8158452b3730)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/pocket-id/pocket-id/backend—
  • every version up to 0.0.0-20260622164202-8158452b3730: fixed in 0.0.0-20260622164202-8158452b3730
—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 15× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  2. 2026-11-12 22:28 UTCEchelonGraph re-scored
  3. 2026-11-12 22:28 UTCGHSA enrichmentGHSA-q4xm-p75h-h9p3 · GitHub severity HIGH · GitHub CVSS 7.7
  4. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  5. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  6. 2026-11-10 16:45 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  7. 2026-11-09 22:41 UTCEchelonGraph re-scored
  8. 2026-11-09 22:41 UTCGHSA enrichmentGHSA-q4xm-p75h-h9p3 · GitHub severity HIGH · GitHub CVSS 7.7
  9. 2026-11-09 22:09 UTCEchelonGraph re-scored
  10. 2026-11-09 22:09 UTCGHSA enrichmentGHSA-q4xm-p75h-h9p3 · GitHub severity HIGH · GitHub CVSS 7.7
  11. 2026-11-09 21:46 UTCEchelonGraph re-scored
  12. 2026-11-09 21:46 UTCGHSA enrichmentGHSA-q4xm-p75h-h9p3 · GitHub severity HIGH · GitHub CVSS 7.7
  13. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  14. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  15. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  16. 2026-11-06 16:39 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  17. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.3% · 18th percentile
  18. 2026-11-04 23:26 UTCEchelonGraph re-scored
  19. 2026-11-04 23:03 UTCENISA EUVD ID recordedEUVD-2026-117171 · Source: ENISA EUVD
  20. 2026-11-04 22:35 UTCEchelonGraph re-scoredFirst assessed: 7.7 HIGH
  21. 2026-11-04 22:34 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-62662?
CVE-2026-62662 is a high-severity vulnerability; its CVE record was published on November 4, 2026. 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…
When was the CVE record for CVE-2026-62662 published?
The CVE record for CVE-2026-62662 was published on November 4, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 12, 2026; the record at its source may have been updated since.
Is CVE-2026-62662 actively exploited?
CVE-2026-62662 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (18th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-62662?
CVE-2026-62662 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-62662?
A fix for CVE-2026-62662 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-62662 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-62662

Explore →

Is Your Infrastructure Affected by CVE-2026-62662?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs