GitLab 19.5.6 security patch fixes separate flaws involving protected CI/CD variables, Kubernetes Secrets, wiki pages and Error Tracking. GitLab released CE and EE versions 19.5.6, 19.4.8 and 19.3.9 on November 16, 2026.
Self-managed administrators should update the branch they run and verify the installed version. GitLab says GitLab.com is already patched and GitLab Dedicated customers need no action for this release.
Which GitLab 19.5.6 Security Patch Version Do You Need?
| Current branch | Fixed CE/EE release |
|---|---|
| 19.5 | 19.5.6 |
| 19.4 | 19.4.8 |
| 19.3 or an affected earlier release | 19.3.9 or a supported later fixed release |
These are GitLab’s November 16 fixed releases, not four different fixes for four separate deployment methods. GitLab says an issue without a named deployment type applies to all deployment types.
Record each instance’s edition, branch and running version before the change. Use Vulnerability Intelligence platform when prioritizing these GitLab vulnerabilities across the affected instances. Follow the organization’s patch management process to schedule and verify the upgrade.
Why CI Secrets and Kubernetes Access Need Separate Review
GitLab says CVE-2026-18241 is a race condition in pipeline job authorization. Under certain conditions, an authenticated user could access protected CI/CD variables and resources; the issue affects CE/EE from 9.3 through the vulnerable branch releases.
CVE-2026-97187 concerns a different authorization boundary. GitLab says an authenticated user could read Kubernetes Secrets in other namespaces through workspaces when a cluster is connected by the GitLab agent.
That Kubernetes issue affects CE/EE from 17.6 through the vulnerable branch releases. We recommend prioritizing connected clusters and projects with sensitive protected variables, then reviewing access evidence before deciding whether credentials need rotation.
Brandefense Blackhole counted 933 dark-chat posts mentioning GitLab from August 19 to November 17, 2026. This product-wide discussion count is a risk-context signal; it does not identify activity against these CVEs or establish exploitation.
How Do the Wiki and Error Tracking Flaws Differ?
GitLab describes CVE-2026-105739 in wiki pages and CVE-2026-108153 in Error Tracking pages as separate cross-site scripting flaws. Improper input sanitization could let an authenticated user run JavaScript in another viewer’s browser under certain conditions.
The wiki issue affects CE/EE from 17.2; the Error Tracking issue affects CE/EE from 16.1. Both are fixed by the branch releases in the table, according to GitLab’s patch advisory.
GitLab rates both browser issues high, alongside the CI/CD authorization flaw and the workspaces issue. Its notice gives CVSS 3.1 scores of 8.7 for each browser flaw, 8.2 for CI/CD and 7.6 for workspaces; it does not give CVSS 4.0 scores.
Do This Now on Self-Managed GitLab
- Inventory instancesIdentify self-managed CE/EE instances, their branches and installed versions.
- Upgrade the branchInstall 19.5.6, 19.4.8 or 19.3.9 as appropriate to the supported branch.
- Verify the resultConfirm the running version after the service returns and record upgrade exceptions.
- Review sensitive pathsCheck protected pipeline variable access and GitLab-agent-connected Kubernetes workspaces for unexpected access.
- Escalate evidencePreserve relevant records and rotate affected credentials when the review indicates possible disclosure.
Use a vulnerability management workflow to track instances that miss the rollout. Assign an owner and follow-up date to each exception.
GitLab’s release notice describes the flaws and fixed versions but does not establish active exploitation or actor attribution. Treat the post-upgrade access review as a precaution, and use an incident response plan if evidence warrants investigation.
Frequently Asked Questions
Which GitLab versions contain the November 16 security fixes?
GitLab lists CE/EE 19.5.6, 19.4.8 and 19.3.9. Choose the fixed release for your supported branch.
Do GitLab.com or GitLab Dedicated customers need to upgrade?
GitLab says GitLab.com is already patched. It says GitLab Dedicated customers need no action for this release.
Does the release notice confirm these flaws were exploited?
GitLab describes the flaws and fixes. Its November 16 notice does not establish active exploitation or actor attribution for the four issues covered here.
