Loading vulnerability…
CVE-2024-10925 is an improper authorization vulnerability in GitLab Enterprise Edition that affects versions 16.2 through before 17.7.6, 17.8 through before 17.8.4, and 17.9 through before 17.9.1. The flaw allows a user with the Guest role to read Security policy YAML that should not be accessible at that privilege level. The issue stems from an authorization check failure in access control enforcement for security policy data, resulting in unintended disclosure of policy configuration content.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A medium-severity improper authorization vulnerability in GitLab EE that allows a Guest user to read Security policy YAML.
A medium-severity authorization flaw in GitLab EE that allows a Guest user to read Security policy YAML.
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.