cve.bz

CVE-2026-110288

5.3 mediumEPSS 0.2%

Medium (5.3). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

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
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-04. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-352 Cross-Site Request Forgery (Cross Site Reference Forgery)
OWASP Top 10
A01:2025 Broken Access Control
Published
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-110288 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-110288?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-110288?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-110288 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Versions

From the CNA's record in the CVE List.

ProductAffected
GitHub Enterprise Serverfrom 3.19.0 before 3.19.*
GitHub Enterprise Serverfrom 3.20.0 before 3.20.*
GitHub Enterprise Serverfrom 3.21.0 before 3.21.*
GitHub Enterprise Serverfrom 3.22.0 before 3.22.*

Fixed in

ProductFixed in
GitHub Enterprise Server3.19.14
GitHub Enterprise Server3.20.10
GitHub Enterprise Server3.21.8
GitHub Enterprise Server3.22.3

Attack patterns (CAPEC)

  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-111 JSON Hijacking (aka JavaScript Hijacking) Likelihood: High · Severity: High
  • CAPEC-462 Cross-Domain Search Timing Severity: Medium
  • CAPEC-467 Cross Site Identification Severity: Low

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON