CVE Feed
6.5 Medium

Outstatic: Authenticated GitHub REST proxy can send OAuth token to non-GitHub origins

CVE-2026-71425

Impact Outstatic’s authenticated GitHub REST proxy accepted an unvalidated endpoint parameter and constructed an upstream GitHub API URL by string concatenation while attaching the authenticated user’s GitHub OAuth token. A user with access to the Outstatic dashboard could craft a request that caused the server to send their own GitHub OAuth token to a non-GitHub host. If that token was captured, it could be used to access GitHub resources available to that same user, including private repositories depending on granted scopes. This does not allow unauthenticated attackers to access private repository data, and it does not directly expose another user’s GitHub token without an additional same-origin execution or request-forging primitive. Patches The issue has been patched by validating that proxied requests resolve to the exact https://api.github.com/ origin and by restricting forwarded request headers. Users should upgrade to v2.2.1 or later. Workarounds If upgrading immediately is not possible, restrict access to /api/outstatic/github to trusted dashboard users only, or temporarily disable the endpoint if it is not needed. As a temporary code-level mitigation, reject…

Assessment

CVSS
6.5 (v3.1)
Severity
Medium
Known exploited
Not listed in CISA KEV
Exploit availability
Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published
18 November 2026
Last updated
18 November 2026
Affected
outstatic
Weakness
CWE-918

CVSS vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept
Before you submit *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-71425