Skip to main content
CVE-2026-131820VulnerabilityPublished

Server-side Request Forgery Vulnerability

Source GCVE Database

0
Compare
Authoritative record:CVE-2026-131820· High 7.7

Not known to be exploited · CVSS 7.7 High · fixed in 3.22.5 : patch Enterprise Server soon.

Data as of 18 Nov 2026, 05:18 UTC

CVSS 4.0 base score
7.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_P)CVSS 4.07.7
Patch
Available – fixed in 3.22.5, 3.21.10, 3.20.12
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 Enterprise Server to 3.22.5, 3.21.10 or 3.20.12.

Affected software

ProductAffectedFixed in
GitHubEnterprise ServerAffected
  • >=3.22.0 <3.22.5
Fixed in
  • 3.22.5
GitHubEnterprise ServerAffected
  • >=3.21.0 <3.21.10
Fixed in
  • 3.21.10
GitHubEnterprise ServerAffected
  • >=3.20.0 <3.20.12
Fixed in
  • 3.20.12

AI-suggested

Apply the official fixes by upgrading to GitHub Enterprise Server versions 3.22.5, 3.21.10, or 3.20.12 or later. Since this is not a cloud service, administrators must manually update affected instances to these fixed versions to remediate the vulnerability.

Description

A server-side request forgery (SSRF) vulnerability in GitHub Enterprise Server allowed an authenticated user with repository write access to send requests to internal services via Slack webhook validity checks. Exploitation required Secret Protection features 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. It was reported through the GitHub Bug Bounty program.

References

Community reviews

Loading reviews…