CVE-2026-118394
No CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
The OAuth2 userinfo endpoint (`/login/oauth/userinfo`) decided whether to limit the `groups` claim to public organizations by re-parsing the `Authorization` header as an OAuth2 access token instead of using the scope of the credential that authenticated the request. When a public-only OAuth2 token was sent as a query parameter or form field, or a public-only personal access token was used, that scope came back empty and the claim listed the token owner's private organizations, teams and concealed memberships. The disclosure is limited to the owner's organization and team names and memberships; no repository content is exposed. The endpoint now uses the scope of the authenticating token.
- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 10th percentile. Scored 2026-11-01. A forecast for this CVE across the internet, not for your own systems.
- CWEs
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-863 Incorrect Authorization - Published
- Modified
- Record from
- the NVD, synced
Ask an AI about this CVE
ChatGPTClaudePerplexityGoogle AI Mode
Show the prompt
Explain CVE-2026-118394 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-118394?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-118394?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an estimate of exploitation activity across the internet over the next 30 days, not a prediction for my systems). Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.