CVE
Outstatic server-side request forgery in GitHub REST proxy
- Exploited
- No known exploitation
- Fix
- Fixed in 2.2.1
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 2.2.1.
Summary
Outstatic, a static site CMS, has a flaw in its authenticated GitHub REST proxy that can send a logged-in dashboard user's GitHub OAuth token to a non-GitHub host. An attacker who has a dashboard account can reach this remotely over the network, and it could expose private repositories and other resources allowed by the token's scopes.
Original description
Outstatic is a static site CMS for Markdown and MDX content stored in GitHub repositories. Prior to 2.2.1, the authenticated GitHub REST proxy accepts an unvalidated endpoint value, constructs an upstream URL by string concatenation, and attaches the current dashboard user's GitHub OAuth token without ensuring the destination remains the exact GitHub API origin. An authenticated dashboard user can cause the server to send that user's token to a non-GitHub host, potentially exposing private repositories and other resources allowed by the token's scopes. The issue does not let an unauthenticated attacker access private data and does not directly expose another user's token without an additional same-origin execution or request-forging primitive. This issue is fixed in version 2.2.1.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure3/25Reachable over the network · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity6.5/10CVSS 6.5
- No patch0/5No signal
What would change the score
- Would score about 65 if added to CISA KEV
- Would score about 60 if CISA's SSVC rates exploitation active
- Would score about 29 if advisories confirm default setups are exposed
What to do
Upgrade to a fixed version: 2.2.1.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-71425 (Outstatic: Authenticated GitHub REST proxy can send OAuth token to non-GitHub origins), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-71425 (entry last updated 2026-11-18):
Affected:
- avitorio outstatic: fixed in 2.2.1
Fixed versions: 2.2.1.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-71425 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-71425 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/avitorio/outstatic/security/advisories/GHSA-7jvc-9xq8-frff
- https://github.com/avitorio/outstatic/commit/03b9147a04336986174ef0be1c300b3abbbec3e1
- https://github.com/avitorio/outstatic/releases/tag/v2.2.1
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-71425
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-71425"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
- avitorio outstatic
fixed in 2.2.1
Evidence 5
| Kind | Source |
|---|---|
| Vendor advisory 1Establishes: Affected and fixed versions. | |
| Advisory | GitHub · avitorio/outstatic · Advisory GHSA-7jvc-9xq8-frff |
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-71425 |
| Record | NVD · CVE-2026-71425 |
| Other links 2 | |
| Repository | GitHub · avitorio/outstatic · Commit 03b9147a |
| Repository | GitHub · avitorio/outstatic · Release v2.2.1 |
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-71425
Is CVE-2026-71425 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
Which versions are affected by CVE-2026-71425?
outstatic: before 2.2.1.Source: cve.now feed data
How do I fix CVE-2026-71425?
Upgrade to a fixed version: 2.2.1.Source: cve.now feed data