Read the docs

Sensitive cache content exposes confidential GitLab issue titles

Priority LOW 16CWE-524Published · Updated

Key facts

Attack vector
Network
Privileges required
Low
User interaction
Required
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
Low · None · None
Fix status
Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA.

Summary

GitLab CE and EE from 15.0 before 19.3.6, from 19.4 before 19.4.3, and from 19.5 before 19.5.1 are affected. A viewer-independent fragment cache key causes per-user redacted content to be shared across all users, which exposes information cached in CWE-524. When a merge request in a public project references a confidential issue from a private project, an authenticated user with no project membership can read the confidential issue's title. CISA does not list the flaw in KEV, but the references include a public exploit link.

Written with Claude Haiku 5.5 from the sources below · 2026-10-30

Description from the CNA

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.0 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when a merge request in a public project referenced a confidential issue from a private project, an authenticated user with no project membership could have read the confidential issue's title, due to a viewer-independent fragment cache key that incorrectly shared per-user-redacted rendered content across all users.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00217 12th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by the CNA
Fix Fixed GitLab (GitLab): 19.3.6, 19.4.3, 19.5.1

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
GitLabGitLab15.0 to before 19.3.6; 19.4 to before 19.4.3; 19.5 to before 19.5.119.3.6, 19.4.3, 19.5.1Patch availableCNA
  • GitLab VendorGitLab Affected 15.0 to before 19.3.6; 19.4 to before 19.4.3; 19.5 to before 19.5.1 Fixed in 19.3.6, 19.4.3, 19.5.1 Patch available CNA

CPE configurations NVD · 6

CPEVersionsRoleVendor
cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*15.0.0 to before 19.3.6VulnerableGitLab
cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*15.0.0 to before 19.3.6VulnerableGitLab
cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:*19.4.0 to before 19.4.3VulnerableGitLab
cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*19.4.0 to before 19.4.3VulnerableGitLab
cpe:2.3:a:gitlab:gitlab:19.5.0:*:*:*:community:*:*:*19.5.0VulnerableGitLab
cpe:2.3:a:gitlab:gitlab:19.5.0:*:*:*:enterprise:*:*:*19.5.0VulnerableGitLab
  • cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:* Versions 15.0.0 to before 19.3.6 Vulnerable ·GitLab
  • cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:* Versions 15.0.0 to before 19.3.6 Vulnerable ·GitLab
  • cpe:2.3:a:gitlab:gitlab:*:*:*:*:community:*:*:* Versions 19.4.0 to before 19.4.3 Vulnerable ·GitLab
  • cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:* Versions 19.4.0 to before 19.4.3 Vulnerable ·GitLab
  • cpe:2.3:a:gitlab:gitlab:19.5.0:*:*:*:community:*:*:* Versions 19.5.0 Vulnerable ·GitLab
  • cpe:2.3:a:gitlab:gitlab:19.5.0:*:*:*:enterprise:*:*:* Versions 19.5.0 Vulnerable ·GitLab

Remediation

Upgrade GitLab to 19.3.6, 19.4.3, or 19.5.1, depending on the release branch in use. The sources list no fixed version for GitLab outside these branches.

Written with Claude Haiku 5.5 from the sources below · 2026-10-30

  • Fix · CNA GitLab (GitLab) Fixed in 19.3.6, 19.4.3, 19.5.1

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    GitLab 19.3.6, 19.4.3, 19.5.1

    11 records Highest priority Priority LOW 11 LOW

    Other records, highest priority first

    • TI-2026-79058 LDAP injection in GitLab lets users take over LDAP-backed accountsPriority LOW 38
    • TI-2026-79063 Cache poisoning in GitLab OAuth/OIDC discovery redirects flowsPriority LOW 32
    • TI-2026-79055 Incorrect authorization in GitLab lets read_api tokens create work itemsPriority LOW 32

Timeline

  1. 2026-10-21 Threatist record created from CVE-2026-105711
  2. 2026-10-22 Alias added: GHSA-5jh8-pw64-jw5v
  3. 2026-10-30 CISA SSVC decision points changed

References

  • TI-2026-71508 Integer overflow in GitLab allows code execution on the server KEVCVSS 3.1CRITICAL 10.0
  • TI-2026-58817 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLab KEVCVSS 3.1CRITICAL 10.0
  • TI-2023-06425 Weak Password Recovery Mechanism for Forgotten Password in GitLab KEVCVSS 3.1CRITICAL 10.0
  • TI-2021-05191 Code injection in GitLab KEVCVSS 3.1CRITICAL 10.0
  • TI-2021-05161 Server-side request forgery in GitLab KEVCVSS 3.1CRITICAL 9.8
  • TI-2022-02763 Injection in GitLab CVSS 3.1CRITICAL 9.9
See all 1506 →

Sources