<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Gitlab — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/tags/gitlab/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Mon, 30 Mar 2026 00:16:01 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/tags/gitlab/feed.xml" rel="self" type="application/rss+xml"/><item><title>GitLab Jira Connect Authentication Bypass Vulnerability (CVE-2026-2370)</title><link>https://feed.craftedsignal.io/briefs/2026-03-gitlab-jira-connect-auth-bypass/</link><pubDate>Mon, 30 Mar 2026 00:16:01 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-03-gitlab-jira-connect-auth-bypass/</guid><description>GitLab CE/EE versions 14.3 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1 are vulnerable to improper authorization checks in Jira Connect installations, allowing an authenticated user with minimal workspace permissions to obtain installation credentials and impersonate the GitLab application.</description><content:encoded>&lt;p>GitLab has addressed a critical vulnerability, CVE-2026-2370, affecting GitLab CE/EE installations with Jira Connect enabled.  This vulnerability impacts versions 14.3 up to 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1. The vulnerability stems from improper authorization checks, which enable an authenticated user with minimal workspace permissions within Jira to potentially obtain GitLab installation credentials. This, in turn, allows the attacker to impersonate the GitLab application…&lt;/p>
</content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>gitlab</category><category>jira</category><category>authentication</category><category>authorization</category><category>cve-2026-2370</category></item><item><title>GitLab Improper HTML Sanitization Vulnerability (CVE-2026-2995)</title><link>https://feed.craftedsignal.io/briefs/2026-03-gitlab-cve-2026-2995/</link><pubDate>Thu, 26 Mar 2026 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-03-gitlab-cve-2026-2995/</guid><description>CVE-2026-2995 is a vulnerability in GitLab EE versions 15.4 to 18.10.1 where an authenticated user can add email addresses to other user accounts due to improper HTML sanitization, potentially leading to account takeover or information disclosure.</description><content:encoded>&lt;p>GitLab has addressed CVE-2026-2995, a vulnerability affecting GitLab Enterprise Edition. The flaw resides in versions 15.4 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1. An authenticated attacker could exploit this vulnerability to inject arbitrary HTML content into user profiles, specifically targeting the addition of unauthorized email addresses. This is due to improper sanitization of HTML within GitLab&amp;rsquo;s user profile management features. Successful exploitation can lead to…&lt;/p>
</content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>gitlab</category><category>html-injection</category><category>cve-2026-2995</category></item><item><title>GitLab GraphQL Denial of Service Vulnerability (CVE-2026-3988)</title><link>https://feed.craftedsignal.io/briefs/2026-03-gitlab-graphql-dos/</link><pubDate>Thu, 26 Mar 2026 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-03-gitlab-graphql-dos/</guid><description>CVE-2026-3988 is a denial of service vulnerability in GitLab CE/EE allowing unauthenticated users to crash instances by sending malformed GraphQL requests, affecting versions 18.5 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1.</description><content:encoded>&lt;p>CVE-2026-3988 is a denial-of-service (DoS) vulnerability affecting GitLab CE/EE. The vulnerability resides in the processing of GraphQL requests and stems from improper input validation. An unauthenticated attacker can exploit this flaw by sending specially crafted GraphQL requests, causing the GitLab instance to become unresponsive, effectively denying service to legitimate users. The affected versions include all versions from 18.5 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1…&lt;/p>
</content:encoded><category domain="severity">medium</category><category domain="type">advisory</category><category>denial-of-service</category><category>graphql</category><category>gitlab</category><category>cve-2026-3988</category></item><item><title>GitLab GraphQL CSRF Vulnerability (CVE-2026-3857)</title><link>https://feed.craftedsignal.io/briefs/2026-03-gitlab-csrf/</link><pubDate>Thu, 26 Mar 2026 12:00:00 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-03-gitlab-csrf/</guid><description>CVE-2026-3857 describes a vulnerability in GitLab CE/EE versions 17.10 before 18.8.7, 18.9 before 18.9.3, and 18.10 before 18.10.1, where an unauthenticated user can execute arbitrary GraphQL mutations on behalf of authenticated users due to insufficient CSRF protection, potentially leading to data modification or privilege escalation.</description><content:encoded>&lt;p>GitLab has addressed a critical security flaw, identified as CVE-2026-3857, within its Community Edition (CE) and Enterprise Edition (EE). This vulnerability impacts GitLab instances running versions 17.10 up to, but not including, 18.8.7, versions 18.9 up to 18.9.3, and versions 18.10 up to 18.10.1.  The core issue lies in insufficient Cross-Site Request Forgery (CSRF) protection when handling GraphQL mutations. An unauthenticated attacker could exploit this by crafting malicious web pages…&lt;/p>
</content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>gitlab</category><category>csrf</category><category>cve-2026-3857</category><category>graphql</category></item></channel></rss>