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

Published Nov 18, 2026
·
Updated

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.

Affected Software

1 affected component
GitHub GitHub Enterprise Server<3.22.5, <3.21.10, <3.20.12

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.22.5
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.21.10
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 3.20.12

Event History

Nov 18, 2026
CVE Published
via MITRE·01:08 AM
Data Sourced
via MITRE·01:08 AM
DescriptionWeakness
Data Sourced
via NVD·02:17 AM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed to this issue?

GitHub Enterprise Server deployments running versions earlier than 3.23 are affected if Secret Protection, secret scanning, and validity checks for partner patterns are enabled. The issue is fixed in 3.20.12, 3.21.10, and 3.22.5.

2

What level of access does an attacker need?

An attacker must be authenticated and have write access to a repository. No user interaction is required.

3

What can an attacker do through this vulnerability?

The attacker can use Slack webhook validity checks to cause the appliance to send requests to internal services. This SSRF condition could potentially lead to remote code execution on the appliance.

4

What should teams do if they cannot immediately upgrade?

The described exploitation path requires Secret Protection with secret scanning and partner-pattern validity checks enabled. Disabling the required validity-check capability may remove the stated prerequisite until an update can be applied.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203