Security readout for executives and security teams
Plain-English summary
GitLab fixed a low-severity issue where a logged-in user could make repository content look different in the web interface than in downloads. This could mislead review or trust decisions, but the published CVSS limits impact to low integrity risk with no confidentiality or availability impact.
Executive priority
Schedule remediation through the normal GitLab patch process. Escalate only where GitLab hosts sensitive code, allows many authenticated users, or supports release workflows that depend on web-based content review.
Technical view
CWE-706 improper Git reference name resolution in GitLab CE/EE could allow an authenticated user, under certain conditions, to create inconsistent repository representations between web display and downloadable content. Affected ranges are from 16.5 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2.
Likely exposure
Exposure is limited to GitLab CE/EE instances running the affected version ranges. The attacker must be authenticated, and the CVSS vector requires user interaction, reducing broad unauthenticated risk.
Exploitation context
The source bundle references a HackerOne technical report, but KEV is false and no provided source states active exploitation in the wild. Treat this as a repository integrity and review-trust issue, not a confirmed campaign.
Researcher notes
The key technical condition is Git reference name resolution causing different content views across GitLab’s web interface and downloadable repository output. Public evidence in the bundle does not define broad impact beyond low integrity loss.
Mitigation direction
- Upgrade GitLab CE/EE to the remediated versions named by GitLab.
- Prioritize internet-facing and widely used shared GitLab instances.
- Check GitLab release guidance for any version-specific upgrade instructions.
- Review repository governance controls for untrusted authenticated users.
Validation and detection
- Inventory GitLab CE/EE versions across hosted and self-managed environments.
- Confirm instances are not in the affected version ranges.
- Review audit logs for unusual repository creation by low-trust authenticated users.
- Spot-check suspicious repositories for web-versus-download content inconsistencies.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-706: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2025-12506 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N2.11.4GitLabVulnerability scoring details
Base CVSS 3.1 score
3.5LowVector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- HackerOne Bug Bounty Report #3351460CVE reference, GitLab · technical-description, exploit
- https://gitlab.com/gitlab-org/gitlab/-/work_items/578988CVE reference, GitLab
- https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-1-2-released/CVE reference, GitLab
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Use of Incorrectly-Resolved Name or Reference
Use of Incorrectly-Resolved Name or Reference represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.