BIT-gitlab-2026-103515

See a problem?
Import Source
https://github.com/bitnami/vulndb/tree/main/data/gitlab/BIT-gitlab-2026-103515.json
JSON Data
https://api.osv.dev/v1/vulns/BIT-gitlab-2026-103515
Aliases
Published
2026-10-29T09:09:49Z
Modified
2026-10-30T10:45:02Z
Summary
Incorrect Authorization in GitLab
Details

GitLab has remediated an issue in GitLab EE affecting all versions from 19.2 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1 that, when an instance administrator locked a group's Duo availability, an authenticated user with group Owner permissions could have re-enabled AI-backed data egress to a third-party service for that group and its descendant projects, due to insufficient granularity of the admin-lock enforcement controls.

Database specific
{
    "cpes":  [
        "cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:*",
        "cpe:2.3:a:gitlab:gitlab:*:*:*:*:enterprise:*:*:*"
    ],
    "severity":  "Low"
}
References

Affected packages

Bitnami / gitlab

Package

Name
gitlab
Purl
pkg:bitnami/gitlab

Severity

  • 2.7 (Low) CVSS_V3 - CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N CVSS Calculator

Affected ranges

Type
SEMVER
Events
Introduced
19.2.0
Fixed
19.3.6
Introduced
19.4.0
Fixed
19.4.3
Introduced
19.5.0
Fixed
19.5.1

Database specific

source
"https://github.com/bitnami/vulndb/tree/main/data/gitlab/BIT-gitlab-2026-103515.json"