GHSA-7JVC-9XQ8-FRFF

Vulnerability from github – Published: 2026-11-18 20:43 – Updated: 2026-11-18 20:43
VLAI
Summary
Outstatic: Authenticated GitHub REST proxy can send OAuth token to non-GitHub origins
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.

Show details on source website

{
  "affected": [
    {
      "database_specific": {
        "last_known_affected_version_range": "\u003c= 2.2.0"
      },
      "package": {
        "ecosystem": "npm",
        "name": "outstatic"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "0"
            },
            {
              "fixed": "2.2.1"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ]
    }
  ],
  "aliases": [
    "CVE-2026-71425"
  ],
  "database_specific": {
    "cwe_ids": [
      "CWE-918"
    ],
    "github_reviewed": true,
    "github_reviewed_at": "2026-11-18T20:43:43Z",
    "nvd_published_at": null,
    "severity": "MODERATE"
  },
  "details": "### Impact\nOutstatic\u2019s authenticated GitHub REST proxy accepted an unvalidated endpoint parameter and constructed an upstream GitHub API URL by string concatenation while attaching the authenticated user\u2019s GitHub OAuth token.\n\nA 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.\n\nThis does not allow unauthenticated attackers to access private repository data, and it does not directly expose another user\u2019s GitHub token without an additional same-origin execution or request-forging primitive.\n\n### Patches\nThe issue has been patched by validating that proxied requests resolve to the exact https://api.github.com/ origin and by restricting forwarded request headers.\n\nUsers should upgrade to v2.2.1 or later.\n\n### Workarounds\nIf 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.\n\nAs 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.\n\nUsers who suspect their token was exposed should revoke the affected GitHub OAuth authorization and sign in again.",
  "id": "GHSA-7jvc-9xq8-frff",
  "modified": "2026-11-18T20:43:43Z",
  "published": "2026-11-18T20:43:43Z",
  "references": [
    {
      "type": "WEB",
      "url": "https://github.com/avitorio/outstatic/security/advisories/GHSA-7jvc-9xq8-frff"
    },
    {
      "type": "WEB",
      "url": "https://github.com/avitorio/outstatic/commit/03b9147a04336986174ef0be1c300b3abbbec3e1"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/avitorio/outstatic"
    },
    {
      "type": "WEB",
      "url": "https://github.com/avitorio/outstatic/releases/tag/v2.2.1"
    }
  ],
  "schema_version": "1.4.0",
  "severity": [
    {
      "score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Outstatic: Authenticated GitHub REST proxy can send OAuth token to non-GitHub origins"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…