CVE-2026-1322: OAuth Authorization Bypass in GitLab
Plattform
gitlab
Komponente
gitlab
Behoben in
18.11.3
CVE-2026-1322 is a security vulnerability in GitLab CE/EE that allows an authenticated user with a read_api scoped OAuth application to bypass authorization checks and create issues and add comments to private projects. This improper authorization control can lead to unauthorized access and potential data leakage. The vulnerability affects versions from 16.0 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3. A fix is available in GitLab 18.11.3.
Auswirkungen und Angriffsszenarien
An attacker exploiting this vulnerability could leverage a readapi scoped OAuth application to gain unauthorized access to private GitLab projects. They could create new issues, add comments, and potentially manipulate project data without proper authorization. This could lead to data breaches, intellectual property theft, or disruption of project workflows. The impact is amplified in organizations with sensitive private projects containing confidential code, financial data, or strategic plans. While the vulnerability requires an existing OAuth application with the readapi scope, the ease of creating such applications makes it a potentially widespread risk.
Ausnutzungskontext
CVE-2026-1322 was published on 2026-05-14. Its severity is rated as Medium (CVSS 6.8). No public exploits or proof-of-concept code are currently known. The vulnerability is not listed on KEV or EPSS, suggesting a low to medium probability of exploitation. Organizations should prioritize patching to mitigate the risk.
Bedrohungsanalyse
Exploit-Status
CISA SSVC
CVSS-Vektor
Was bedeuten diese Metriken?
- Attack Vector
- Netzwerk — aus der Ferne über das Internet ausnutzbar. Kein physischer oder lokaler Zugriff erforderlich.
- Attack Complexity
- Hoch — erfordert eine Race-Condition, Nicht-Standard-Konfiguration oder spezifische Umstände.
- Privileges Required
- Niedrig — jedes gültige Benutzerkonto ist ausreichend.
- User Interaction
- Keine — automatischer und lautloser Angriff. Das Opfer tut nichts.
- Scope
- Unverändert — Auswirkung auf das anfällige Komponente beschränkt.
- Confidentiality
- Hoch — vollständiger Vertraulichkeitsverlust. Angreifer kann alle Daten lesen.
- Integrity
- Hoch — Angreifer kann beliebige Daten schreiben, ändern oder löschen.
- Availability
- Keine — kein Verfügbarkeitseinfluss.
Betroffene Software
Schwachstellen-Klassifikation (CWE)
Zeitleiste
- Reserviert
- Veröffentlicht
Mitigation und Workarounds
The primary mitigation for CVE-2026-1322 is to upgrade GitLab to version 18.11.3 or later. If an immediate upgrade is not feasible, consider reviewing and restricting the permissions granted to OAuth applications, specifically limiting the scope to only what is absolutely necessary. Implement stricter access controls within GitLab to limit the potential impact of unauthorized actions. Monitor GitLab audit logs for suspicious activity related to issue creation and commenting, particularly from OAuth applications. After upgrading, confirm the fix by verifying that users with read_api OAuth applications can no longer create issues or add comments to private projects.
So behebenwird übersetzt…
Actualice GitLab a la versión 18.9.7 o superior, 18.10.6 o superior, o 18.11.3 o superior para mitigar la vulnerabilidad. Esta actualización corrige una falla de autorización que permitía a usuarios autenticados con aplicaciones OAuth crear y comentar en issues de proyectos privados.
Häufig gestellte Fragen
What is CVE-2026-1322 — OAuth Authorization Bypass in GitLab?
CVE-2026-1322 is a medium-severity vulnerability in GitLab affecting versions 16.0.0–18.11.3. It allows authenticated users with read_api OAuth apps to create issues and comments in private projects, bypassing authorization controls.
Am I affected by CVE-2026-1322 in GitLab?
If you are running GitLab versions 16.0.0 through 18.11.3 and use OAuth applications with the read_api scope, you are potentially affected by this vulnerability. Check your GitLab version immediately.
How do I fix CVE-2026-1322 in GitLab?
Upgrade GitLab to version 18.11.3 or later to resolve this vulnerability. Review and restrict OAuth application permissions as a temporary mitigation.
Is CVE-2026-1322 being actively exploited?
As of the current publication date, there are no known active exploits or public proof-of-concept code for CVE-2026-1322, but proactive patching is still recommended.
Where can I find the official GitLab advisory for CVE-2026-1322?
Refer to the official GitLab security advisory for CVE-2026-1322 at [https://gitlab.com/security/advisories/CVE-2026-1322](https://gitlab.com/security/advisories/CVE-2026-1322).
Ist dein Projekt betroffen?
Lade deine Abhängigkeitsdatei hoch und erfahre sofort, ob dich diese und andere CVEs treffen.
Jetzt testen — kein Konto
Laden Sie ein Manifest hoch (composer.lock, package-lock.json, WordPress Plugin-Liste…) oder fügen Sie Ihre Komponentenliste ein. Sie erhalten sofort einen Schwachstellenbericht. Das Hochladen einer Datei ist nur der Anfang: Mit einem Konto erhalten Sie kontinuierliche Überwachung, Slack/email-Benachrichtigungen, Multi-Projekt- und White-Label-Berichte.
Abhängigkeitsdatei hier ablegen
composer.lock, package-lock.json, requirements.txt, Gemfile.lock, pubspec.lock, Dockerfile...