CVE-2026-131820

Server-side request forgery in GitHub Enterprise Server enabled remote code execution via Slack webhook validity checks

Published Nov 18, 2026 CVSS 4.0 · 7.7 High EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

A server‑side request forgery flaw in GitHub Enterprise Server allows an authenticated user with repository write access to target internal services through Slack webhook validity checks. By satisfying Secret Protection with secret scanning and partner pattern validity checks, an attacker can cause the enterprise appliance to execute arbitrary code. The weakness is a classic SSRF vulnerability (CWE‑918) that can compromise confidentiality, integrity, and availability of the affected system.

Affected Systems

GitHub Enterprise Server versions earlier than 3.23 are affected. The issue has been addressed in 3.22.5, 3.21.10, and 3.20.12 releases, as noted in GitHub’s enterprise server release notes for these versions.

Risk and Exploitability

The CVSS score of 7.7 indicates high severity, and the EPSS score is < 1%. The vulnerability is not listed in the CISA KEV catalog. It requires the application’s Secret Protection feature and partner pattern checks to be enabled, meaning that exploitation is limited to customers who have both enabled. Nonetheless, if those conditions are met, an attacker can exploit the SSRF vector to reach internal network services and potentially achieve remote code execution on the appliance.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to the latest GitHub Enterprise Server release (at least 3.22.5, 3.21.10, or 3.20.12) where the SSRF fix is applied
  • If upgrading immediately is not possible, disable the Secret Protection partner pattern checks for Slack webhook validation to eliminate the exploitation route
  • Restrict repository write permissions to trusted users only, ensuring that only authenticated owners can trigger the vulnerable workflow

Generated by OpenCVE AI on November 18, 2026 at 21:38 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Github
Github enterprise Server
Vendors & Products Github
Github enterprise Server
Type Values Removed Values Added
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.
Title Server-side request forgery in GitHub Enterprise Server enabled remote code execution via Slack webhook validity checks
Weaknesses CWE-918
References
Metrics cvssV4_0

{'score': 7.7, 'vector': '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'}

Weaknesses
  • CWE-918

    Server-Side Request Forgery (SSRF)

Sources

Status
PUBLISHED
Assigner
GitHub_P
Published
Updated
Nov 18, 2026, 5:37 PM
Reserved
Nov 17, 2026, 11:04 PM
Status
Received
Published
Nov 18, 2026, 2:17 AM
Modified
Nov 18, 2026, 6:19 PM