Cyber Resilience

CVE-2025-12653

Auth Bypass in Gitlab 18.3.0 – 18.4.5

Published
26 November 2025
Modified
10 December 2025
CVSS Score v3.1 6.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
EPSS Score 0.0028 20th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2025-12653 is a medium-severity Authentication Bypass by Spoofing (CWE-290) vulnerability in Gitlab Gitlab. Its CVSS base score is 6.5 (Medium).

Operationally, ranked at the 20th 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-14 (Permitted Actions Without Identification or Authentication) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 18.3 before 18.4.5, 18.5 before 18.5.3, and 18.6 before 18.6.1 that under specific conditions could have allowed an unauthenticated user to join arbitrary organizations by changing headers on…

more

some requests.

CWE(s)

Related Threats

CVEs Like This One

CVE-2024-6678Same product: Gitlab Gitlab
CVE-2024-1347Same product: Gitlab Gitlab
CVE-2023-2001Same product: Gitlab Gitlab
CVE-2023-2030Same product: Gitlab Gitlab
CVE-2026-13151Same product: Gitlab Gitlab
CVE-2024-1211Same product: Gitlab Gitlab
CVE-2023-5009Same product: Gitlab Gitlab
CVE-2023-0632Same product: Gitlab Gitlab
CVE-2024-2818Same product: Gitlab Gitlab
CVE-2023-6680Same product: Gitlab Gitlab

Affected Assets

gitlab
gitlab
18.6.0 · 18.3.0 — 18.4.5 · 18.3.0 — 18.4.5 · 18.5.0 — 18.5.3

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • AC-3 Access Enforcement
  • SI-10 Information Input Validation
  • AC-14 Permitted Actions Without Identification or Authentication
Detect
Catch it (NIST detect / respond)

Harden
Shrink the surface (DISA STIG)
  • 3 hardening rules · 3 OS baselines
Validate
Prove the fix (OWASP ASVS)
  • V6.4.3
  • V10.4.16
  • V10.5.1
  • V11.4.3

Mitigating Controls (NIST 800-53 r5) AI

prevent

Directly enforces authorization decisions on organization-join requests so that header manipulation cannot grant access without valid authentication.

prevent

Requires validation of HTTP headers used for authentication context, blocking the spoofing vector that allows unauthenticated joins.

prevent

Explicitly identifies and restricts actions (such as joining organizations) that may be performed without identification or authentication.

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-04 full match
prevents

Protecting, conveying, and verifying identity assertions specifically prevents the spoofing that enables authentication bypass.

PR.AA-03 mostly match
prevents

Requiring authentication of users/services/hardware directly counters spoofing-based bypass when strong methods are used.

PR.AA-02 partial match
prevents

Proofing and binding identities reduces spoofing opportunities during enrollment but does not address runtime authentication implementation flaws.

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.

degrades

Secure authentication control directly mitigates authentication bypass by spoofing.

degrades

Authentication information management directly addresses credential handling that prevents spoofing.

detects

Security testing can detect spoofing vulnerabilities but does not prevent them by itself.

prevents

Access control policy reduces spoofing opportunities but does not prescribe authentication mechanisms.

prevents

Identity management supports unique identities but does not guarantee resistance to spoofing.

prevents

Access rights assignment limits exposure but does not enforce authentication strength.

References