Loading vulnerability…
CVE-2024-5258 is an authorization vulnerability in GitLab Community Edition and Enterprise Edition affecting versions 16.10 before 16.10.6, 16.11 before 16.11.3, and 17.0 before 17.0.1. The flaw affects pipeline authorization logic associated with the Set Pipeline Status of a Commit API. An authenticated attacker can use a crafted naming convention, including conditions involving mismatched SHA and pipeline identifier handling, to bypass intended authorization checks. This can cause GitLab to incorrectly accept operations that should have been rejected by normal pipeline access-control enforcement.
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 authorization bypass vulnerability in GitLab that allows an authenticated attacker to bypass pipeline authorization logic via crafted naming conventions in the Set Pipeline Status of a Commit API flow.
Medium-severity authorization flaw in GitLab pipeline-related API logic that can allow an authenticated attacker to bypass pipeline authorization checks via crafted naming conventions.
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.