CVE-2026-131820
7.7HighPublished 18 Nov 2026 · NVD status: Received · AI triage by gemini-3.1-flash-lite
High
0CVSS v4.010
- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User action
- None
- Impact
- Full C/I/A compromise
- Weakness
- CWE-918
What an attacker gets
Authenticated users with repository write access can achieve remote code execution on the appliance. This requires Secret Protection with secret scanning and validity checks for partner patterns to be enabled.
Root cause
The application performs server-side request forgery during Slack webhook validity checks.
Affected versions
GitHub Enterprise Server versions prior to 3.23
CVSS v4.0 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Fix & remediation
Upgrade to GitHub Enterprise Server 3.22.5, 3.21.10, or 3.20.12. If you cannot patch immediately, disable secret scanning and validity checks for partner patterns.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
A server-side request forgery vulnerability in GitHub Enterprise Server allowed an authenticated user with repository write access to send requests to internal services through Slack webhook validity checks, potentially leading to remote code execution on the appliance. Exploitation required Secret Protection with secret scanning and validity checks for partner patterns enabled. This vulnerability affected all versions prior to 3.23 and was fixed in versions 3.22.5, 3.21.10, and 3.20.12. This vulnerability was reported via the GitHub Bug Bounty program.