---
title: "#gitlab articles | Hashnode"
description: "GitLab is a web-based Git-repository manager with wiki and issue-tracking features, using an open-source license, developed by GitLab Inc. The software was w..."
url: "https://hashnode.com/tag/gitlab"
---

Tag

# #gitlab

1,187 posts · 6,386 followers

[Mo' Claudius](https://hashnode.com/@KodedMo) · [1d ago](https://hashnode.com/posts/patch-your-self-hosted-gitlab-anatomy-of-the-ai-gateway-rce/6afa1bed1d6e9bb93f076539)

### [Patch Your Self-Hosted GitLab: Anatomy of the AI Gateway RCE](https://kodedmo.dev/patch-your-self-hosted-gitlab-anatomy-of-the-ai-gateway-rce?utm_source=hashnode&utm_medium=feed)

The critical October flaw was not in GitLab itself. It was in the AI Gateway beside it, a separate service with its own versions, and patching the application never touched it.

19 min read · [kodedmo.dev](https://kodedmo.dev/patch-your-self-hosted-gitlab-anatomy-of-the-ai-gateway-rce?utm_source=hashnode&utm_medium=feed)

[Atul Vishwakarma](https://hashnode.com/@vatul16) · [6d ago](https://hashnode.com/posts/gitlab-flow-guide/6af28d0fbc81d549b1f0fbc5)

### [GitLab Flow: The Middle Ground Between GitFlow and GitHub Flow](https://atulcodes.hashnode.dev/gitlab-flow-guide?utm_source=hashnode&utm_medium=feed)

Environment branches, release branches, or a production branch: how to pick the GitLab Flow variant that matches the way you deploy.

6 min read · [atulcodes.hashnode.dev](https://atulcodes.hashnode.dev/gitlab-flow-guide?utm_source=hashnode&utm_medium=feed)

[AI CodeOps](https://hashnode.com/@aicodeops) · [Nov 4](https://hashnode.com/posts/ai-coding-agents-beyond-github-gitlab-bitbucket-gitea-and-forgejo/6aeb8c1dac6d7c68da6d641f)

### [AI Coding Agents Beyond GitHub: GitLab, Bitbucket, Gitea and Forgejo](https://aicodeops.hashnode.dev/ai-coding-agents-beyond-github-gitlab-bitbucket-gitea-and-forgejo?utm_source=hashnode&utm_medium=feed)

Most AI coding agents assume your code lives on GitHub. A lot of it doesn't. Here's what it takes to run gated AI changes on the Git host you already use. If you read the docs of most AI coding agents

4 min read · [aicodeops.hashnode.dev](https://aicodeops.hashnode.dev/ai-coding-agents-beyond-github-gitlab-bitbucket-gitea-and-forgejo?utm_source=hashnode&utm_medium=feed)

[AI CodeOps](https://hashnode.com/@aicodeops) · [Nov 4](https://hashnode.com/posts/how-to-gate-ai-written-pull-requests-in-github-actions-and-gitlab-ci/6aeb8b9e4fbb31b13b2eb3a0)

### [How to Gate AI-Written Pull Requests in GitHub Actions and GitLab CI](https://aicodeops.hashnode.dev/how-to-gate-ai-written-pull-requests-in-github-actions-and-gitlab-ci?utm_source=hashnode&utm_medium=feed)

AI coding agents open pull requests faster than teams can review them. Branch protection helps, but a green CI run only tells you the build passed. It doesn't tell you whether the change was reviewed,

4 min read · [aicodeops.hashnode.dev](https://aicodeops.hashnode.dev/how-to-gate-ai-written-pull-requests-in-github-actions-and-gitlab-ci?utm_source=hashnode&utm_medium=feed)

[Ilja Krasnjanski](https://hashnode.com/@iljakrasnjanski) · [Nov 2](https://hashnode.com/posts/gitlab-dead-drop-infrastructure/6ae856129023a1bb138a08a5)

### [Following the GitLab Dead Drop: Configuration Changes and C2 History](https://unk-deaddrop.hashnode.dev/gitlab-dead-drop-infrastructure?utm_source=hashnode&utm_medium=feed)

How a GitLab-hosted configuration file let the UNK\_DeadDrop operators change servers without new payloads, and what its revision history reveals.

7 min read · [unk-deaddrop.hashnode.dev](https://unk-deaddrop.hashnode.dev/gitlab-dead-drop-infrastructure?utm_source=hashnode&utm_medium=feed)

[Cyber Knight](https://hashnode.com/@cyberknight2479) · [Nov 2](https://hashnode.com/posts/they-couldn-t-prove-the-server-was-clean-so-they-rebuilt-it-from-scratch/6ae8354bd3cace28c9a0cadf)

### [They Couldn't Prove the Server Was Clean — So They Rebuilt It From Scratch](https://nulltrace.hashnode.dev/they-couldn-t-prove-the-server-was-clean-so-they-rebuilt-it-from-scratch?utm_source=hashnode&utm_medium=feed)

Alpine Linux faced a CVSS 10.0 GitLab flaw, eight crashed workers, and a gap in its own evidence. Its answer was the hardest call in incident response.

5 min read · [nulltrace.hashnode.dev](https://nulltrace.hashnode.dev/they-couldn-t-prove-the-server-was-clean-so-they-rebuilt-it-from-scratch?utm_source=hashnode&utm_medium=feed)

[Damiano Bianda](https://hashnode.com/@damianobianda) · [Oct 30](https://hashnode.com/posts/gitlab-was-patched-the-server-was-still-vulnerable-cve-2026-97229-lives-in-ruby/6ae46dbfe7474075d33ff978)

### [GitLab Was Patched, the Server Was Still Vulnerable: CVE-2026-97229 Lives in Ruby](https://damianobianda.hashnode.dev/gitlab-was-patched-the-server-was-still-vulnerable-cve-2026-97229-lives-in-ruby?utm_source=hashnode&utm_medium=feed)

CVE-2026-97229 is a CVSS 10.0 GitLab RCE, but the bug lives in Ruby. Alpine Linux upgraded GitLab and stayed vulnerable. What to check on your instance.

6 min read · [damianobianda.hashnode.dev](https://damianobianda.hashnode.dev/gitlab-was-patched-the-server-was-still-vulnerable-cve-2026-97229-lives-in-ruby?utm_source=hashnode&utm_medium=feed)

[AI Developer](https://hashnode.com/@lycore) · [Oct 30](https://hashnode.com/posts/php2shell-fragnesia-chain-patch-php-linux-gitlab/6ae41a5f15fe72784523f288)

### [PHP2Shell + Fragnesia: The Chain That Turns a PHP Bug Into Root (and Why Django Teams Should Care)](https://aidevpro.hashnode.dev/php2shell-fragnesia-chain-patch-php-linux-gitlab?utm_source=hashnode&utm_medium=feed)

CISA says attackers chain PHP2Shell with the Fragnesia Linux bug to get root. Who is exposed, fixed versions, and commands to patch and check today.

20 min read · [aidevpro.hashnode.dev](https://aidevpro.hashnode.dev/php2shell-fragnesia-chain-patch-php-linux-gitlab?utm_source=hashnode&utm_medium=feed)

[Rabin Adhikari](https://hashnode.com/@softverse) · [Oct 30](https://hashnode.com/posts/github-actions-vs-gitlab-ci-vs-jenkins-in-2026-which-ci-cd-tool-fits-your-team/6ae4c1fa5ceaf88286f3a8c1)

### [GitHub Actions vs GitLab CI vs Jenkins in 2026: Which CI/CD Tool Fits Your Team?](https://devopsenginer.hashnode.dev/github-actions-vs-gitlab-ci-vs-jenkins-in-2026-which-ci-cd-tool-fits-your-team?utm_source=hashnode&utm_medium=feed)

By DevOps Enginer – CI/CD Series · Updated for 2026 Quick answer: If your code already lives on GitHub and you want CI/CD with almost no setup or maintenance, GitHub Actions is the default choice in 2

28 min read · [devopsenginer.hashnode.dev](https://devopsenginer.hashnode.dev/github-actions-vs-gitlab-ci-vs-jenkins-in-2026-which-ci-cd-tool-fits-your-team?utm_source=hashnode&utm_medium=feed)

[Cyber Knight](https://hashnode.com/@cyberknight2479) · [Oct 30](https://hashnode.com/posts/they-patched-gitlab-the-bug-stayed/6ae4416e750d1b17018df4f8)

### [They Patched GitLab. The Bug Stayed.](https://nulltrace.hashnode.dev/they-patched-gitlab-the-bug-stayed?utm_source=hashnode&utm_medium=feed)

Alpine Linux did the responsible thing — it upgraded on time — and stayed vulnerable for four more days. The fix was never in GitLab's code at all.

6 min read · [nulltrace.hashnode.dev](https://nulltrace.hashnode.dev/they-patched-gitlab-the-bug-stayed?utm_source=hashnode&utm_medium=feed)
