CISA added CVE-2026-115731, a deserialization flaw in Puppet report processing that lets an agent certificate holder run code on Puppet Server, to the KEV list on 17 November 2026; fixed in Puppet Enterprise 2026.0.1, 2025.12.1 and 2023.8.13.
GitHub Enterprise Server 3.22.5 and November patch releases fix high-severity flaws
EditorialBy TrustList Editorial
GitHub Enterprise Server 3.22.5, 3.21.10, 3.20.12 and 3.19.16, released on 17 November 2026, fix a list of high-severity flaws, from pre-receive hook sandbox escapes and SSH certificate checks to command injection in GitHub Pages.
- Cybersecurity
- DevOps
- Patch Management
About GitHub Enterprise Server 3.22.5 and November patch releases fix high-severity flaws
GitHub Enterprise Server 3.22.5 and November patch releases fix high-severity flaws
17 November 2026: GitHub has released GitHub Enterprise Server 3.22.5, together with patch releases for older supported branches: 3.21.10, 3.20.12 and 3.19.16, all dated the same day. The 3.22.5 release notes list nine fixes rated high, one medium and two low. GitHub Enterprise Server is the self-hosted version of GitHub, so these updates are for organisations that run it on their own infrastructure; github.com itself is patched by GitHub.
Not yet independently verified. The list of flaws below is from the release notes of 3.22.5. The 3.21.10, 3.20.12 and 3.19.16 releases carry the same date, but we did not check which of these flaws each older branch includes. GitHub says it has requested the CVE IDs, so some may not yet be published. No exploitation is reported. We will update this when it can be confirmed, and remove this note.
The high-severity fixes in 3.22.5
- Git is updated for CVE-2026-105437, CVE-2026-111760, CVE-2026-113408, CVE-2026-114466, CVE-2026-114467 and CVE-2026-114469. GitHub notes this was announced with the previous patch release but had not been fully resolved.
- CVE-2026-112740: in a cluster, a site administrator could run commands as the host git user on peer Git nodes, outside the pre-receive hook sandbox, through a crafted download URL for a custom hook environment.
- CVE-2026-116637: a site administrator could change host files with root privileges and disclose private repository data, because of weak path validation in pre-receive hook environment setup.
- CVE-2026-116643: an organisation member could read and change another user's private repositories through improper SSH certificate identity validation, on instances using built-in authentication with a trusted SSH certificate authority.
- CVE-2026-111801: an authenticated user could read private file paths and source excerpts by supplying another repository's review-thread IDs, with no victim interaction.
- CVE-2026-110307: an ownership-check bypass let a session whose numeric user ID matched an enterprise's ID generate private keys for that enterprise's GitHub Apps.
- CVE-2026-131800: stored HTML in a custom-property option could add an SSH key to another member's account.
- CVE-2026-131820: server-side request forgery in Slack webhook validity checks could lead to remote code execution on the appliance, where secret scanning validity checks are enabled.
- CVE-2026-130824: OS command injection in the GitHub Pages deployment process allowed commands to run as the Pages service user.
The medium fix, CVE-2026-131647, closes a branch-protection bypass when resolving pull request conflicts. GitHub says it has requested the CVE IDs, and the flaws were reported through its bug bounty programme.
Who should move first
Several flaws need an existing account, often a site administrator or a user with write access, so the main risk is from insiders, compromised accounts and the large number of people with write access on a busy instance. That is a reason to patch promptly, not to wait. Clusters, instances using SSH certificate authorities, and those with secret scanning validity checks or GitHub Pages switched on are directly named.
What administrators should do
Plan the upgrade to the latest patch release on your branch in your next maintenance window, taking a backup first, and follow GitHub's upgrade steps for clusters if you run one. If you are on 3.19, check GitHub's support dates for that branch and plan a move to a newer feature release. Read the release notes for your own branch to confirm which fixes it carries, then check the version in the Management Console after the upgrade. While you wait, review who holds site administrator rights and remove any that are no longer needed.
Sources
- GitHub Docs: GitHub Enterprise Server 3.22 release notes (3.22.5), 17 November 2026
- GitHub Docs: GitHub Enterprise Server 3.21 release notes, 17 November 2026
- ACN (Italian national cybersecurity agency): vulnerabilities fixed in GitHub Enterprise Server, 18 November 2026
Categories & features
- Cybersecurity
- DevOps
- Patch Management
TrustList Weekly
The week in software and IT, in one email
The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.
You may be interested in
One of the four high-severity bugs let workspace users read Kubernetes Secrets from other namespaces; GitLab.com is already patched and Dedicated customers need do nothing.
One lets a user who can view users or audit events become an administrator, and turns critical where guest access is on. Patches shipped in September; Octopus Cloud is already fixed.
Releases 3.19.14, 3.20.10, 3.21.8 and 3.22.3 fix a use-after-free that lets an SSH user run commands as the Git service, and an incomplete earlier fix that let Dependabot write Actions workflows.
A client with no credentials can tie up memory, file descriptors and backend connections on Traefik 3.7.14 to 3.7.16 and 2.11.58 to 2.11.60, whether or not NTLM is used. It is the latest of more than a dozen fixes since 6 October.
Seven are rated high, including an account takeover through OAuth2 auto-linking and fork workflows that receive repository secrets. Every release up to 28.2.0 is affected; there is no backport line.
The GitLab regex flaw lets an unauthenticated user run code through a CI/CD configuration; the Cisco flaw reloads ASA and FTD firewalls. Both entered the exploited list on 29 October with a three-day deadline.
The workflow tool's 28 October advisories cover a deprecated Code node escape (CVSS 8.7), expression sandbox isolation and a bundled GraphicsMagick reachable through webhooks; 3.0.1 and 2.46.1 carry the fixes.
More on TrustList
Everything here links back to the same verified catalogue. Pick your next stop.
- More CybersecurityThe ranking for this subject
- CompaniesAgencies, consultancies and IT service providers, ranked by verified reviews.
- ProductsSoftware and SaaS with pricing, features, integrations and alternatives.
- AwardsAnnual recognition decided by verified reviews and an independent jury.
- LaunchesNew products and releases, voted up by the community every day.
- AI ModelsBenchmark scores and community ratings for every major model.
- RequestsBuyers describe what they need; vendors respond directly.
- PeopleReviewers, authors and makers with public profiles.
- ComparePut up to four listings side by side before you shortlist.