Advisory severityLow2.7Red Hat Linux

Low [CVE-2026-6352] Auditor-level users can modify compliance records via improper authorization in GraphQL

This low-severity Red Hat Linux advisory covers CVE-2026-6352.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-6352 Source published Jul 8, 2026Source updated Jul 8, 2026

VulniPulse record published Jul 13, 2026Record updated Jul 19, 2026

CVE-2026-6352

Affected products & platforms

Red Hat LinuxUnclassified

Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Get CVE alerts See app features

Summary

GitLab has remediated an issue in GitLab EE affecting all versions from 18.2 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user with auditor-level access to modify compliance violation records due to improper authorization on certain GraphQL operations.

A flaw was found in GitLab Enterprise Edition (EE). This was possible due to improper authorization on certain GraphQL operations, allowing them to bypass intended access controls.

Red Hat severity: Low — CVSS 2.7 (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N). Weakness: CWE-639.

Red Hat lists OpenShift Pipelines; Red Hat OpenShift Container Platform 4 as not affected.

Affected versions

< 18.2
< 18.11.7
< 19.0
< 19.0.4
< 19.1
< 19.1.2

Official advisory · high-confidence parse· fetched 21 days ago·verify at source

Fixed versions

No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.

Official advisory · high-confidence parse· fetched 21 days ago·verify at source

Mitigation

The source record does not include mitigation steps. That is not a statement that no fix exists — read the vendor advisory below for the authoritative guidance.

Official advisory · high-confidence parse· fetched 21 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.