Skip to main content
VulnerabilityPublished

CVE-2026-131820: GitHub Enterprise Server · Server-Side Request Forgery

Affects GitHub Enterprise ServerSource CVE Database V5

0
Compare

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

Data as of 18 Nov 2026, 01:35 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 GitHub 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 GitHub Enterprise Server to versions 3.20.12, 3.21.10, or 3.22.5 or later. These versions contain patches that resolve the SSRF vulnerability. No other mitigation is indicated or required beyond applying these updates.

Description

CVE-2026-131820 is a server-side request forgery (SSRF) vulnerability in GitHub Enterprise Server that allowed authenticated users with repository write access to send requests to internal services via Slack webhook validity checks. Exploitation required specific secret protection features enabled. The flaw could potentially lead to remote code execution on the appliance. It affected versions prior to 3.20.12, 3.21.10, and 3.22.5 and was fixed in those releases.

References

Community reviews

Loading reviews…