CVE-2026-117649
No CVSS score yet. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
The issue timeline API and the web issue page hid cross-reference events that point at issues the reader cannot access, but not "dependency added" and "dependency removed" events. When a readable issue had been linked as a dependency to an issue in a repository the reader cannot access, for example a private repository, any reader of the first issue, including anonymous users of a public repository, received the linked issue's current title, body, state, labels, poster and attachment names through the API, and its repository, number and title on the web page. Creating the link requires access to both issues; comments and attachment downloads of the linked issue stayed protected. Dependency events are now filtered with the same read permission check; a related exposure of unlinked attachment metadata through hidden dependency placeholders was already fixed in 28.2.0.
- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 13th percentile. Scored 2026-11-01. A forecast for this CVE across the internet, not for your own systems.
- Published
- Modified
- Record from
- the NVD, synced
Ask an AI about this CVE
ChatGPTClaudePerplexityGoogle AI Mode
Show the prompt
Explain CVE-2026-117649 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-117649?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-117649?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.