Cyber Resilience

CVE-2025-6769

Gitlab 15.1.0 – 18.1.6

Published
12 September 2025
Modified
20 September 2025
Patch / advisory
View advisory
CVSS Score v3.1 4.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS Score 0.0029 21th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-6769 is a medium-severity Exposure of Sensitive System Information to an Unauthorized Control Sphere (CWE-497) vulnerability in Gitlab Gitlab. Its CVSS base score is 4.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Data from Information Repositories (T1213); ranked at the 21th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to AC-3 (Access Enforcement) and AC-4 (Information Flow Enforcement) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A01:2025 Broken Access Control

EU & UK References

Vulnerability Data

An issue has been discovered in GitLab CE/EE affecting all versions from 15.1 before 18.1.6, 18.2 before 18.2.6, and 18.3 before 18.3.2 that could have allowed authenticated users to view administrator-only maintenance notes by accessing runner details through specific interfaces.

CWE(s)
CWE-497

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1213 Data from Information Repositories Collection
Adversaries may leverage information repositories to mine valuable information.
attack.mitre.org →
Why these techniques?

Info disclosure vuln directly enables access to restricted data in GitLab information repository (runner details).

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2025-6195Same product: Gitlab Gitlab
CVE-2026-3160Same product: Gitlab Gitlab
CVE-2024-10240Same product: Gitlab Gitlab
CVE-2026-8472Same product: Gitlab Gitlab
CVE-2024-6389Same product: Gitlab Gitlab
CVE-2025-1212Same product: Gitlab Gitlab
CVE-2026-5796Same product: Gitlab Gitlab
CVE-2026-8716Same product: Gitlab Gitlab
CVE-2026-0602Same product: Gitlab Gitlab
CVE-2023-2030Same product: Gitlab Gitlab

Affected Assets

gitlab
gitlab
15.1.0 — 18.1.6 · 15.1.0 — 18.1.6 · 18.2.0 — 18.2.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • AC-4 Information Flow Enforcement
  • AC-6 Least Privilege
Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)
  • 5 hardening rules · 4 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V14.1.2

Mitigating Controls (NIST 800-53 r5) AI

AC-3 Access Enforcement good match
prevent

Directly enforces access restrictions so that administrator-only maintenance notes cannot be retrieved by non-privileged users via runner details.

AC-4 Information Flow Enforcement partial match
prevent

Prevents unauthorized information flows that would otherwise expose sensitive maintenance notes to authenticated but non-admin users.

AC-6 Least Privilege partial match
prevent

Limits privileges so that ordinary users cannot obtain the elevated rights needed to view admin-only runner maintenance notes.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.AA-05 mostly match
prevents

Enforcing least-privilege access permissions directly prevents unauthorized actors from reaching sensitive system information.

PR.IR-01 mostly match
prevents

Protecting environments from unauthorized logical access stops exposure of internal system details to outsiders.

PR.PS-06 partial match
prevents

Secure-development practices reduce the chance of code paths that leak sensitive system information.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.7.3 Securing offices, rooms and facilities none match
none

Keeping internal maps, directories, and signage from public view prevents disclosure of system or facility details that could aid reconnaissance or targeted attacks.

References