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

Medium CVSS 6.5

OSV id
GHSA-7jvc-9xq8-frff
Also known as
CVE-2026-71425
Published
Last modified

Affected packages

PackageAffected versionsFixed in
outstatic
npm
< 2.2.1 2.2.1

How to fix it

Upgrade outstatic to 2.2.1 or later.

npm install outstatic@2.2.1
# if it is an indirect dependency: npm update outstatic (or npm audit fix)
  • If it is an indirect dependency, upgrade the package that depends on it, or force the version with "overrides" (npm), "resolutions" (Yarn) or "pnpm.overrides" (pnpm) in package.json.
  • Check the changelog for breaking changes (especially across major versions), update the lockfile with the package manager, and run your tests.

Not sure whether your project uses an affected version? Check your lockfile below for free.

Details

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 body-provided endpoint values that do not begin with /, verify the parsed URL origin is exactly https://api.github.com/, and block forwarding of sensitive headers such as Authorization, Host, and User-Agent.

Users who suspect their token was exposed should revoke the affected GitHub OAuth authorization and sign in again.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: GitHub Advisory Database via OSV.dev (CC-BY 4.0). Severity comes from the advisory's own rating when it has one, else from its CVSS score.