CVE-2026-119625
No CVSS score yet. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
The `/{username}` web route accepted personal access tokens over HTTP Basic authentication without checking their scope. A token confined to an unrelated scope, such as `read:issue`, could read its owner's private activity through the user RSS/Atom feed and the profile activity tab, and other members' activity in a private organization through the organization feed; a public-only token could list the owner's private repositories and organizations and render private profile READMEs. For a site administrator's token this applied to every account. Tokens are now accepted on this route only for feeds, which require `read:user` or `read:organization`.
- EPSS
- 0.3% estimated probability of exploitation activity in the next 30 days; 17th percentile. Scored 2026-11-01. A forecast for this CVE across the internet, not for your own systems.
- CWE
- 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-119625 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-119625?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-119625?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.