CVE-2026-16553: GitLab has remediated an issue in GitLab EE affecting all versions from 18.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed some...

Medium CVSS 5.4

CVE id
CVE-2026-16553
Published
Last modified

Affected packages

PackageAffected versionsFixed in
GitLab EE
Runtimes and servers
>= 18.8.0, < 19.0.5
>= 19.1.0, < 19.1.3
19.0.5, 19.1.3

How to fix it

Upgrade GitLab EE to the fixed release of the line you run: 19.0.5, 19.1.3.

gitlab-rake gitlab:env:info
  • Upgrade your self-managed GitLab EE (the gitlab/gitlab-ee image tag or the gitlab-ee package) to the patched release of your series.

A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.

Details

GitLab has remediated an issue in GitLab EE affecting all versions from 18.8 before 19.0.5, 19.1 before 19.1.3, and 19.2 before 19.2.1 that under certain conditions could have allowed some sensitive information to be disclosed to an unintended host due to improper handling of upstream requests in virtual registries.

References

Am I affected?

Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.

or paste its content

Needed when you paste. package.json and pyproject.toml only have version ranges: use the lockfile next to them.

Only package names and versions are checked; the file itself is not kept. We use your email to send this report and nothing else unless you tick the box above. Privacy policy.

About this data

Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.