Skip to main content
VulnerabilityPublished

CVE-2026-71425: Outstatic · Authenticated GitHub REST proxy can send OAuth token to non-GitHub origins

Affects outstaticSource GCVE Database

0
Compare
Authoritative record:CVE-2026-71425· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.2.1 when convenient.

Data as of 18 Nov 2026, 21:37 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 3.16.5
Patch
Available – fixed in 2.2.1
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade outstatic to 2.2.1.

Affected software

ProductAffectedFixed in
npmoutstaticAffected
  • <2.2.1
Fixed in
  • 2.2.1

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available in Outstatic version 2.2.1 that fixes this vulnerability by enforcing strict origin validation and restricting forwarded headers. Users should upgrade to version 2.2.1 or later. If immediate upgrade is not possible, restrict access to the /api/outstatic/github endpoint to trusted dashboard users or disable the endpoint if unused. As a temporary code-level mitigation, reject endpoint values not starting with '/', verify the URL origin is exactly https://api.github.com/, and block forwarding of sensitive headers such as Authorization, Host, and User-Agent. Users who suspect token exposure should revoke the affected GitHub OAuth authorization and re-authenticate.

Description

Outstatic versions prior to 2.2.1 contain a vulnerability in their authenticated GitHub REST proxy that allows a user with dashboard access to cause the server to send their GitHub OAuth token to arbitrary non-GitHub origins. This occurs because the endpoint parameter was not properly validated, enabling token leakage to external hosts. The vulnerability does not allow unauthenticated attackers to access private data or other users' tokens without additional exploits. The issue has been fixed in version 2.2.1 by enforcing strict origin validation and restricting forwarded headers.

References

Community reviews

Loading reviews…