CVE-2026-71425: avitorio outstatic · Server-Side Request Forgery
Affects avitorio outstaticSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 2.2.1 when convenient.
Data as of 18 Nov 2026, 20:06 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 6.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:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 17 Nov 2026.
What to do
Upgrade avitorio outstatic to 2.2.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| avitoriooutstatic | Affected
| Fixed in
|
AI-suggested
Upgrade avitorio outstatic to version 2.2.1 or later, where this SSRF vulnerability is fixed. No other mitigation is required as the vendor has provided an official fix.
Description
CVE-2026-71425 is a server-side request forgery (SSRF) vulnerability in avitorio outstatic versions prior to 2.2.1. The issue arises because the authenticated GitHub REST proxy accepts an unvalidated endpoint parameter and concatenates it to form an upstream URL, attaching the user's GitHub OAuth token without verifying the destination host. This allows an authenticated user to cause the server to send their token to a non-GitHub host, potentially exposing private repositories and resources accessible by the token. The vulnerability does not allow unauthenticated attackers to access private data or other users' tokens without additional exploitation. The issue is fixed in version 2.2.1.