Loading vulnerability…
CVE-2025-12506 is a low-severity vulnerability in GitLab Community Edition and Enterprise Edition caused by improper handling of Git reference name resolution. In affected versions, an authenticated user could, under certain conditions, create a repository in which the content rendered in the GitLab web interface differed from the content obtained through download mechanisms. The issue affects all versions from 16.5 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2. The flaw stems from ambiguity in resolving tag or branch references, creating a mismatch between how repository content is interpreted and presented across different access paths.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A lower-severity GitLab vulnerability caused by improper handling of Git references, leading to discrepancies between displayed and downloadable repository content.
A low-severity Git reference ambiguity vulnerability in GitLab CE/EE that could let an authenticated user create a repository whose web-displayed content differs from downloadable content.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.