Skip to main content

GitHub Enterprise Server EUVDEUVD-2026-116582

| CVE-2026-110288 MEDIUM
Cross-Site Request Forgery (CSRF) (CWE-352)
2026-11-03 GitHub_P GHSA-34h8-2q57-6h55
5.3
CVSS 4.0 · Vendor: GitHub_P
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Lure signed-in Management Console operator
  2. Delivery
    Serve attacker-controlled web page
  3. Exploit
    Browser sends tokenless cross-site GET to integration removal endpoint
  4. Execution
    Delete Slack/Teams ChatOps config and credentials
  5. Impact
    Disrupt ChatOps notifications on config apply/reload

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Anti-CSRF tokens, SameSite cookies
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires two concrete preconditions stated in the description: (1) the GitHub Enterprise Server instance must have Slack and/or Microsoft Teams ChatOps integrations configured, and (2) an authenticated Management Console operator must visit attacker-controlled content while signed in to the Management Console, so that their browser issues the tokenless cross-site GET to the integration removal endpoint. Limiting factors: the attack needs that operator's active, authenticated session plus user interaction (UI:P), and it only takes effect - disrupting ChatOps notifications and commands - when configuration is applied or services are reloaded. If ChatOps integrations are not configured, there is nothing to delete. The impact is restricted to deletion of ChatOps configuration/provider credentials (integrity/availability), with no confidentiality exposure.

Impact

This is a medium-severity CSRF flaw (CWE-352, vendor CVSS 4.0 base 5.3) whose real-world priority is moderate rather than urgent. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:L) shows a network-reachable, low-complexity issue that needs no attacker privileges, but it is gated by passive user interaction (UI:P) and causes only limited integrity and availability impact with no confidentiality loss (VC:N) - consistent with an attacker who can delete ChatOps configuration/credentials but cannot read data or take over the system. There is no CISA KEV listing and no EPSS score is present in the input, so there is no signal of active or probable exploitation; no public exploit or PoC reference is provided either. The vuln.today decision label is 'this_month', which aligns with the medium technical impact and the non-trivial preconditions (configured ChatOps integrations plus a logged-in Management Console operator who must visit attacker content). Net: a legitimate issue to remediate in the normal monthly patch cycle, not an emergency; the biggest caveat is that exploitation depends on an operator's session and browser behavior, which the raw 'unauthenticated/AV:N' labeling can overstate if read in isolation.

Exploit ScenarioDerived

An attacker crafts a web page containing a cross-site GET request (e.g., an embedded resource) targeting the ChatOps integration removal endpoint and lures a GitHub Enterprise Server Management Console operator to visit it while that operator is signed in. Because the removal endpoint accepts the request without a CSRF token, the operator's browser silently deletes the configured Slack and Microsoft Teams ChatOps configuration and stored provider credentials. No public exploit identified at time of analysis; exploitation requires the operator interaction and complexity reflected in UI:P.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Nov 03, 2026

Cross-site request forgery in GitHub Enterprise Server (all versions prior to 3.23) allows an unauthenticated attacker to delete stored Slack and Microsoft Teams ChatOps configuration and provider credentials by luring a signed-in Management Console operator's browser into issuing a tokenless cross-site GET to the integration removal endpoint. Exploitation is not opportunistic: the instance must already have ChatOps integrations configured and the operator must visit attacker-controlled content while authenticated to the Management Console, with the disruption to notifications and commands materializing only when configuration is applied or services are reloaded. Severity is medium (vendor CVSS 4.0 base 5.3; assessed CVSS 3.1 AV:N/AC:L/PR:N/UI:R with low integrity and availability impact and no confidentiality exposure), no public exploit code has been identified at time of analysis, and fixes are available in 3.19.14, 3.20.10, 3.21.8 and 3.22.3.

RemediationAI

Vendor-released patches are available: upgrade to GitHub Enterprise Server 3.19.14, 3.20.10, 3.21.8 or 3.22.3 according to the branch in use, as documented in the release notes at https://docs.github.com/en/enterprise-server@3.19/admin/release-notes#3.19.14, https://docs.github.com/en/enterprise-server@3.20/admin/release-notes#3.20.10, https://docs.github.com/en/enterprise-server@3.21/admin/release-notes#3.21.8 and https://docs.github.com/en/enterprise-server@3.22/admin/release-notes#3.22.3. Because the attack path requires configured ChatOps integrations, instances that do not depend on Slack or Microsoft Teams ChatOps can remove that exposure by not configuring those integrations, at the cost of losing ChatOps notifications and commands; where integrations are required, the deletion only manifests when configuration is applied or services reloaded, so post-upgrade verification of the stored integration configuration and provider credentials is warranted. The stated prerequisite also means operators should not browse untrusted content in a browser session that is signed in to the Management Console.

Affected VersionsENISA

Enterprise Server 3.22.0 <3.22.*
Enterprise Server 3.20.0 <3.20.*
Enterprise Server 3.21.0 <3.21.*
Enterprise Server 3.19.0 <3.19.*

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a classic CWE-352 cross-site request forgery against the GitHub Enterprise Server Management Console, the administrative surface used to configure instance-wide settings including ChatOps integrations with Slack and Microsoft Teams. The integration removal endpoint accepts a state-changing GET request without a CSRF token, so a page hosted by an attacker can cause an already-authenticated operator's browser to send the request and have it accepted on the strength of the operator's session alone. Affected code is tracked as cpe:2.3:a:github:enterprise_server across every release before 3.23; the root cause class is the absence of request-origin/anti-forgery validation on a state-changing action, combined with the use of GET for a destructive operation. The affected state is the stored ChatOps configuration and the associated provider credentials, so the outcome is data loss rather than data disclosure - there is no confidentiality vector in either the vendor's or the assessed score. The precise request flow and any additional parameters beyond the tokenless cross-site GET are not described in the available sources.

Know when Github gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_P) PRIMARY 5.3 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N
vuln.today AI 5.4 MEDIUM

Classic CSRF: attacker is unauthenticated (PR:N) but needs the operator to visit content (UI:R); deletion of config/credentials gives limited integrity and availability impact and no confidentiality (C:N).

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_P).

CVSS VectorVendor: GitHub_P

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
Passive
Vulnerable system: Confidentiality
None
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Nov 04, 2026 - 02:16 EUVD
CVE Published
Nov 03, 2026 - 22:50 cve.org
MEDIUM 5.3

DescriptionCVE.org

A cross-site request forgery vulnerability was identified in GitHub Enterprise Server that allowed an unauthenticated attacker to delete stored Slack and Microsoft Teams ChatOps configuration and provider credentials by inducing an authenticated Management Console operator's browser to send a cross-site GET request to the integration removal endpoint without a CSRF token. Exploitation required configured ChatOps integrations and an operator visiting attacker-controlled content while signed in to the Management Console; deletion could disrupt ChatOps notifications and commands when configuration was applied or services reloaded. This vulnerability affected all versions of GitHub Enterprise Server prior to 3.23 and was fixed in versions 3.19.14, 3.20.10, 3.21.8, and 3.22.3. This vulnerability was reported via the GitHub Bug Bounty program.

Threat Intelligence Overview

Prevalence
High
widely deployed self-hosted enterprise DevOps platform
Data Quality
3 sources
Confidence: Low

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS N/A
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact· derived
High

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Request Forgery exploits the automatic credential inclusion behavior of web browsers.

More in Github

View all
CVE-2026-1699 CRITICAL POC
10.0 Jan 30

Supply chain vulnerability in Eclipse Theia GitHub Actions workflow. The preview.yml workflow uses pull_request_target w

CVE-2026-27941 CRITICAL POC
9.9 Feb 26

Supply chain attack vector in OpenLIT GitHub Actions workflows. The pull_request_target trigger with checkout enables ma

CVE-2026-22869 CRITICAL POC
9.8 Jan 13

Eigent multi-agent workflow CI pipeline (ci.yml) uses pull_request_target with checkout of untrusted PR code, enabling a

CVE-2024-0200 CRITICAL POC
9.8 Jan 16

An unsafe reflection vulnerability was identified in GitHub Enterprise Server that could lead to reflection injection. R

CVE-2022-24724 CRITICAL POC
9.8 Mar 03

cmark-gfm is GitHub's extended version of the C reference implementation of CommonMark. Rated critical severity (CVSS 9.

CVE-2024-9487 CRITICAL POC
9.5 Oct 10

An improper verification of cryptographic signature vulnerability was identified in GitHub Enterprise Server that allowe

CVE-2026-28215 CRITICAL POC
9.1 Feb 26

Unauthenticated infrastructure overwrite in Hoppscotch API development ecosystem before 2026.2.0. Attackers can overwrit

CVE-2018-1000600 HIGH POC
8.8 Jun 26

A exposure of sensitive information vulnerability exists in Jenkins GitHub Plugin 1.29.1 and earlier in GitHubTokenCrede

CVE-2026-30920 HIGH POC
8.6 Mar 10

OneUptime versions prior to 10.0.19 allow unauthenticated attackers to hijack GitHub App integrations across projects by

CVE-2026-25221 HIGH POC
8.1 Feb 02

PolarLearn versions 0-PRERELEASE-15 and earlier lack proper state parameter validation in OAuth 2.0 authentication, enab

CVE-2026-23644 HIGH POC
7.5 Jan 18

Path traversal in esm.sh CDN prior to version 0.0.0-20260116051925-c62ab83c589e allows unauthenticated remote attackers

CVE-2024-42471 HIGH POC
7.5 Sep 02

actions/artifact is the GitHub ToolKit for developing GitHub Actions. Rated high severity (CVSS 7.5), this vulnerability

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy