# GitLab

GitLab is a platform for planning, source control, CI/CD, and software delivery.

This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles.

## Java4Shell: GitLab helps find and remediate a critical Java flaw

DevFeed: [Java4Shell: GitLab helps find and remediate a critical Java flaw](<https://devfeed.tech/articles/java4shell-gitlab-helps-find-and-remediate-a-critical-java-flaw-146875.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/java4shell-critical-java-flaw-how-gitlab-helps/>)

Author: Daniel Abeles

Published: 2026-11-20T00:00:00Z

Content type: tutorial

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [openjdk](<https://devfeed.tech/topics/openjdk.md>), [GitLab](<https://devfeed.tech/topics/gitlab.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [Container Image Building](<https://devfeed.tech/topics/container-image-building.md>), [x86](<https://devfeed.tech/topics/x86.md>)

Tags: [base64](<https://devfeed.tech/tags/base64.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [corruption](<https://devfeed.tech/tags/corruption.md>), [cpus](<https://devfeed.tech/tags/cpus.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-114938](<https://devfeed.tech/tags/cve-2026-114938.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [hardening](<https://devfeed.tech/tags/hardening.md>), [java](<https://devfeed.tech/tags/java.md>), [java-flaw](<https://devfeed.tech/tags/java-flaw.md>), [java4shell](<https://devfeed.tech/tags/java4shell.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [november-17](<https://devfeed.tech/tags/november-17.md>), [openjdk](<https://devfeed.tech/tags/openjdk.md>), [optimized](<https://devfeed.tech/tags/optimized.md>), [option](<https://devfeed.tech/tags/option.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [security](<https://devfeed.tech/tags/security.md>), [security-labs](<https://devfeed.tech/tags/security-labs.md>), [security-research](<https://devfeed.tech/tags/security-research.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>)

### AI overview

Java4Shell is a memory corruption flaw in optimized Base64 decoding in recent x86-64 Java runtimes; researchers demonstrated unauthenticated remote code execution in several products' default configurations. The excerpt says GitLab assessed its own managed infrastructure as not exploitable, while proactively upgrading one component containing the affected bundle. It recommends upgrading Java runtimes from 17.0.6 onward to listed fixed builds or distribution patches; until then, `-XX:-UseBASE64Intrinsics` disables the vulnerable optimization with a slight performance cost and requires restarting Java processes. For discovery, it pairs static checks (package and optional binary container scanning, Orbit, and Java/Kotlin project filters) with runtime workload inventories, since each view can miss Java installations. It also outlines GitLab Duo agent workflows for proposing per-project fixes, with human review and merge.

### Source excerpt

GitLab has internally assessed the impact of Java4Shell, and concluded it is not exploitable in GitLab-managed infrastructure. Exploitation requires a specific combination of conditions, which we confirmed are not present in our production environment. A single component was found to contain the impacted bundle in its runtime environment, which we are proactively upgrading as a hardening measure. On November 17, 2026, OpenJDK, the project that most Java runtimes are built from, fixed a memory corruption flaw known as Java4Shell (CVE-2026-114938, CVSS 8.1) in the optimized java.util.Base64 decoding used on recent x86-64 CPUs. Web servers and frameworks routinely decode Base64 values from users, such as authentication headers and cookies, before the application sees the request. Researchers have demonstrated unauthenticated remote code execution in the default configurations of several widely used Java products. Upgrade Java to a fixed version now To mitigate this issue, upgrade every Java runtime from 17.0.6 onward, including unsupported releases such as Java 18 and 24, to a build based on OpenJDK 17.0.21.1, 21.0.13.1, 25.0.5.1, or 27.0.1.1, or to your distribution's patched package. If you can't upgrade right away, turn off the vulnerable optimization with the -XX:-UseBASE64Intrinsics JVM option. Here are fixed builds and packages as of November 19: Vendor or distributionFixed build or packageOpenJDK17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1Eclipse Temurin17.0.21.1+2, 21.0.13.1+2, 25.0.5.1+2, 27.0.1.1+4Amazon Corretto17.0.21.1.2, 21.0.13.1.2, 25.0.5.1.2, 27.0.1.1.4Azul Zulu17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1BellSoft Liberica17.0.21.1+5, 21.0.13.1+5, 25.0.5.1+5, 27.0.1.1+5SapMachine17.0.21.1, 21.0.13.1, 25.0.5.1, 27.0.1.1Microsoft Build of OpenJDK17.0.21.1, 21.0.13.1, 25.0.5.1Oracle Java SE 8 Performance Pack8u513-perf. Other Java 8 builds aren't affectedUbuntu 26.10, 26.04, 24.04, 22.04openjdk-17 17.0.21.1, openjdk-21 21.0.13.1, openjdk-25 25.0.5.1, and on 26.10

## Rotate a leaked GitLab token and let GitLab Duo fix the code

DevFeed: [Rotate a leaked GitLab token and let GitLab Duo fix the code](<https://devfeed.tech/articles/rotate-a-leaked-gitlab-token-and-let-gitlab-duo-fix-the-code-144779.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/secret-detection-token-rotate-and-fix/>)

Author: Mark Mishaev

Published: 2026-11-19T00:00:00Z

Content type: release

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [Secure token management](<https://devfeed.tech/topics/secure-token-management.md>), [Secret Scanning](<https://devfeed.tech/topics/secret-scanning.md>), [personal access token](<https://devfeed.tech/topics/personal-access-token.md>), [CI/CD secrets management](<https://devfeed.tech/topics/ci-cd-secrets-management.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [gitlab-ci](<https://devfeed.tech/topics/gitlab-ci.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [GitLab](<https://devfeed.tech/topics/gitlab.md>)

Tags: [acting](<https://devfeed.tech/tags/acting.md>), [actions](<https://devfeed.tech/tags/actions.md>), [after](<https://devfeed.tech/tags/after.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [beta](<https://devfeed.tech/tags/beta.md>), [branch](<https://devfeed.tech/tags/branch.md>), [build](<https://devfeed.tech/tags/build.md>), [can](<https://devfeed.tech/tags/can.md>), [cd](<https://devfeed.tech/tags/cd.md>), [chat](<https://devfeed.tech/tags/chat.md>), [ci](<https://devfeed.tech/tags/ci.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [code](<https://devfeed.tech/tags/code.md>), [duo](<https://devfeed.tech/tags/duo.md>), [features](<https://devfeed.tech/tags/features.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [let](<https://devfeed.tech/tags/let.md>), [product](<https://devfeed.tech/tags/product.md>), [security](<https://devfeed.tech/tags/security.md>), [token](<https://devfeed.tech/tags/token.md>)

### AI overview

Starting with GitLab 19.6 beta for GitLab Ultimate, an active leaked GitLab PAT can be rotated from its vulnerability finding: GitLab revokes it, stores a replacement in Secrets Manager, and GitLab Duo opens an MR to update CI/CD jobs. The replacement value is not shown to the user or agent; rotation happens before the agent starts. Review and merge the MR, then resolve the finding. Rotation is immediate and irreversible, and the replacement is scoped to the current project, so scripts outside GitLab CI/CD or jobs in other projects need another token. The feature supports GitLab PATs, including fine-grained PATs, but not other detected secret types. GitLab.com users can rotate their own tokens; Self-Managed administrators can also rotate others' tokens. If the Duo session fails, rotation and secret storage still occur, leaving code updates manual. A dependency-free CLI can batch-rotate group findings and eligible CI/CD variable tokens; it defaults to dry-run, caps runs at 10 rotations unless configured, and omits token values from reports.

### Source excerpt

Secret detection alerts you when an active personal access token (PAT) is exposed in your default branch. Acting on that finding is harder: revoking the token breaks dependent pipelines, and replacing it safely takes several manual steps. While the finding waits in your vulnerability report, the token stays live. Starting in GitLab 19.6 in beta for GitLab Ultimate, you can remediate a leaked GitLab PAT directly from the vulnerability page. Select Rotate and fix, and GitLab revokes the token, stores a replacement in GitLab Secrets Manager, and uses GitLab Duo Agent Platform to open a merge request (MR) to update your CI/CD jobs. You review and merge the MR. GitLab never exposes the new token value to you or your agents. Why leaked tokens stay active after detection Imagine that secret detection flags an active PAT in deploy.sh: export GITLAB_TOKEN="glpat-..." Fixing this manually requires tracking down the token's owner, revoking it, generating a replacement with matching scopes, storing it securely, and opening MRs to update your scripts and CI/CD jobs. Because this process is tedious, remediations often stall or go wrong: The finding ages: Nobody wants to break the pipeline, so the finding sits in the vulnerability report while the token remains active. The fix stops halfway: Someone revokes the token immediately, breaking the build. In a rush to recover, they paste a replacement into a less secure CI/CD variable. The new token leaks: Someone shares the replacement token in a chat thread so a teammate can configure it. In the gap between detected and rotated, the token still works for anyone who can read the repository. Rotate and fix in a snap The Rotate and fix function closes this gap by combining secret detection and validity checks, GitLab Secrets Manager, and GitLab Duo Agent Platform. When you open an active PAT finding and select AI actions > Fix with AI > Rotate and fix, GitLab: Revokes the leaked token and creates a replacement with the same name, scopes,

## Duo Agent Platform now does up to 2x more per GitLab Credit

DevFeed: [Duo Agent Platform now does up to 2x more per GitLab Credit](<https://devfeed.tech/articles/duo-agent-platform-now-does-up-to-2x-more-per-gitlab-credit-144775.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/duo-agent-platform-does-more-per-gitlab-credit/>)

Author: Stuart Moncada

Published: 2026-11-19T00:00:00Z

Content type: release

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [AI Agent](<https://devfeed.tech/topics/ai-agent.md>), [AI-assisted coding](<https://devfeed.tech/topics/ai-assisted-coding.md>), [Claude](<https://devfeed.tech/topics/claude.md>), [Slack](<https://devfeed.tech/topics/slack.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [anthropic](<https://devfeed.tech/tags/anthropic.md>), [channel](<https://devfeed.tech/tags/channel.md>), [conversations](<https://devfeed.tech/tags/conversations.md>), [duo](<https://devfeed.tech/tags/duo.md>), [fewer](<https://devfeed.tech/tags/fewer.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [google](<https://devfeed.tech/tags/google.md>), [here](<https://devfeed.tech/tags/here.md>), [hosted](<https://devfeed.tech/tags/hosted.md>), [mention](<https://devfeed.tech/tags/mention.md>), [models](<https://devfeed.tech/tags/models.md>), [openai](<https://devfeed.tech/tags/openai.md>), [platform](<https://devfeed.tech/tags/platform.md>), [product](<https://devfeed.tech/tags/product.md>), [prompt-caching](<https://devfeed.tech/tags/prompt-caching.md>), [slack](<https://devfeed.tech/tags/slack.md>), [thread](<https://devfeed.tech/tags/thread.md>), [use-case](<https://devfeed.tech/tags/use-case.md>), [use-cases](<https://devfeed.tech/tags/use-cases.md>)

### AI overview

GitLab says model-use efficiencies will make most customers' GitLab Credits go up to twice as far: agent and flow tasks use fewer model requests, with prompt caching reducing requests further for eligible tasks. The stated efficiency applies across models from Anthropic, OpenAI, Google, and GitLab-hosted open-weight models. Flat-rate features (Code Review Flow, SAST flows, and Code Suggestions) are unaffected, and self-hosted models remain at 8 requests per credit. The excerpt highlights Slack-triggered agent work, scheduled automations (beta in GitLab 19.6), a Business Logic Security Analyzer (beta for GitLab Ultimate on GitLab.com), issue-to-merge-request work, and `/goal` workflows. The new efficiencies begin Nov. 19, 2026 for new customers; existing customers may opt in from that date, a one-way move, or move by default Dec. 18. Customers who opt out before Dec. 18 keep current terms and included credits until renewal or 12 months, whichever comes first. From Jan. 1, 2027, monthly promotional credits change to $8 per Premium seat and $16 per Ultimate seat.

### Source excerpt

GitLab Duo Agent Platform has become more efficient in how it uses the underlying models offered through GitLab. That includes all the latest models from Anthropic, OpenAI, Google, and GitLab-hosted open-weight models. And, we're passing the savings to you. Each task you give to agents and flows in GitLab now results in fewer model requests. Enable prompt caching and eligible tasks use even fewer requests. Together, these efficiencies mean most customers will see their GitLab Credits go up to twice as far. What this looks like in real life As a representative example, consider the following example of a real team of 500 people using GitLab Duo Agent Platform in October 2026. Across every use case, the number of requests they were billed for (Column 2) is higher than what it would be with the new efficiencies turned on (Column 4). Therefore, the GitLab Credits used moving forward (same request to credit ratios by model type) will be lower. Your GitLab account team can show how your recent usage compares with the new efficiencies enabled, so you can see how much further your credits will go.Put the extra credits to work With fewer credits required for your current use cases, you can enable more agents and flows, and automate more steps in your software development lifecycle, natively integrated in the GitLab platform you already use. Here are some good places to start: Turn Slack conversations into shipped work. GitLab for Slack now has agent capabilities. Mention @GitLab in a team channel or your own DM, and the agent reads the conversation, checks what already exists in GitLab, turns decisions into issues and merge requests, and starts agent flows, posting the results back to the thread. Each request runs with your own GitLab permissions and is recorded as an agent session. Put routine work on a schedule. With scheduled automations, now in beta in GitLab 19.6, flows run on their own at a cadence your team sets, from every 15 minutes to every month. Triage new issues

## GitLab 19.6 released

DevFeed: [GitLab 19.6 released](<https://devfeed.tech/articles/gitlab-19-6-released-144780.md>)

Original publisher: [Read original article](<https://docs.gitlab.com/releases/19/gitlab-19-6-released/>)

Author: GitLab

Published: 2026-11-19T00:00:00Z

Content type: release

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Loop Engineering](<https://devfeed.tech/topics/loop-engineering.md>), [Secret Scanning](<https://devfeed.tech/topics/secret-scanning.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [Slack](<https://devfeed.tech/topics/slack.md>)

Tags: [1-5](<https://devfeed.tech/tags/1-5.md>), [2](<https://devfeed.tech/tags/2.md>), [2026](<https://devfeed.tech/tags/2026.md>), [3](<https://devfeed.tech/tags/3.md>), [about](<https://devfeed.tech/tags/about.md>), [account](<https://devfeed.tech/tags/account.md>), [actions](<https://devfeed.tech/tags/actions.md>), [added](<https://devfeed.tech/tags/added.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [advanced](<https://devfeed.tech/tags/advanced.md>), [after](<https://devfeed.tech/tags/after.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [availability](<https://devfeed.tech/tags/availability.md>), [duo](<https://devfeed.tech/tags/duo.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [slack](<https://devfeed.tech/tags/slack.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

GitLab 19.6 adds governance, agent workflows, faster merge request reviews, and security controls. MCP server tool calls now create audit events, while group Owners can deny tools, require approval, or allow them (the control is in beta). Duo in Slack is in limited availability on GitLab.com; `/goal` starts long-running Developer Flow sessions that can commit, push, and create merge requests without per-action approval, and scheduled automations are in beta. Rapid Diffs is generally available, streaming server-rendered diffs; the first file is reported to appear in about 1.5 seconds versus 4.5 seconds previously. Security updates include Rust scanning in Advanced SAST (added in 19.5 and still beta), malware rules for merge request approvals requiring SBOM-based dependency scanning, and configurable pipeline-variable limits. Web search in Agentic Chat is off by default and requires group or instance enablement; searches create audit events. The notes also flag upgrade guidance, including potential custom NGINX configuration breaks after the bundled version update.

### Source excerpt

GitLab 19.6 released with GitLab Duo in Slack in limited availability on GitLab.com

## GitLab Transcend Hackathon: Meet the 'Life After Code' winners

DevFeed: [GitLab Transcend Hackathon: Meet the 'Life After Code' winners](<https://devfeed.tech/articles/gitlab-transcend-hackathon-meet-the-life-after-code-winners-142002.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/gitlab-transcend-hackathon-life-after-code/>)

Author: Missy Davies

Published: 2026-11-18T00:00:00Z

Content type: news

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [agentic workflows](<https://devfeed.tech/topics/agentic-workflows.md>), [Hackathon](<https://devfeed.tech/topics/hackathon.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [gitlab-ci](<https://devfeed.tech/topics/gitlab-ci.md>), [Test-driven development](<https://devfeed.tech/topics/tdd.md>), [human review](<https://devfeed.tech/topics/human-review.md>), [GitLab](<https://devfeed.tech/topics/gitlab.md>), [3D](<https://devfeed.tech/topics/3d.md>)

Tags: [3d](<https://devfeed.tech/tags/3d.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [automated](<https://devfeed.tech/tags/automated.md>), [autonomous](<https://devfeed.tech/tags/autonomous.md>), [bug](<https://devfeed.tech/tags/bug.md>), [ci](<https://devfeed.tech/tags/ci.md>), [code-generation](<https://devfeed.tech/tags/code-generation.md>), [community](<https://devfeed.tech/tags/community.md>), [contributors](<https://devfeed.tech/tags/contributors.md>), [control](<https://devfeed.tech/tags/control.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [email](<https://devfeed.tech/tags/email.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [flow](<https://devfeed.tech/tags/flow.md>), [generation](<https://devfeed.tech/tags/generation.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [graph](<https://devfeed.tech/tags/graph.md>), [hackathon](<https://devfeed.tech/tags/hackathon.md>), [math](<https://devfeed.tech/tags/math.md>), [npm](<https://devfeed.tech/tags/npm.md>), [npm-package](<https://devfeed.tech/tags/npm-package.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [payment](<https://devfeed.tech/tags/payment.md>), [pharmacy](<https://devfeed.tech/tags/pharmacy.md>)

### AI overview

The Transcend Hackathon challenged developers to use GitLab Duo Agent Platform to move work from code to production, with varying levels of human oversight. The winners show agents handling investigation, fixes and routing while tests, CI checks and people provide controls. Examples include Aftermath, which traces CI exposure from a compromised npm package and requires human sign-off on investigation scope and containment; ShakeFix, which tested and deployed a pharmacy bug fix in 18 minutes and 34 seconds without human intervention; and Unstuck, which completed dependency upgrades through reviewed merge requests, pausing when behavior changes. Locus released tactile math graphs only after they passed touch-rule checks. Other projects covered benefits-payment corrections, code review preferences, changing security conditions, risk-based autonomy and lower-carbon CI. The excerpt describes selected winners and examples, not every project in the gallery.

### Source excerpt

Code generation is the easy part now. The hard part is everything that comes after it: getting software from a working change to running in production. That's the problem we put to the community in the Transcend Hackathon: "Life after code, the path to production at the speed of imagination". The hackathon, which ran during October, challenged participants to build agents and flows on GitLab Duo Agent Platform that can take over the work after the code is written. They also had to decide how much control to hand the agents, from approving every step to making them completely autonomous. More than 3,300 developers registered and 783 projects were submitted. The winning projects show how far agents and flows can go after code generation. A pharmacy app bug reported simply by shaking a phone was fixed and shipped in 18 minutes with no human in the middle. A teacher's email became a 3D-printable math graph a blind student could read by touch. A flow applied to a benefits software app helped detect payment miscalculations based on a won appeal. What these projects share: Agents do the reading, writing, and routing, while automated checks and people make the final calls. The winners The prize pool was $45,000 across nine categories, with each project eligible for one path prize and one special prize. You can find the full field in the project gallery. Path A: Start Fresh New projects built from scratch on GitLab Best Assisted Agent ($4,000): Aftermath Aftermath by Ahadi Cyizere answers the question scanners can't: When a hijacked npm package is disclosed, had it already run in last week's CI? A custom GitLab Duo flow with three subagents traces past CI jobs and the credentials each job could reach. A person signs off on the scope of the investigation, then on the containment plan, and finally closes the incident once CI has rotated only the exposed keys and deleted the affected images, and proof is attached. Best Supervised Agent ($4,000): Lookback Lookback by Ujwal Sures

## Agentic engineering with GitLab and your local agent: A walkthrough

DevFeed: [Agentic engineering with GitLab and your local agent: A walkthrough](<https://devfeed.tech/articles/agentic-engineering-with-gitlab-and-your-local-agent-a-walkthrough-144773.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/agentic-engineering-walkthrough/>)

Author: Fatima Sarah Khalid

Published: 2026-11-18T00:00:00Z

Content type: tutorial

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [Agent Skills](<https://devfeed.tech/topics/agent-skills.md>), [Agent Harness](<https://devfeed.tech/topics/agent-harness.md>), [gitlab-ci](<https://devfeed.tech/topics/gitlab-ci.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [Loop Engineering](<https://devfeed.tech/topics/loop-engineering.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>), [codex](<https://devfeed.tech/topics/codex.md>), [cursor](<https://devfeed.tech/topics/cursor.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-engineering](<https://devfeed.tech/tags/agentic-engineering.md>), [agentic-workflows](<https://devfeed.tech/tags/agentic-workflows.md>), [ai](<https://devfeed.tech/tags/ai.md>), [code](<https://devfeed.tech/tags/code.md>), [code-reviews](<https://devfeed.tech/tags/code-reviews.md>), [codex](<https://devfeed.tech/tags/codex.md>), [coding](<https://devfeed.tech/tags/coding.md>), [connect](<https://devfeed.tech/tags/connect.md>), [cursor](<https://devfeed.tech/tags/cursor.md>), [developer](<https://devfeed.tech/tags/developer.md>), [devsecops](<https://devfeed.tech/tags/devsecops.md>), [duo](<https://devfeed.tech/tags/duo.md>), [environment](<https://devfeed.tech/tags/environment.md>), [failed](<https://devfeed.tech/tags/failed.md>), [flow](<https://devfeed.tech/tags/flow.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [harness](<https://devfeed.tech/tags/harness.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [install](<https://devfeed.tech/tags/install.md>), [issue](<https://devfeed.tech/tags/issue.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>)

### AI overview

The GitLab Duo setup skill connects a local coding harness to GitLab Duo Agent Platform, where repository-aware work runs as GitLab flows and merge requests remain subject to existing review, pipeline, security, and approval policies. After reviewing one setup plan, an Owner can enable group workflows, automatic code review, failed-pipeline automation, and the GitLab MCP connection; a project Maintainer can configure only that project. The walkthrough covers handing assigned issues to Developer, reviewing MRs and resolving feedback or conflicts, fixing failed pipelines, and--on Ultimate--triaging security findings. Pipeline fixes appear as inline suggestions when they fit the MR diff, as a new MR when they require other files or no MR is open, or as guidance when a reliable fix cannot be determined or the failure is security-sensitive. Prerequisites include a GitLab.com group with GitLab Credits, a project with pipelines and work items, and Claude Code plus git and glab; group-wide setup requires the Owner role. The pipeline flow reads only the last 150 KiB of a job log. Security automation offers standard and conservative presets with different thresholds and open-MR limits.

### Source excerpt

You can build an agentic engineering environment to drive greater automation throughout your workflow. How? Start in the harness you already use and connect to GitLab Duo Agent Platform once with a skill. Longer, repository-aware workflows run on GitLab, and every merge request still hits the same reviews, pipelines, scans, and approval policies. In this article, we will show you how to quickly get started, from setup to tackling four key use cases. We focus on Claude Code as the local harness because that's what we see most of our customers using but this same flow can apply to the local harness of your choosing, including Duo CLI. How to configure your agentic engineering environment If you already do most of your coding in a local harness, keep working there and wire it to GitLab Duo Agent Platform. From the terminal, you can direct lifecycle work to agentic workflows that run inside GitLab: Picking up an issue and opening a merge request Reviewing every MR as it lands Resolving merge conflicts Repairing a pipeline that just failed With GitLab Ultimate, triaging and fixing security findings once code lands Claude Code, Codex, Cursor, OpenCode, and others become the place from where you direct that work. Part 1 is the setup Install the GitLab Duo setup skill, ask Claude Code to run it, and it sets up your whole top-level group with the necessary settings, the flows, an automation in every project, and the MCP connection. Part 2 walks through four workflows You can try them as soon as the setup is done, each driven from Claude Code: Find an issue assigned to you and hand it to the Developer flow. Get automated code reviews on your merge requests, act on the findings without leaving your harness, and resolve any conflicts that pop up. Use an automation to fix a failed pipeline. On Ultimate, triage and fix security findings with the security flows. When you want an even tighter loop The MR followup skill guides your local harness through the steps above even faster.

## Run GitLab-certified hardened images for GitLab Enterprise Edition with the security of Chainguard

DevFeed: [Run GitLab-certified hardened images for GitLab Enterprise Edition with the security of Chainguard](<https://devfeed.tech/articles/run-gitlab-certified-hardened-images-for-gitlab-enterprise-edition-with-the-security-of-chainguard-133959.md>)

Original publisher: [Read original article](<https://www.chainguard.dev/unchained/run-gitlab-certified-hardened-images-for-gitlab-enterprise-edition-with-the-security-of-chainguard>)

Published: 2026-11-13T00:00:00Z

Content type: release

Language: en

Sources: [Chainguard: Unchained](<https://devfeed.tech/sources/chainguard-unchained.md>)

Topics: [chainguard commercial builds](<https://devfeed.tech/topics/chainguard-commercial-builds.md>), [chainguard images](<https://devfeed.tech/topics/chainguard-images.md>), [GitLab](<https://devfeed.tech/topics/gitlab.md>), [chainguard sboms](<https://devfeed.tech/topics/chainguard-sboms.md>), [chainguard cve remediation](<https://devfeed.tech/topics/chainguard-cve-remediation.md>), [container images](<https://devfeed.tech/topics/container-images.md>), [fips 140-3](<https://devfeed.tech/topics/fips-140-3.md>), [containers for fedramp](<https://devfeed.tech/topics/containers-for-fedramp.md>)

Tags: [3](<https://devfeed.tech/tags/3.md>), [accelerate](<https://devfeed.tech/tags/accelerate.md>), [advanced](<https://devfeed.tech/tags/advanced.md>), [alerts](<https://devfeed.tech/tags/alerts.md>), [attack-surface](<https://devfeed.tech/tags/attack-surface.md>), [audit](<https://devfeed.tech/tags/audit.md>), [bloat](<https://devfeed.tech/tags/bloat.md>), [build](<https://devfeed.tech/tags/build.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [chainguard](<https://devfeed.tech/tags/chainguard.md>), [container](<https://devfeed.tech/tags/container.md>), [container-images](<https://devfeed.tech/tags/container-images.md>), [cves](<https://devfeed.tech/tags/cves.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [fips](<https://devfeed.tech/tags/fips.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [hardened-images](<https://devfeed.tech/tags/hardened-images.md>), [images](<https://devfeed.tech/tags/images.md>), [sboms](<https://devfeed.tech/tags/sboms.md>), [security](<https://devfeed.tech/tags/security.md>)

### AI overview

Organizations can keep their existing GitLab Enterprise Edition license while Chainguard maintains GitLab-certified hardened container images. GitLab runs its end-to-end QA suite against each release; images include SBOM, provenance, and signature artifacts and are built through Chainguard Factory, described as SLSA Level 3-compliant. The images omit shells, package managers, and other unnecessary components, and Chainguard states remediation timelines of 7 days for critical CVEs and 14 days for other severities. FIPS-ready variants are available. An active GitLab subscription is required: Chainguard handles image rebuilds, CVE remediation, and image-related support under its support plan, while GitLab provides application support through its subscription. Chainguard coordinates with GitLab on vulnerability remediation and daily rebuilds.

### Source excerpt

Secure GitLab Enterprise Edition with Chainguard's certified hardened container images, featuring minimal CVEs, signed SBOMs, and FIPS-ready options.

## Turn Jira tickets into GitLab merge requests with Duo Agent Platform

DevFeed: [Turn Jira tickets into GitLab merge requests with Duo Agent Platform](<https://devfeed.tech/articles/turn-jira-tickets-into-gitlab-merge-requests-with-duo-agent-platform-131497.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/jira-ticket-to-gitlab-mr-with-duo-agent-platform/>)

Author: Itzik Gan Baruch

Published: 2026-11-12T00:00:00Z

Content type: tutorial

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [jira](<https://devfeed.tech/topics/jira.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [2](<https://devfeed.tech/tags/2.md>), [admin](<https://devfeed.tech/tags/admin.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agentic](<https://devfeed.tech/tags/agentic.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-catalog](<https://devfeed.tech/tags/ai-catalog.md>), [also](<https://devfeed.tech/tags/also.md>), [api](<https://devfeed.tech/tags/api.md>), [atlassian](<https://devfeed.tech/tags/atlassian.md>), [beta](<https://devfeed.tech/tags/beta.md>), [can](<https://devfeed.tech/tags/can.md>), [catalog](<https://devfeed.tech/tags/catalog.md>), [change](<https://devfeed.tech/tags/change.md>), [duo](<https://devfeed.tech/tags/duo.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [jira](<https://devfeed.tech/tags/jira.md>), [merge](<https://devfeed.tech/tags/merge.md>), [platform](<https://devfeed.tech/tags/platform.md>), [product](<https://devfeed.tech/tags/product.md>), [tickets](<https://devfeed.tech/tags/tickets.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>), [with](<https://devfeed.tech/tags/with.md>)

### AI overview

The tutorial connects Jira and GitLab so a custom Jira agent can search, summarize, and comment on tickets, then hand implementation to Developer Flow with `/goal`, which creates a draft merge request. GitLab's Jira integration links MRs that mention a ticket key back to the Jira ticket and can post comments. Setup requires GitLab Premium or Ultimate, Duo Agent Platform and Developer Flow, a Jira Cloud project, and an Atlassian API token for the standard integration; Atlassian organization admin access is needed to authorize GitLab as an MCP client. Each user connects their own Atlassian account, so Jira access follows their permissions and comments appear under their name. Developer Flow runs as a CI pipeline with Git and GitLab API write access after the goal is sent; review the draft MR, as nothing merges automatically. The Atlassian MCP server is experimental and not production-ready, and each goal consumes GitLab Credits.

### Source excerpt

Many teams plan in Jira and ship in GitLab. Even if you already use GitLab Duo Agent Platform, you still open Jira to read each ticket, copy it into an agent for implementation, and report the merge request back. This tutorial shows you how to remove that handoff. You add a Jira agent to Duo Agentic Chat. The agent knows your project and repository, and you use it to find, create, and update tickets. Then you hand a ticket to Developer Flow with /goal, and Developer Flow creates the merge request. Watch the short demo first: A custom Jira agent finds the urgent tickets, one goes to Developer Flow, and the merge request shows up on the Jira ticket. Prerequisites GitLab Premium or Ultimate on GitLab.com, with GitLab Duo Agent Platform turned on for your top-level group and Developer Flow enabled for the project. For the Atlassian MCP server in the AI Catalog: experiment and beta features turned on for the top-level group (Settings > GitLab Duo > Change configuration). Maintainer or Owner role on the project for the one-time settings in Steps 1 and 2; Developer or above on a project to use the agent there afterwards. A Jira Cloud project you can read and comment on, and Atlassian admin access once, to trust GitLab as a Model Context Protocol (MCP) client. Jira names a ticket with a ticket key: the project key plus a number. Our examples use project key KAN, so an example ticket key looks like KAN-123. The examples also use GitLab project my-group/my-project. A Jira API token from id.atlassian.com, used only by GitLab's Jira integration in Step 1. Note: The Atlassian MCP server in the AI Catalog is an experiment and isn't ready for production use. Try it on a test project first. Tutorial Here are the steps to follow to turn Jira tickets into GitLab merge requests. 1. Connect GitLab to Jira This is GitLab's standard Jira integration. It makes any MR that mentions a ticket, for example KAN-123, show up on that Jira ticket, and posts a comment there. Five minutes, done onc

## GitLab 19.5 Makes Agentic Development a Governed Part of the DevOps Platform

DevFeed: [GitLab 19.5 Makes Agentic Development a Governed Part of the DevOps Platform](<https://devfeed.tech/articles/gitlab-19-5-makes-agentic-development-a-governed-part-of-the-devops-platform-121075.md>)

Original publisher: [Read original article](<https://www.infoq.com/news/2026/11/gitlab-19-5-agentic-platform/>)

Author: Craig Risi

Published: 2026-11-06T12:00:00Z

Content type: release

Language: en

Sources: [InfoQ](<https://devfeed.tech/sources/infoq.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [ai-governance](<https://devfeed.tech/topics/ai-governance.md>), [agentic-coding](<https://devfeed.tech/topics/agentic-coding.md>), [DevOps](<https://devfeed.tech/topics/devops.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [agentic](<https://devfeed.tech/tags/agentic.md>), [agentic-development](<https://devfeed.tech/tags/agentic-development.md>), [agentic-development-lifecycle](<https://devfeed.tech/tags/agentic-development-lifecycle.md>), [agentic-software-development](<https://devfeed.tech/tags/agentic-software-development.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-coding-agents](<https://devfeed.tech/tags/ai-coding-agents.md>), [ai-governance](<https://devfeed.tech/tags/ai-governance.md>), [ai-ml-data-engineering](<https://devfeed.tech/tags/ai-ml-data-engineering.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [cli](<https://devfeed.tech/tags/cli.md>), [codex](<https://devfeed.tech/tags/codex.md>), [coding-agents](<https://devfeed.tech/tags/coding-agents.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [cursor](<https://devfeed.tech/tags/cursor.md>), [dashboard](<https://devfeed.tech/tags/dashboard.md>), [devops](<https://devfeed.tech/tags/devops.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [gitlab-19-5-agentic-platform](<https://devfeed.tech/tags/gitlab-19-5-agentic-platform.md>), [governance](<https://devfeed.tech/tags/governance.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [ml-data-engineering](<https://devfeed.tech/tags/ml-data-engineering.md>), [model-context-protocol-mcp](<https://devfeed.tech/tags/model-context-protocol-mcp.md>), [news](<https://devfeed.tech/tags/news.md>)

### AI overview

GitLab 19.5 makes its MCP server generally available, letting compatible tools such as Claude Code and Cursor access GitLab capabilities and start or monitor Duo agents and flows. Administrators can restrict exposed toolsets; GitLab.com limits MCP requests to 60 per minute for Free users and 600 for Premium and Ultimate, counting reconnects and retries. Organizations can connect external agents through the GitLab CLI, record qualifying sessions in AI Governance, and stream audit events to a SIEM. Duo CLI's auto mode can run tools without per-action approval, but is disabled by default, can be controlled at instance, group, and project levels, and still blocks tools marked Always Deny. The release also makes Secrets Manager generally available and adds centralized security profiles for Secret Detection and SAST. The article presents GitLab's approach as making the DevOps platform agent-accessible while emphasizing governance.

### Source excerpt

GitLab 19.5, released on October 15, puts agentic software development and governance at the centre of the platform, making its GitLab MCP server generally available while expanding how external AI agents can interact with GitLab. By Craig Risi

## Over 1,000 GitLab servers vulnerable to ongoing RCE attacks

DevFeed: [Over 1,000 GitLab servers vulnerable to ongoing RCE attacks](<https://devfeed.tech/articles/over-1-000-gitlab-servers-vulnerable-to-ongoing-rce-attacks-112216.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/over-1-000-gitlab-servers-vulnerable-to-code-execution-attacks/>)

Author: Sergiu Gatlan

Published: 2026-11-02T12:47:00Z

Content type: news

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [gitlab-ci](<https://devfeed.tech/topics/gitlab-ci.md>)

Tags: [actively-exploited](<https://devfeed.tech/tags/actively-exploited.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [exposed](<https://devfeed.tech/tags/exposed.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [rce](<https://devfeed.tech/tags/rce.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [remote-code-execution-attacks](<https://devfeed.tech/tags/remote-code-execution-attacks.md>), [security](<https://devfeed.tech/tags/security.md>), [servers](<https://devfeed.tech/tags/servers.md>), [shadowserver](<https://devfeed.tech/tags/shadowserver.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [support](<https://devfeed.tech/tags/support.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

CVE-2026-97229 is an integer overflow flaw in GitLab's CI/CD Regular Expression Compiler that can let an unauthenticated attacker execute code through a crafted regular expression in a pipeline configuration. GitLab released patches for CE and EE versions 19.4.2, 19.3.5, and 19.2.8, and recommends self-managed installations upgrade immediately; GitLab.com is patched, while GitLab Dedicated customers need no action. CISA confirmed active exploitation and added the flaw to its KEV Catalog. Shadowserver reported tracking more than 1,000 exposed, unpatched instances amid ongoing attacks.

### Source excerpt

Over 1,000 Internet-exposed GitLab servers are still unpatched against a maximum-severity flaw actively exploited in remote code execution attacks. [...]

## Alpine Linux rebuilds GitLab after attempted RCE attack

DevFeed: [Alpine Linux rebuilds GitLab after attempted RCE attack](<https://devfeed.tech/articles/alpine-linux-rebuilds-gitlab-after-attempted-rce-attack-110767.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/alpine-linux-rebuilds-gitlab-after-attempted-rce-attack/>)

Author: Bill Toulas

Published: 2026-11-01T15:11:21Z

Content type: news

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [Exploit](<https://devfeed.tech/topics/exploit.md>), [software supply-chain attack](<https://devfeed.tech/topics/software-supply-chain-attack.md>), [gitlab-ci](<https://devfeed.tech/topics/gitlab-ci.md>), [Linux](<https://devfeed.tech/topics/linux.md>)

Tags: [actively-exploited](<https://devfeed.tech/tags/actively-exploited.md>), [all](<https://devfeed.tech/tags/all.md>), [alpine](<https://devfeed.tech/tags/alpine.md>), [alpine-linux](<https://devfeed.tech/tags/alpine-linux.md>), [attack](<https://devfeed.tech/tags/attack.md>), [compromise](<https://devfeed.tech/tags/compromise.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [critical](<https://devfeed.tech/tags/critical.md>), [development](<https://devfeed.tech/tags/development.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [gitlab-vulnerability](<https://devfeed.tech/tags/gitlab-vulnerability.md>), [hackers](<https://devfeed.tech/tags/hackers.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [october](<https://devfeed.tech/tags/october.md>), [open](<https://devfeed.tech/tags/open.md>), [open-source](<https://devfeed.tech/tags/open-source.md>), [over](<https://devfeed.tech/tags/over.md>), [passwords](<https://devfeed.tech/tags/passwords.md>), [rce](<https://devfeed.tech/tags/rce.md>), [rebuilds](<https://devfeed.tech/tags/rebuilds.md>), [security](<https://devfeed.tech/tags/security.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [supply-chain-attack](<https://devfeed.tech/tags/supply-chain-attack.md>), [support](<https://devfeed.tech/tags/support.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

Attackers repeatedly triggered GitLab worker crashes while attempting to exploit CVE-2026-97229 in Alpine Linux's development infrastructure; four attempts were partially successful, but the project found no evidence of code execution or tampering. Missing logs and outbound connection records meant it could not rule out compromise, so it rebuilt GitLab from scratch. The vulnerability fix required a Ruby patch absent from Alpine's custom image: upgrades to GitLab 19.3.4 and then 19.3.6 had not closed the flaw. Alpine found no tampering in commits, packages, or releases through October 27, and said signing keys were not stored on the server. It advises users to reset GitLab passwords and pull alpinelinux/gitlab:19.3.6, published October 27 with Ruby 3.3.13.

### Source excerpt

Hackers attempted to exploit a critical GitLab vulnerability in Alpine Linux's development infrastructure on October 20-21, prompting the open-source project to rebuild its GitLab server and reset all passwords over concerns of a possible compromise. [...]

## CISA says max severity GitLab flaw now exploited in the wild

DevFeed: [CISA says max severity GitLab flaw now exploited in the wild](<https://devfeed.tech/articles/cisa-says-max-severity-gitlab-flaw-now-exploited-in-the-wild-107790.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/hackers-now-exploiting-max-severity-gitlab-flaw-in-attacks/>)

Author: Sergiu Gatlan

Published: 2026-10-30T13:00:32Z

Content type: news

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [cybersecurity and infrastructure security agency](<https://devfeed.tech/topics/cybersecurity-and-infrastructure-security-agency.md>), [Exploit](<https://devfeed.tech/topics/exploit.md>), [Cybersecurity](<https://devfeed.tech/topics/cybersecurity.md>), [gitlab-ci](<https://devfeed.tech/topics/gitlab-ci.md>), [Security](<https://devfeed.tech/topics/security.md>)

Tags: [active-exploitation](<https://devfeed.tech/tags/active-exploitation.md>), [actively-exploited](<https://devfeed.tech/tags/actively-exploited.md>), [bod-26-04](<https://devfeed.tech/tags/bod-26-04.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cisa](<https://devfeed.tech/tags/cisa.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [credentials](<https://devfeed.tech/tags/credentials.md>), [devsecops-platform](<https://devfeed.tech/tags/devsecops-platform.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [exposed](<https://devfeed.tech/tags/exposed.md>), [federal-agencies](<https://devfeed.tech/tags/federal-agencies.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [integer-overflow](<https://devfeed.tech/tags/integer-overflow.md>), [kev-catalog](<https://devfeed.tech/tags/kev-catalog.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [patched](<https://devfeed.tech/tags/patched.md>), [rce](<https://devfeed.tech/tags/rce.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [security](<https://devfeed.tech/tags/security.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [support](<https://devfeed.tech/tags/support.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

CISA confirmed active exploitation of CVE-2026-97229, a critical integer overflow flaw in GitLab's CI/CD Regular Expression Compiler. A specially crafted regular expression in a pipeline configuration could allow an unauthenticated remote attacker to execute arbitrary code on a GitLab server. GitLab fixed the issue in CE and EE versions 19.4.2, 19.3.5, and 19.2.8 and urged administrators to patch; it also released threat detections for self-managed instances. CISA added the flaw to its Known Exploited Vulnerabilities catalog and set a Sunday remediation deadline for federal agencies, while urging other security teams to prioritize patching. Shadowserver tracks nearly 2,800 internet-exposed GitLab CE instances, but the excerpt does not say how many are secured.

### Source excerpt

Attackers have started exploiting a maximum-severity GitLab vulnerability patched earlier this month, according to the US Cybersecurity and Infrastructure Security Agency (CISA). [...]

## Max-Severity GitLab Vulnerability Exploited Against Alpine Linux

DevFeed: [Max-Severity GitLab Vulnerability Exploited Against Alpine Linux](<https://devfeed.tech/articles/max-severity-gitlab-vulnerability-exploited-against-alpine-linux-107600.md>)

Original publisher: [Read original article](<https://www.securityweek.com/max-severity-gitlab-vulnerability-exploited-against-alpine-linux/>)

Author: Ionut Arghire

Published: 2026-10-30T09:32:27Z

Content type: news

Language: en

Sources: [SecurityWeek](<https://devfeed.tech/sources/securityweek.md>)

Topics: [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [Exploit](<https://devfeed.tech/topics/exploit.md>), [GitLab](<https://devfeed.tech/topics/gitlab.md>), [Linux](<https://devfeed.tech/topics/linux.md>)

Tags: [account](<https://devfeed.tech/tags/account.md>), [actor](<https://devfeed.tech/tags/actor.md>), [added](<https://devfeed.tech/tags/added.md>), [adobe](<https://devfeed.tech/tags/adobe.md>), [agencies](<https://devfeed.tech/tags/agencies.md>), [all](<https://devfeed.tech/tags/all.md>), [allowed](<https://devfeed.tech/tags/allowed.md>), [alpine](<https://devfeed.tech/tags/alpine.md>), [alpine-linux](<https://devfeed.tech/tags/alpine-linux.md>), [also](<https://devfeed.tech/tags/also.md>), [attack](<https://devfeed.tech/tags/attack.md>), [bug](<https://devfeed.tech/tags/bug.md>), [cisa-kev](<https://devfeed.tech/tags/cisa-kev.md>), [code](<https://devfeed.tech/tags/code.md>), [cve](<https://devfeed.tech/tags/cve.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [featured](<https://devfeed.tech/tags/featured.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [gitlab-vulnerability](<https://devfeed.tech/tags/gitlab-vulnerability.md>), [linux](<https://devfeed.tech/tags/linux.md>), [server](<https://devfeed.tech/tags/server.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>)

### AI overview

CVE-2026-97229 is a maximum-severity flaw in Ruby's Onigmo regular-expression engine that can let unauthenticated users execute code through crafted GitLab CI/CD configuration. Alpine Linux reported an exploit attempt on October 20-21 that crashed workers; the attacker partly progressed in four attempts and downloaded Alpine's GitLab container image, but Alpine found no evidence of server code execution and could not rule it out. Alpine rebuilt the instance, found no tampering in its repository, packages, or October 21 releases, and reset passwords while investigating before reopening GitLab. Updating GitLab to 19.3.6 did not fix the issue in Alpine's image because the flaw is in Ruby. Operators using their own Ruby must also upgrade to Ruby 3.3.13, 3.4.12, 4.0.9, or later. CISA added the vulnerability to its KEV catalog and directed federal agencies to patch within three days.

### Source excerpt

Tracked as CVE-2026-97229, the bug allows unauthenticated attackers to execute arbitrary code on the server. The post Max-Severity GitLab Vulnerability Exploited Against Alpine Linux appeared first on SecurityWeek.

## CISA Adds Actively Exploited GitLab RCE and Cisco Firewall DoS Flaws to KEV

DevFeed: [CISA Adds Actively Exploited GitLab RCE and Cisco Firewall DoS Flaws to KEV](<https://devfeed.tech/articles/cisa-adds-actively-exploited-gitlab-rce-and-cisco-firewall-dos-flaws-to-kev-107733.md>)

Original publisher: [Read original article](<https://thehackernews.com/2026/10/cisa-adds-actively-exploited-gitlab-rce.html>)

Author: The Hacker News

Published: 2026-10-30T07:27:05Z

Content type: news

Language: en

Sources: [Cyber Newsroom](<https://devfeed.tech/sources/cyber-newsroom.md>)

Topics: [known exploitable vulnerabilities](<https://devfeed.tech/topics/known-exploitable-vulnerabilities.md>), [cybersecurity and infrastructure security agency](<https://devfeed.tech/topics/cybersecurity-and-infrastructure-security-agency.md>), [GitLab](<https://devfeed.tech/topics/gitlab.md>), [Cisco](<https://devfeed.tech/topics/cisco.md>), [gitlab-ci](<https://devfeed.tech/topics/gitlab-ci.md>), [cve remediation](<https://devfeed.tech/topics/cve-remediation.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [active-exploitation](<https://devfeed.tech/tags/active-exploitation.md>), [actively-exploited](<https://devfeed.tech/tags/actively-exploited.md>), [added](<https://devfeed.tech/tags/added.md>), [cisa](<https://devfeed.tech/tags/cisa.md>), [cisco](<https://devfeed.tech/tags/cisco.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-76418](<https://devfeed.tech/tags/cve-2026-76418.md>), [cyber-attack](<https://devfeed.tech/tags/cyber-attack.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [cybersecurity-and-infrastructure-security-agency](<https://devfeed.tech/tags/cybersecurity-and-infrastructure-security-agency.md>), [devsecops](<https://devfeed.tech/tags/devsecops.md>), [dos](<https://devfeed.tech/tags/dos.md>), [exploited](<https://devfeed.tech/tags/exploited.md>), [exploited-vulnerabilities](<https://devfeed.tech/tags/exploited-vulnerabilities.md>), [firewall](<https://devfeed.tech/tags/firewall.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [kev](<https://devfeed.tech/tags/kev.md>), [linux](<https://devfeed.tech/tags/linux.md>), [network-security](<https://devfeed.tech/tags/network-security.md>), [rce](<https://devfeed.tech/tags/rce.md>), [security](<https://devfeed.tech/tags/security.md>), [software](<https://devfeed.tech/tags/software.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [web-security](<https://devfeed.tech/tags/web-security.md>)

### AI overview

CISA added two actively exploited flaws to its KEV: GitLab CVE-2026-97229 (CVSS 10.0), an integer overflow that can enable unauthenticated code execution through a crafted CI/CD configuration, and Cisco ASA/FTD CVE-2026-76418 (CVSS 8.6), which can let a remote unauthenticated attacker trigger a reload and denial of service. Alpine Linux reported that an attempted GitLab exploit in October crashed worker processes but found no evidence it succeeded; it rebuilt the instance and said its repositories, packages, and October 21 releases were not tampered with. Cisco had reported active exploitation of its flaw but had not identified the attackers, targets, or follow-on actions. CISA recommended that FCEB agencies apply fixes by November 1, 2026.

### Source excerpt

CISA Adds Actively Exploited GitLab RCE and Cisco Firewall DoS Flaws to KEV The U.S. Cybersecurity and Infrastructure Security Agency (CISA) on Thursday added two security flaws impacting Cisco and GitLab software to its Known Exploited Vulnerabilities (KEV), citing evidence ... Read more Published Date: Oct 30, 2026 (4 hours, 46 minutes ago) Vulnerabilities has been mentioned in this article. CVE-2026-76418 CVE-2026-97229

## Attacker Tried to Exploit Alpine Linux's GitLab via CVSS 10.0 Flaw Its Ruby Left Open

DevFeed: [Attacker Tried to Exploit Alpine Linux's GitLab via CVSS 10.0 Flaw Its Ruby Left Open](<https://devfeed.tech/articles/attacker-tried-to-exploit-alpine-linux-s-gitlab-via-cvss-10-0-flaw-its-ruby-left-open-106310.md>)

Original publisher: [Read original article](<https://thehackernews.com/2026/10/attacker-tried-to-exploit-alpine-linuxs.html>)

Author: The Hacker News

Published: 2026-10-29T09:05:39Z

Content type: news

Language: en

Sources: [Cyber Newsroom](<https://devfeed.tech/sources/cyber-newsroom.md>)

Topics: [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [GitLab](<https://devfeed.tech/topics/gitlab.md>), [Ruby](<https://devfeed.tech/topics/ruby.md>), [gitlab-ci](<https://devfeed.tech/topics/gitlab-ci.md>), [Linux](<https://devfeed.tech/topics/linux.md>)

Tags: [alpine-linux](<https://devfeed.tech/tags/alpine-linux.md>), [attack](<https://devfeed.tech/tags/attack.md>), [build](<https://devfeed.tech/tags/build.md>), [built-from-source](<https://devfeed.tech/tags/built-from-source.md>), [ci](<https://devfeed.tech/tags/ci.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [cisa](<https://devfeed.tech/tags/cisa.md>), [code](<https://devfeed.tech/tags/code.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [commands](<https://devfeed.tech/tags/commands.md>), [compile](<https://devfeed.tech/tags/compile.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [cyber-attack](<https://devfeed.tech/tags/cyber-attack.md>), [exploit](<https://devfeed.tech/tags/exploit.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [gitlab-vulnerability](<https://devfeed.tech/tags/gitlab-vulnerability.md>), [linux](<https://devfeed.tech/tags/linux.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [software-security](<https://devfeed.tech/tags/software-security.md>), [supply-chain](<https://devfeed.tech/tags/supply-chain.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [web-security](<https://devfeed.tech/tags/web-security.md>)

### AI overview

CVE-2026-97229 is a critical flaw in Ruby's Onigmo regular expression engine that can enable code execution through crafted GitLab CI configuration. Alpine Linux said an attacker probed its server while it was unpatched; it found no evidence of code execution but could not rule it out, so it rebuilt the server, replaced secret keys, and reset account passwords. The GitLab upgrade alone failed to fix Alpine's installation because its image used system Ruby rather than GitLab's bundled, patched Ruby. Administrators using GitLab's Linux package or official images should upgrade to the latest release for their branch; self-compiled installs and images with separately installed Ruby also need Ruby 3.3.13, 3.4.12, 4.0.9, or later. Alpine users should pull its 19.3.6 image again: only the version published on 27 October includes the fixed Ruby. The excerpt also notes limits in Alpine's forensic evidence and that temporary access restrictions suggested for one exploit route do not fix the underlying flaw.

### Source excerpt

Attacker Tried to Exploit Alpine Linux's GitLab via CVSS 10.0 Flaw Its Ruby Left Open An attacker tried to exploit a critical GitLab vulnerability on the Alpine Linux project's own GitLab server a week after GitLab released a fix, Alpine Linux said on 28 October. The flaw, CVE-2026-972 ... Read more Published Date: Oct 29, 2026 (5 hours, 7 minutes ago) Vulnerabilities has been mentioned in this article. CVE-2026-110264 CVE-2026-97229

## GitLab Orbit is GA: Higher agent accuracy, lower token cost

DevFeed: [GitLab Orbit is GA: Higher agent accuracy, lower token cost](<https://devfeed.tech/articles/gitlab-orbit-is-ga-higher-agent-accuracy-lower-token-cost-106403.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/gitlab-orbit-ga/>)

Author: Gabriel Engel

Published: 2026-10-29T00:00:00Z

Content type: release

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [AI Integration Strategies](<https://devfeed.tech/topics/ai-integration-strategies.md>), [Claude Code](<https://devfeed.tech/topics/claude-code.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [gitlab-ci](<https://devfeed.tech/topics/gitlab-ci.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [backend](<https://devfeed.tech/tags/backend.md>), [claude-code](<https://devfeed.tech/tags/claude-code.md>), [code](<https://devfeed.tech/tags/code.md>), [confidence](<https://devfeed.tech/tags/confidence.md>), [context](<https://devfeed.tech/tags/context.md>), [context-graph](<https://devfeed.tech/tags/context-graph.md>), [cost](<https://devfeed.tech/tags/cost.md>), [costs](<https://devfeed.tech/tags/costs.md>), [features](<https://devfeed.tech/tags/features.md>), [fewer](<https://devfeed.tech/tags/fewer.md>), [files](<https://devfeed.tech/tags/files.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [lifecycle](<https://devfeed.tech/tags/lifecycle.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [merge](<https://devfeed.tech/tags/merge.md>), [model](<https://devfeed.tech/tags/model.md>), [news](<https://devfeed.tech/tags/news.md>), [orbit](<https://devfeed.tech/tags/orbit.md>), [product](<https://devfeed.tech/tags/product.md>), [token](<https://devfeed.tech/tags/token.md>), [token-cost](<https://devfeed.tech/tags/token-cost.md>)

### AI overview

GitLab Orbit is generally available as a live, queryable graph linking code with merge requests, work items, pipelines, vulnerabilities, deployments, and ownership. GitLab says that, in its tests, agents using Orbit needed up to 45 times fewer retries and 4.5 times fewer tokens on the same tasks with the same model. In Compare the Market's evaluation across 79 real merge requests, an Orbit-grounded reviewer matched about 70% of expected inline comments, versus about 58% for RAG, which performed worse than adding no context. Agents can query the shared graph through Duo, MCP-compatible tools such as Claude Code or Codex, REST, or the Data Explorer; Orbit mirrors GitLab permissions and draws on existing GitLab data. It is offered to Premium and Ultimate customers, with pricing based on shared query packs: $30 in GitLab Credits per user monthly for 1,000 queries, with additional usage billed at 33 queries per Credit. Availability starts on GitLab.com, with Self-Managed and GitLab Dedicated to follow.

### Source excerpt

An agent's true cost isn't only the tokens it burns. It's the review that calls your code "safe to merge" after seeing the diff, but without any context on the pipeline. We call that artificial confidence, not artificial intelligence. Agents guess because code is all they can see; they can't see the merge request that last changed it, the pipeline that ran it, the vulnerability it carries, or the people who wrote and reviewed it. Guessing is expensive. If you've tried running agents in a large monorepo, one with tens of thousands of files, you know how it goes: the agent iterates, pinging the backend again and again for the information it needs to complete the task. Every round trip costs more time and more tokens. Eventually the agent gives up. The model isn't the constraint. Context is. That's the constraint that GitLab Orbit removes. Now generally available, Orbit is the context graph for your software lifecycle: a live, queryable view of all your code, merge requests, work items, pipelines, vulnerabilities, and ownership, with every relationship continuously updated as you ship. Every agent and engineer can work from one connected view of the lifecycle. In GitLab testing, agents connected to Orbit needed up to 45x fewer retries and used 4.5x fewer tokens on the same tasks with the same model. Grounded agents get answers right the first time An agent like Claude Code, connected to GitLab Orbit through MCP, stops crawling files and instead asks the graph. The first response comes back with real callers, recent changes, and owners, so your follow-up prompts can refine the answer rather than correct it. The difference is measurable. Compare the Market, one of the UK's largest price comparison platforms, tested four context approaches for an internal AI code reviewer across 79 real merge requests. The GitLab Orbit-grounded reviewer matched about 70% of expected inline comments; RAG managed about 58%, worse than no added context at all. "GitLab Orbit gave us an AI cod

## Extend GitLab Duo Agent Platform into your business systems

DevFeed: [Extend GitLab Duo Agent Platform into your business systems](<https://devfeed.tech/articles/extend-gitlab-duo-agent-platform-into-your-business-systems-102391.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/extend-gitlab-duo-agent-platform-into-your-business-systems/>)

Author: Harshit Bhandari

Published: 2026-10-27T00:00:00Z

Content type: tutorial

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [Error Handling](<https://devfeed.tech/topics/error-handling.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [agent orchestration](<https://devfeed.tech/topics/agent-orchestration.md>)

Tags: [agent](<https://devfeed.tech/tags/agent.md>), [ai](<https://devfeed.tech/tags/ai.md>), [analysis](<https://devfeed.tech/tags/analysis.md>), [api](<https://devfeed.tech/tags/api.md>), [automatically](<https://devfeed.tech/tags/automatically.md>), [build](<https://devfeed.tech/tags/build.md>), [business](<https://devfeed.tech/tags/business.md>), [button](<https://devfeed.tech/tags/button.md>), [call](<https://devfeed.tech/tags/call.md>), [cause](<https://devfeed.tech/tags/cause.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [class](<https://devfeed.tech/tags/class.md>), [code](<https://devfeed.tech/tags/code.md>), [custom](<https://devfeed.tech/tags/custom.md>), [devsecops](<https://devfeed.tech/tags/devsecops.md>), [duo](<https://devfeed.tech/tags/duo.md>), [engineer](<https://devfeed.tech/tags/engineer.md>), [extend](<https://devfeed.tech/tags/extend.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [integrations](<https://devfeed.tech/tags/integrations.md>), [platform](<https://devfeed.tech/tags/platform.md>), [systems](<https://devfeed.tech/tags/systems.md>), [tutorial](<https://devfeed.tech/tags/tutorial.md>)

### AI overview

A Salesforce error can trigger a GitLab Duo Agent Platform custom flow through the Flows API; the flow examines Salesforce metadata stored in GitLab and opens an issue with cited root-cause analysis. The tutorial uses a narrowly scoped flow with file and commit reading plus issue creation, and recommends either queueing it from Apex exception handling or invoking it on demand. Setup requires GitLab Premium or Ultimate (GitLab.com or GitLab 19.5+), Duo Agent Platform with custom flows enabled, Salesforce metadata in a GitLab project, and a project access token with the `api` scope and at least Developer role. The example stores that token in a Salesforce Named Credential and runs callouts in a Queueable. It warns that transaction rollback discards queued work and that the sample omits response checks, retries, and tests. Before production, strip sensitive data from error reports, minimize privileges, scope and rotate the token, and keep an engineer responsible for decisions. The same HTTP-triggered pattern is described as applicable to other systems.

### Source excerpt

Developers mostly use GitLab Duo Agent Platform where they already work: the IDE, merge requests, and issues. But DevSecOps teams also support the business systems the rest of the company runs on, and those systems break too. In Salesforce, for example, when a validation fails, a callout times out, or a null slips through a trigger, the error gets logged, but the log doesn't explain the cause. An engineer still has to read the stack trace, find the class in the repository, check what changed recently, and decide whether this is a one-off or a regression. Meanwhile, the business user who hit the error has to wait. When your Salesforce metadata lives in GitLab and ships through GitLab CI/CD, the code that explains the error is already there. In this tutorial, Salesforce calls a custom GitLab Duo Agent Platform flow through the Flows API the moment an error happens. The flow investigates the code, and your team gets a GitLab issue that already contains the root-cause analysis. Along the way, three parts of the GitLab platform work together: GitLab Duo Agent Platform investigates the error, a GitLab issue tracks the work, and GitLab CI/CD runs the flow and ships the fix. Salesforce is the example we'll walk through in this tutorial, but the same approach works for any system that can make an HTTP request. What you'll build Salesforce makes one call to GitLab. A custom flow in GitLab Duo Agent Platform does the rest. Errors reach GitLab Duo Agent Platform automatically from your Apex error handling, or on demand from a button. Either way, the same Apex job calls the Flows API, and the flow opens an issue with its analysis. Prerequisites GitLab Premium or Ultimate, on GitLab.com or GitLab 19.5 and later. The Flows API used in this tutorial is generally available from 19.5. GitLab Duo Agent Platform turned on, with custom flows allowed for your top-level group. Your Salesforce metadata (Apex classes, triggers, Flows) stored in a GitLab project. This is the project the flow

## Pillow CVE-2026-112900: How to find and fix it with GitLab

DevFeed: [Pillow CVE-2026-112900: How to find and fix it with GitLab](<https://devfeed.tech/articles/pillow-cve-2026-112900-how-to-find-and-fix-it-with-gitlab-102392.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/pillow-cve-find-and-fix-with-gitlab/>)

Author: Daniel Abeles

Published: 2026-10-26T00:00:00Z

Content type: tutorial

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [Image](<https://devfeed.tech/topics/image.md>), [CVSS v4.0](<https://devfeed.tech/topics/cvss-v4-0.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [container images](<https://devfeed.tech/topics/container-images.md>)

Tags: [argument-injection](<https://devfeed.tech/tags/argument-injection.md>), [cve](<https://devfeed.tech/tags/cve.md>), [dependency](<https://devfeed.tech/tags/dependency.md>), [dependency-scanning](<https://devfeed.tech/tags/dependency-scanning.md>), [ghostscript](<https://devfeed.tech/tags/ghostscript.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [guide](<https://devfeed.tech/tags/guide.md>), [how-to](<https://devfeed.tech/tags/how-to.md>), [orbit](<https://devfeed.tech/tags/orbit.md>), [python](<https://devfeed.tech/tags/python.md>), [scanning](<https://devfeed.tech/tags/scanning.md>), [search](<https://devfeed.tech/tags/search.md>), [security](<https://devfeed.tech/tags/security.md>), [security-fixes](<https://devfeed.tech/tags/security-fixes.md>), [security-labs](<https://devfeed.tech/tags/security-labs.md>), [security-research](<https://devfeed.tech/tags/security-research.md>), [upgrade](<https://devfeed.tech/tags/upgrade.md>), [version](<https://devfeed.tech/tags/version.md>)

### AI overview

Pillow versions 2.6.0 through 12.x are affected by CVE-2026-112900, a critical argument injection in the Ghostscript call used to render EPS images; the supplied text says no in-the-wild exploitation has been reported. Upgrade to Pillow 13.0.0 or later, checking distribution security trackers because package versions and fixes vary. Rebuild and redeploy containers, update pinned versions, and check upstream base images. If upgrading is delayed, use generated filenames, restrict accepted image formats, or remove Ghostscript where EPS support is unnecessary. The excerpt recommends locating dependencies with GitLab dependency and container scanning, GitLab Orbit, and code search, then prioritizing projects that combine Pillow, Ghostscript, and uploads. GitLab Duo Agent Platform can help create project issues and merge requests, but people still need to review and merge changes, run image-processing tests for changed TIFF and PNG behavior, and confirm deployment. GitLab products and managed infrastructure are stated to be unaffected.

### Source excerpt

GitLab is not affected by CVE-2026-112900 or the other vulnerabilities fixed in Pillow 13.0.0. GitLab products do not include the Pillow library, and our Security team has found no evidence of impact to GitLab-managed infrastructure. GitLab.com, GitLab Self-Managed, and GitLab Dedicated are not impacted. Pillow is one of the most widely used image libraries in the Python ecosystem. It often sits several layers down in a dependency tree, pulled in by a web framework, a thumbnailing service or an ML toolkit that nobody chose it for directly. On October 16, 2026, the Pillow project released version 13.0.0, and one of its security fixes is CVE-2026-112900: an argument injection in the way Pillow calls Ghostscript to render EPS images. The CVE record, published on October 19, rates it 9.2 (Critical) on CVSS 4.0. It affects every Pillow release from 2.6.0 up to, but not including, 13.0.0. No exploitation in the wild has been reported so far, but CISA's assessment marks it as automatable with total technical impact. Upgrade Pillow to 13.0.0 on every project and image that handles untrusted images, and remove Ghostscript from images that do not need EPS support. This guide is for security and platform teams with Python projects on GitLab. It covers the fixed version for each distribution, how the flaw works, the other High and Critical issues fixed in the same release, how to locate affected projects with dependency scanning, container scanning, GitLab Orbit, and code search, and how to remediate at scale with GitLab Duo Agent Platform. CVE-2026-112900 at a glance CVE-2026-112900 is an OS command and argument injection flaw in Pillow's EPS plugin, rated Critical (CVSS 4.0 score of 9.2) by the CVE Numbering Authority (CNA). The CVE record was published on October 19, 2026. FieldDetailCVECVE-2026-112900GitHub advisoryGHSA-w889-685w-c8fhTitlePillow: Argument Injection in Ghostscript call, potentially leading into RCEWeaknessCWE-88 (argument injection), CWE-78 (OS command injec

## GitLab AI API and CI Agents

DevFeed: [GitLab AI API and CI Agents](<https://devfeed.tech/articles/gitlab-ai-api-and-ci-agents-98752.md>)

Original publisher: [Read original article](<https://www.swytchcode.com/content/gitlab-ai-api>)

Author: Chaitrali Kakde

Published: 2026-10-24T10:33:19.077565Z

Content type: article

Language: en

Sources: [Swytchcode](<https://devfeed.tech/sources/swytchcode.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [Access Control](<https://devfeed.tech/topics/access-control.md>), [API](<https://devfeed.tech/topics/api.md>), [personal access token](<https://devfeed.tech/topics/personal-access-token.md>), [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [gitlab-ci](<https://devfeed.tech/topics/gitlab-ci.md>), [Pull Request](<https://devfeed.tech/topics/pull-request.md>), [human in the loop agent](<https://devfeed.tech/topics/human-in-the-loop-agent.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>)

Tags: [403](<https://devfeed.tech/tags/403.md>), [access-control](<https://devfeed.tech/tags/access-control.md>), [accountability](<https://devfeed.tech/tags/accountability.md>), [administrator](<https://devfeed.tech/tags/administrator.md>), [agent](<https://devfeed.tech/tags/agent.md>), [agents](<https://devfeed.tech/tags/agents.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [ai-agents](<https://devfeed.tech/tags/ai-agents.md>), [ai-api](<https://devfeed.tech/tags/ai-api.md>), [api](<https://devfeed.tech/tags/api.md>), [api-access](<https://devfeed.tech/tags/api-access.md>), [audit](<https://devfeed.tech/tags/audit.md>), [ci](<https://devfeed.tech/tags/ci.md>), [engineering](<https://devfeed.tech/tags/engineering.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [permissions](<https://devfeed.tech/tags/permissions.md>), [personal-access-token](<https://devfeed.tech/tags/personal-access-token.md>), [project](<https://devfeed.tech/tags/project.md>), [security](<https://devfeed.tech/tags/security.md>), [token](<https://devfeed.tech/tags/token.md>)

### AI overview

GitLab agent security depends first on token scope: a project access token limits exposure to one project, while a personal token carries the user's permissions across projects they can access. Use `read_api` for analysis because GitLab enforces it as read-only for most GET and HEAD endpoints; reserve `api` for a separate agent that needs to comment. The excerpt recommends allowing review comments while excluding merges, approvals, branch deletion, and CI variable access, which could expose deployment credentials. It also advises using the `PRIVATE-TOKEN` header, honoring `Retry-After` on rate limits, specifying whether an MR pipeline tests the source branch or merged result, and using idempotency keys plus existing-note checks to prevent duplicate comments. CI job tokens may suit pipeline agents if required endpoints are supported. The supplied text also describes Swytchcode setup and example review, pipeline-explanation, stale-MR, and release-note workflows.

### Source excerpt

A personal access token gives your agent your permissions across every project you can see. A project access token gives it one project. That choice is the whole security model.

## Ruby Fixes Three Regex Engine Bugs Responsible for Four Critical GitLab RCE Flaws

DevFeed: [Ruby Fixes Three Regex Engine Bugs Responsible for Four Critical GitLab RCE Flaws](<https://devfeed.tech/articles/ruby-fixes-three-regex-engine-bugs-responsible-for-four-critical-gitlab-rce-flaws-98290.md>)

Original publisher: [Read original article](<https://thehackernews.com/2026/10/ruby-fixes-three-regex-engine-bugs.html>)

Author: The Hacker News

Published: 2026-10-23T17:54:08Z

Content type: news

Language: en

Sources: [Cyber Newsroom](<https://devfeed.tech/sources/cyber-newsroom.md>)

Topics: [Ruby](<https://devfeed.tech/topics/ruby.md>), [GitLab](<https://devfeed.tech/topics/gitlab.md>), [Regular expression](<https://devfeed.tech/topics/regular-expression.md>), [bugfixes](<https://devfeed.tech/topics/bugfixes.md>), [Memory Safety](<https://devfeed.tech/topics/memory-safety.md>), [Bug Bounty](<https://devfeed.tech/topics/bugbounty.md>), [gitlab-ci](<https://devfeed.tech/topics/gitlab-ci.md>), [cybersecurity and infrastructure security agency](<https://devfeed.tech/topics/cybersecurity-and-infrastructure-security-agency.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [application-security](<https://devfeed.tech/tags/application-security.md>), [applications](<https://devfeed.tech/tags/applications.md>), [bug-bounty](<https://devfeed.tech/tags/bug-bounty.md>), [bugs](<https://devfeed.tech/tags/bugs.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [compile](<https://devfeed.tech/tags/compile.md>), [copy](<https://devfeed.tech/tags/copy.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-110264](<https://devfeed.tech/tags/cve-2026-110264.md>), [cves](<https://devfeed.tech/tags/cves.md>), [engine](<https://devfeed.tech/tags/engine.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [rce](<https://devfeed.tech/tags/rce.md>), [regex](<https://devfeed.tech/tags/regex.md>), [regular](<https://devfeed.tech/tags/regular.md>), [ruby](<https://devfeed.tech/tags/ruby.md>), [security](<https://devfeed.tech/tags/security.md>), [software-security](<https://devfeed.tech/tags/software-security.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [web-security](<https://devfeed.tech/tags/web-security.md>)

### AI overview

Ruby 4.0.9, 3.4.12, and 3.3.13 fix three Onigmo bugs tied to four critical GitLab remote code execution flaws. Applications are affected when they compile attacker-controlled regex text through Regexp.new, Regexp.union, Regexp.compile, or interpolation; apps using only developer-written patterns are not affected. Ruby says Regexp.timeout and pattern-length caps do not reliably prevent the bugs. Ruby 3.2 and earlier will not receive fixes; it recommends upgrading to 3.4 or 4.0, or avoiding regex compilation from untrusted input until then. For self-managed GitLab, install a release patched for CVE-2026-110264 (18.11.13 or the listed newer release branches); GitLab.com is already patched. Ruby has not assigned its own CVEs for these fixes, which may limit scanners that rely on CVE records.

### Source excerpt

Ruby Fixes Three Regex Engine Bugs Responsible for Four Critical GitLab RCE Flaws Ruby has released versions 4.0.9, 3.4.12, and 3.3.13 to fix three bugs in Onigmo, the regular expression engine built into the language. The bugs lie behind four critical security flaws that GitLab pa ... Read more Published Date: Oct 23, 2026 (1 hour, 46 minutes ago) Vulnerabilities has been mentioned in this article. CVE-2026-110264 CVE-2026-97229 CVE-2024-27282 CVE-2022-28738

## GitLab critical patches include one for a bug that allows code execution by unauthenticated users

DevFeed: [GitLab critical patches include one for a bug that allows code execution by unauthenticated users](<https://devfeed.tech/articles/gitlab-critical-patches-include-one-for-a-bug-that-allows-code-execution-by-unauthenticated-users-96307.md>)

Original publisher: [Read original article](<https://www.infoworld.com/article/4239276/gitlab-critical-patches-include-one-for-a-bug-that-allows-code-execution-by-unauthenticated-users.html>)

Author: Evan Schuman

Published: 2026-10-22T20:21:23Z

Content type: news

Language: en

Sources: [InfoWorld](<https://devfeed.tech/sources/infoworld.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [patches](<https://devfeed.tech/topics/patches.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [AI Chat](<https://devfeed.tech/topics/ai-chat.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-agent](<https://devfeed.tech/tags/ai-agent.md>), [authentication](<https://devfeed.tech/tags/authentication.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [critical](<https://devfeed.tech/tags/critical.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [gitlab-security-software-development-version-control-systems-vulnerabilities](<https://devfeed.tech/tags/gitlab-security-software-development-version-control-systems-vulnerabilities.md>), [integer-overflow](<https://devfeed.tech/tags/integer-overflow.md>), [language-en](<https://devfeed.tech/tags/language-en.md>), [ldap](<https://devfeed.tech/tags/ldap.md>), [patches](<https://devfeed.tech/tags/patches.md>), [regex](<https://devfeed.tech/tags/regex.md>), [security](<https://devfeed.tech/tags/security.md>), [software-development](<https://devfeed.tech/tags/software-development.md>), [storytype-news](<https://devfeed.tech/tags/storytype-news.md>), [version-control-systems](<https://devfeed.tech/tags/version-control-systems.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

GitLab's CE and EE updates address a critical integer overflow in Ruby regular-expression compilation that could let an unauthenticated user execute code on the server, plus a high-severity OmniAuth SAML and LDAP auto-linking flaw that could let an authenticated user take over an LDAP-backed account. Affected releases include versions before 18.11.13, 19.0.10, 19.1.9, 19.2.9, 19.3.6, 19.4.3 and 19.5.1 in the listed branches; those versions and later patched releases contain the fixes. The excerpt says patches include database migrations and single-node instances will be down during them. It also highlights checking older or forgotten GitLab instances and asking other vendors about possible Ruby regex exposure.

### Source excerpt

GitLab on Wednesday published updated versions of its Community Edition (CE) and Enterprise Edition (EE) that address a dozen bugs and security issues, including some that allow various unauthenticated actions. The most serious of the security issues, labeled critical in severity, is CVE-2026-110264, an integer overflow issue. "GitLab has remediated an issue that, under certain conditions, could have allowed an unauthenticated user to execute arbitrary code on the GitLab server due to integer overflow when compiling a specially crafted regular expression," GitLab said in its bulletin. "In addition to our standard patch releases, we have backported this fix to GitLab CE/EE versions 18.11.13, 19.0.10, 19.1.9, and 19.2.9." Impacted versions of GitLab CE/EE include all versions from 7.0 before 18.11.13, 19.0 before 19.0.10, 19.1 before 19.1.9, 19.2 before 19.2.9, 19.3 before 19.3.6, 19.4 before 19.4.3, and 19.5 before 19.5.1. The patched releases are versions 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10 and 18.11.13. The patches also fix a high severity flaw tracked as CVE-2026-15723, an improper authentication issue in OmniAuth-to-LDAP auto-linking email lookup that impacts GitLab CE/EE, which is an issue, GitLab said, because "when OmniAuth SAML and LDAP auto-linking were both enabled, an authenticated user could have taken over an existing LDAP-backed account without any interaction from the targeted user, due to improper input sanitization in the LDAP email lookup path used during OmniAuth identity linking." This is the fourth critical security issue that GitLab has experienced within two months. Earlier in October, it patched a maximum severity regex flaw, and in September, it fixed CVE-2026-85706, also rated perfect 10 in severity. Another September report also revealed a concerning issue: a long-lived token that puts CI/CD security at risk. Immediate action needed Analysts and consultants agreed that the current holes are serious and merit immediate action. "W

## GitLab Releases Critical Security Patches

DevFeed: [GitLab Releases Critical Security Patches](<https://devfeed.tech/articles/gitlab-releases-critical-security-patches-98279.md>)

Original publisher: [Read original article](<https://thecyberthrone.in/2026/10/22/gitlab-releases-critical-security-patches/>)

Author: PravinKarthik

Published: 2026-10-22T13:32:24Z

Content type: release

Language: en

Sources: [Cyber Newsroom](<https://devfeed.tech/sources/cyber-newsroom.md>)

Topics: [Vulnerabilities](<https://devfeed.tech/topics/vulnerabilities.md>), [GitLab](<https://devfeed.tech/topics/gitlab.md>), [patches](<https://devfeed.tech/topics/patches.md>), [Security](<https://devfeed.tech/topics/security.md>), [releases](<https://devfeed.tech/topics/releases.md>), [code security](<https://devfeed.tech/topics/code-security.md>)

Tags: [2026](<https://devfeed.tech/tags/2026.md>), [access-controls](<https://devfeed.tech/tags/access-controls.md>), [ai](<https://devfeed.tech/tags/ai.md>), [ai-features](<https://devfeed.tech/tags/ai-features.md>), [ai-gateway](<https://devfeed.tech/tags/ai-gateway.md>), [api](<https://devfeed.tech/tags/api.md>), [community-edition](<https://devfeed.tech/tags/community-edition.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-110264](<https://devfeed.tech/tags/cve-2026-110264.md>), [cybersecurity](<https://devfeed.tech/tags/cybersecurity.md>), [enterprise](<https://devfeed.tech/tags/enterprise.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [october](<https://devfeed.tech/tags/october.md>), [patches](<https://devfeed.tech/tags/patches.md>), [release](<https://devfeed.tech/tags/release.md>), [releases](<https://devfeed.tech/tags/releases.md>), [remote](<https://devfeed.tech/tags/remote.md>), [security](<https://devfeed.tech/tags/security.md>), [security-patches](<https://devfeed.tech/tags/security-patches.md>), [security-vulnerabilities](<https://devfeed.tech/tags/security-vulnerabilities.md>), [vulnerabilities](<https://devfeed.tech/tags/vulnerabilities.md>)

### AI overview

GitLab's October 21, 2026 patch fixes 12 vulnerabilities in CE and EE, led by CVE-2026-110264 (CVSS 10.0): a regular-expression compiler integer overflow that could let an unauthenticated attacker execute code on affected servers. Other fixes cover account takeover, OAuth/OIDC cache poisoning, API access controls, information exposure, merge request approvals and vulnerability records. GitLab recommends affected self-managed installations upgrade to the patched release for their branch: 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10 or 18.11.13. Administrators should verify their installed version against each advisory because affected ranges vary. Single-node upgrades require downtime for database migrations; multi-node deployments can use GitLab's documented zero-downtime procedure. GitLab.com is patched, and the stated later GitLab Dedicated versions already include the fixes.

### Source excerpt

GitLab Releases Critical Security Patches GitLab released a critical patch update on October 21, 2026, fixing 12 security vulnerabilities in GitLab Community Edition (CE) and Enterprise Edition (EE).The release includes a critical remote cod ... Read more Published Date: Oct 22, 2026 (1 day, 6 hours ago) Vulnerabilities has been mentioned in this article. CVE-2026-16255 CVE-2026-15723 CVE-2026-14288 CVE-2026-13319 CVE-2026-12664 CVE-2026-112378 CVE-2026-112326 CVE-2026-112212 CVE-2026-110264 CVE-2026-105777 CVE-2026-105711 CVE-2026-103515

## GitLab warns of new max severity code execution vulnerability

DevFeed: [GitLab warns of new max severity code execution vulnerability](<https://devfeed.tech/articles/gitlab-warns-of-new-max-severity-code-execution-vulnerability-95362.md>)

Original publisher: [Read original article](<https://www.bleepingcomputer.com/news/security/gitlab-warns-of-new-max-severity-code-execution-vulnerability/>)

Author: Sergiu Gatlan

Published: 2026-10-22T11:41:48Z

Content type: news

Language: en

Sources: [BleepingComputer](<https://devfeed.tech/sources/bleepingcomputer.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [code security](<https://devfeed.tech/topics/code-security.md>), [gitlab-ci](<https://devfeed.tech/topics/gitlab-ci.md>)

Tags: [actively-exploited](<https://devfeed.tech/tags/actively-exploited.md>), [ci-cd](<https://devfeed.tech/tags/ci-cd.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [community-edition](<https://devfeed.tech/tags/community-edition.md>), [compiler](<https://devfeed.tech/tags/compiler.md>), [computer-help](<https://devfeed.tech/tags/computer-help.md>), [computer-security](<https://devfeed.tech/tags/computer-security.md>), [computers](<https://devfeed.tech/tags/computers.md>), [cve](<https://devfeed.tech/tags/cve.md>), [devsecops](<https://devfeed.tech/tags/devsecops.md>), [devsecops-platform](<https://devfeed.tech/tags/devsecops-platform.md>), [ee](<https://devfeed.tech/tags/ee.md>), [exposed](<https://devfeed.tech/tags/exposed.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [infosec](<https://devfeed.tech/tags/infosec.md>), [infosec-computer-security](<https://devfeed.tech/tags/infosec-computer-security.md>), [integer-overflow](<https://devfeed.tech/tags/integer-overflow.md>), [linux](<https://devfeed.tech/tags/linux.md>), [mac](<https://devfeed.tech/tags/mac.md>), [malware](<https://devfeed.tech/tags/malware.md>), [malware-removal](<https://devfeed.tech/tags/malware-removal.md>), [rce](<https://devfeed.tech/tags/rce.md>), [regular](<https://devfeed.tech/tags/regular.md>), [remote](<https://devfeed.tech/tags/remote.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [security](<https://devfeed.tech/tags/security.md>), [security-patches](<https://devfeed.tech/tags/security-patches.md>), [spyware](<https://devfeed.tech/tags/spyware.md>), [support](<https://devfeed.tech/tags/support.md>), [tech-support](<https://devfeed.tech/tags/tech-support.md>), [technical-support](<https://devfeed.tech/tags/technical-support.md>), [virus](<https://devfeed.tech/tags/virus.md>), [virus-removal](<https://devfeed.tech/tags/virus-removal.md>), [vulnerability](<https://devfeed.tech/tags/vulnerability.md>), [warning](<https://devfeed.tech/tags/warning.md>), [windows](<https://devfeed.tech/tags/windows.md>)

### AI overview

GitLab says an integer overflow in its Regular Expression Compiler could, under certain conditions, let an unauthenticated attacker execute arbitrary code on a vulnerable server using a specially crafted regular expression. The flaw, CVE-2026-110264, affects GitLab CE and EE; fixes are available in versions 19.5.1, 19.4.3, 19.3.6, 19.2.9, 19.1.9, 19.0.10, and 18.11.13. GitLab recommends upgrading affected installations promptly. GitLab.com is already patched, and Dedicated tenants on 19.3.5-internal0, 19.4.2-internal0, or later do not need to act. The text also reports more than 2,700 internet-exposed CE instances, while noting the count does not distinguish honeypots or systems already secured.

### Source excerpt

GitLab has released security patches for a maximum-severity Regular Expression Compiler flaw that can let remote attackers run arbitrary code on vulnerable servers. [...]

## PHP2Shell: GitLab helps find and remediate critical PHP flaws

DevFeed: [PHP2Shell: GitLab helps find and remediate critical PHP flaws](<https://devfeed.tech/articles/php2shell-gitlab-helps-find-and-remediate-critical-php-flaws-96423.md>)

Original publisher: [Read original article](<https://about.gitlab.com/blog/gitlab-helps-remediate-critical-php-flaws/>)

Author: Dinesh Bolkensteyn

Published: 2026-10-22T00:00:00Z

Content type: tutorial

Language: en

Sources: [GitLab](<https://devfeed.tech/sources/gitlab.md>)

Topics: [GitLab](<https://devfeed.tech/topics/gitlab.md>), [Security research](<https://devfeed.tech/topics/security-research.md>), [gitlab-ci](<https://devfeed.tech/topics/gitlab-ci.md>), [CI/CD](<https://devfeed.tech/topics/cicd.md>), [container image compliance](<https://devfeed.tech/topics/container-image-compliance.md>), [Composer](<https://devfeed.tech/topics/composer.md>), [CVSS v4.0](<https://devfeed.tech/topics/cvss-v4-0.md>)

Tags: [apache](<https://devfeed.tech/tags/apache.md>), [code-execution](<https://devfeed.tech/tags/code-execution.md>), [critical](<https://devfeed.tech/tags/critical.md>), [cve](<https://devfeed.tech/tags/cve.md>), [cve-2026-109618](<https://devfeed.tech/tags/cve-2026-109618.md>), [cve-2026-109619](<https://devfeed.tech/tags/cve-2026-109619.md>), [cvss](<https://devfeed.tech/tags/cvss.md>), [cvss-v4-0](<https://devfeed.tech/tags/cvss-v4-0.md>), [drupal](<https://devfeed.tech/tags/drupal.md>), [features](<https://devfeed.tech/tags/features.md>), [gitlab](<https://devfeed.tech/tags/gitlab.md>), [infrastructure](<https://devfeed.tech/tags/infrastructure.md>), [mod-php](<https://devfeed.tech/tags/mod-php.md>), [nginx](<https://devfeed.tech/tags/nginx.md>), [php](<https://devfeed.tech/tags/php.md>), [php2shell](<https://devfeed.tech/tags/php2shell.md>), [platform-teams](<https://devfeed.tech/tags/platform-teams.md>), [remote-code-execution](<https://devfeed.tech/tags/remote-code-execution.md>), [run](<https://devfeed.tech/tags/run.md>), [runtime](<https://devfeed.tech/tags/runtime.md>), [security](<https://devfeed.tech/tags/security.md>), [security-labs](<https://devfeed.tech/tags/security-labs.md>)

### AI overview

PHP2Shell (CVE-2026-109618 and CVE-2026-109619) comprises two critical PHP engine flaws rated 9.2 on CVSS v4.0; an unauthenticated request can execute code before application code runs. GitLab says its services are unaffected. Upgrade every PHP web runtime and container to a listed fixed version or patched distribution package, restart PHP processes, and rebuild and redeploy images; framework, Composer, validation, and authentication changes do not fix the engine. GitLab container scanning finds package-installed PHP but misses source-built PHP, while exact code search covers declared files on the default branch but does not show what is running. Compare both with a runtime inventory; Kubernetes operational scanning has the same package-only limitation. Review internet-facing server logs from October 17 onward for PHPSESSID response cookies; a successful exploit may return HTTP 200 without errors. If exploitation is suspected, isolate and investigate, preserve evidence before restarting where possible, and rotate credentials accessible to PHP. The excerpt also notes GitLab Dedicated lacks exact code search and that a read-only remediation skill cannot verify inaccessible hosts.

### Source excerpt

GitLab is not affected by PHP2Shell (CVE-2026-109618 and CVE-2026-109619). The GitLab application is not written in PHP and does not run it to serve web requests, and our Security team has found no evidence of impact to GitLab-managed infrastructure. GitLab.com, GitLab Self-Managed, and GitLab Dedicated are not impacted. PHP is a widely used programming language that runs on web servers and powers popular platforms like WordPress, Drupal, and Magento, so a flaw in PHP itself can affect many websites and applications. On October 21, 2026, the PHP project fixed two critical remote code execution flaws in PHP, together known as PHP2Shell (CVE-2026-109618 and CVE-2026-109619). PHP rates both 9.2 on CVSS v4.0. The flaws are in the PHP engine, not in any framework, library, or application code, so there is no application-level fix. Any web server that runs PHP is affected, including NGINX and Apache. The PHP project confirmed the vulnerability on Apache with mod_php, where an unauthenticated request can achieve remote code execution before any application code runs. Upgrade every server and container that runs PHP to serve web requests to PHP 8.5.12, 8.4.27, 8.3.36, or 8.2.35, or to your distribution's patched package now. This guide is for security and platform teams with PHP projects on GitLab. It covers the fixed version for each PHP branch and distribution, how to use GitLab features to locate PHP projects across your groups, how to track remediation, and how to check for signs of compromise. Upgrade PHP to a fixed version now Upgrade the PHP runtime on every host and in every container image to a fixed version. Framework updates, Composer updates, input validation, and authentication don't help, because PHP handles the request before application code runs. BranchFixed inPHP 8.5.x8.5.12PHP 8.4.x8.4.27PHP 8.3.x8.3.36PHP 8.2.x8.2.35 (end of life December 31, 2026)PHP 8.6 release candidates8.6.0RC4. The official php:8.6-rc image was still on RC3 on October 21, and RC3 do

[Next page](<https://devfeed.tech/topics/gitlab.md?cursor=WyIyMDI2LTEwLTIyVDAwOjAwOjAwKzAwOjAwIiwgIjVjZDlkNWE0LTdlODgtNGU4NS1iMTZmLTE5NDczMDEzZGEzMyJd>)