Skip to main content
Mallory
← Back to News
widely-deployed-product-advisoryinternet-facing-service-vulnerabilityend-of-life-software

GitHub Enterprise Server Security Updates Address Vulnerabilities Across Four Release Branches

Patch & Detection Intelligence · 4 sources · Updated 14d ago · First seen Nov 4, 2026

GitHub Enterprise Server Security Updates Address Vulnerabilities Across Four Release Branches

The Canadian Centre for Cyber Security issued advisory AV26-1126 warning of vulnerabilities affecting four GitHub Enterprise Server release branches. Affected installations include versions earlier than 3.19.14, 3.20.10, 3.21.8, and 3.22.3 in their respective branches. The Cyber Centre urged administrators to review GitHub’s release information and apply necessary updates. The notice does not identify specific CVEs, severity ratings, vulnerability impacts, or exploitation activity.

Administrators should inventory deployed versions and prioritize upgrades to the applicable updated releases, checking GitHub’s release notes for prerequisites. GitHub’s lifecycle documentation states that it supports at least its four most recent feature releases; the listed support end dates for branches 3.17 and 3.18 have already passed. Documentation retained for unsupported versions is not maintained or updated. Upgrade planning should also account for compatible CodeQL CLI and GitHub Actions Runner versions, including minimum self-hosted runner requirements. Ephemeral runners with automatic updates disabled must be upgraded before upgrading GitHub Enterprise Server.

Patch this, or something else?See real exploitation activity before you spend the cycle.
Triage this advisory
Event timeline

How this story unfolded

Events from the most recent confirmed update back to the earliest known activity.

5 events · Dec 9, 2025 – Nov 4, 2026
  1. Nov 4, 202615d ago

    Canadian Cyber Centre issues GitHub security advisory AV26-1126

    The Canadian Centre for Cyber Security issued AV26-1126, identifying vulnerabilities affecting GitHub Enterprise Server as of November 3 in branches 3.19 through 3.22 before versions 3.19.14, 3.20.10, 3.21.8, and 3.22.3, respectively. It urged administrators to review GitHub's release information and apply necessary updates; the notice supplied no CVE identifiers, severity ratings, technical impacts, or exploitation details.

    GitHub security advisory (AV26-1126) - Malware News - Malware Analysis, News and Indicators
  2. Reported Jan 1, 202611mo ago

    GitHub releases Enterprise Server 3.22

    GitHub released Enterprise Server 3.22, the newest release branch subsequently covered by advisory AV26-1126.

    GitHub Enterprise Server releases - GitHub Enterprise Server 3.19 Docs
  3. Reported Jan 1, 202611mo ago

    GitHub releases Enterprise Server 3.21

    GitHub released Enterprise Server 3.21, which was later included among the branches affected by the vulnerabilities described in advisory AV26-1126.

    GitHub Enterprise Server releases - GitHub Enterprise Server 3.19 Docs
  4. Reported Jan 1, 202611mo ago

    GitHub releases Enterprise Server 3.20

    GitHub released Enterprise Server 3.20, another release branch subsequently covered by advisory AV26-1126.

    GitHub Enterprise Server releases - GitHub Enterprise Server 3.19 Docs
  5. Dec 9, 20251y ago

    GitHub releases Enterprise Server 3.19

    GitHub released Enterprise Server 3.19, one of the release branches later identified as affected by vulnerabilities in advisory AV26-1126.

    GitHub Enterprise Server releases - GitHub Enterprise Server 3.19 Docs
Linked entities

Related entities

Vulnerabilities, threat actors, malware, products, organizations, and breaches Mallory has linked to this story.

Open in app →

Affected products

1 linked
Github Enterprise Server
Do you run this?See real exploitation activity behind this advisory so you can triage it against everything else in the queue.
Prioritize This Patch
Mallory platform

See the full picture, correlated to your attack surface.

This page covers what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which threat actors are using it right now, and what to deploy next.

Exposure mappingMap indicators from this story to your assets and identify affected systems in minutes.
Threat actor evidenceEvery observed campaign, victim, and pivot linked to actors named in this story.
Associated malwareMalware, exploits, and IOCs connected to the activity described here.
Detection signaturesYARA, Sigma, and Snort rules deployed to your SIEM as soon as they’re published.
Scheduled alertsGet matching new stories delivered to your team as they break, not the next morning.
AI threadsAsk questions about this story and take action on the answers.