GitLab RCE PoC Published: No Admin Rights Required
A working RCE exploit for self-managed GitLab 18.11.3 is now public. Any authenticated user can execute server commands as git — no admin rights needed.
airgap Working PoC published. Researcher Yuhang Wu (depthfirst) today released a proof-of-concept exploit chain for self-managed GitLab 18.11.3 that executes commands as the git system user.
Barrier to exploitation: a standard authenticated GitLab account. No administrator rights, no CI runner access, no victim interaction required.
Confirmed: Named researcher, named platform version, public PoC. Full disclosure via The Hacker News. The attack path involves specially crafted Jupyter notebook files submitted through GitLab’s normal commit workflow, with code execution triggered during diff processing.
Active exploitation in the wild: Unconfirmed as of publication. Working public exploit is out. Treat the window accordingly.
What git-level access means: The git system user is the account GitLab’s application runs under on most self-managed installs. It has access to all repositories on the server — private ones included — and to CI/CD pipeline configuration stored on disk. That commonly means source code across the entire organization, and frequently embedded secrets: API keys, deployment credentials, webhook tokens stored in repository variables or config files. Not root. Depending on what lives there, not far from it.
CVE: Not present in the researcher’s disclosure at time of writing. No GitLab security advisory has been published at this writing. Monitor GitLab’s security releases page and NVD for a formal identifier.
Affected scope: Self-managed GitLab instances running 18.11.3. GitLab.com (hosted) is not mentioned in the researcher’s disclosure — treat hosted as unaffected unless GitLab issues guidance to the contrary.
Recommended actions: Restrict network exposure on self-managed instances where possible. Watch for a GitLab security advisory addressing Jupyter notebook diff handling. Full technical disclosure is available at The Hacker News — we are not reproducing the exploit chain here.
This article will be updated as GitLab issues a formal advisory or CVE assignment. For context on GitLab’s past RCE exposure history, see our ExifTool RCE explainer.
Found this useful? Share it.
