CyberSecBulletin
CVE-2026-1322NVD status: Analyzed

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.0 before 18.9.7…

CVE-2026-1322 is a high-severity vulnerability in GitLab, with a CVSS 3.1 base score of 8.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. The record lists versions 18.9.7, 18.10.6, 18.11.3 as the first without the flaw, so updating GitLab to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.31% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update GitLab to 18.9.7 or 18.10.6 or 18.11.3, whichever matches your release line, or a later version.

Affected products and versions

VendorProductAffected versionsFixed in
GitLabGitLab16.0 up to, but not including, 18.9.7; 18.10 up to, but not including, 18.10.6; 18.11 up to, but not including, 18.11.318.9.7, 18.10.6, 18.11.3

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.16.8MediumCNA (gitlab.com)
CVSS 3.18.1HighNVD

Official description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 16.0 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user with a read_api scoped OAuth application to create issues and add comments to issues in private projects due to improper authorization.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in GitLab

All GitLab vulnerabilities

Spotted an error? Tell us.