What is the CVSS score of CVE-2026-9694?

CVE-2026-9694 has a CVSS 3.1 base score of 4.3 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N. EPSS exploitation probability: 0.0%.

Is there a public PoC exploit available for CVE-2026-9694?

Yes, a public proof-of-concept exploit is available for CVE-2026-9694. Prioritise patching immediately. EPSS: 0.0%.

Is there a patch available for CVE-2026-9694?

Yes, a patch is available for CVE-2026-9694. Update the affected software to the latest version immediately.

GitLab CE/EE CVE-2026-9694

EUVD-2026-36224 MEDIUM

Improper Neutralization of Substitution Characters (CWE-153)

2026-06-11 GitLab

GHSA-5cr4-qwvx-32j2

Gitlab Code Injection

4.3

CVSS 3.1 · NVD

Severity by source

Vendor (GitLab) PRIMARY

LOW

qualitative

NVD

4.3 MEDIUM

AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

vuln.today AI

3.1 LOW

AV:N because attack is delivered via email; AC:H per 'certain conditions'; PR:N per description's explicit 'unauthenticated user' language, overriding the conflicting official PR:L; UI:R because victim must view the injected issue content; I:L for content injection only.

3.1 AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:N

4.0 AV:N/AC:H/AT:P/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (GitLab).

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Lifecycle Timeline

Severity Changed

Jun 11, 2026 - 17:37 NVD

LOW MEDIUM

CVSS changed

Jun 11, 2026 - 17:37 NVD

2.6 (LOW) 4.3 (MEDIUM)

Patch available

Jun 11, 2026 - 13:01 EUVD

Analysis Generated

Jun 11, 2026 - 11:51 vuln.today

DescriptionNVD

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 15.9 before 18.10.8, 18.11 before 18.11.5, and 19.0 before 19.0.2 that under certain conditions, could have allowed an unauthenticated user to impersonate the GitLab Support Bot and inject arbitrary content via a specially crafted Service Desk email reply due to improper neutralization in email template processing.

AnalysisAI

Content injection via Service Desk email template processing in GitLab CE/EE allows an unauthenticated attacker to impersonate the GitLab Support Bot and inject arbitrary content into issue threads. The vulnerability affects all GitLab instances running versions from 15.9 through 19.0.1 with the Service Desk feature active, and stems from improper neutralization of substitution characters (CWE-153) in email template rendering. A publicly available exploit exists on HackerOne, though no active exploitation has been confirmed by CISA KEV; the official CVSS score of 2.6 reflects the high attack complexity and limited integrity-only impact.

Technical ContextAI

GitLab's Service Desk feature accepts inbound emails and processes them as issue comments using an internal email template engine. The vulnerability is rooted in CWE-153 (Improper Neutralization of Substitution Characters), meaning the template processor fails to sanitize or escape substitution tokens within attacker-controlled email reply content before rendering. This allows an adversary to craft an email body containing template substitution sequences that, when processed by GitLab's mailer/template layer, are evaluated rather than treated as literal text, effectively letting the attacker forge content attributed to the privileged GitLab Support Bot identity. The affected product is identified via CPE cpe:2.3:a:gitlab:gitlab:*:*:*:*:*:*:*:* and applies to both Community Edition and Enterprise Edition deployments across a wide version range (15.9 to 19.0.1). The HackerOne report and GitLab work item (ID 601330) corroborate the template-injection root cause.

RemediationAI

Upgrade to a patched release immediately: GitLab 18.10.8, 18.11.5, or 19.0.2, as documented in the vendor patch advisory at https://about.gitlab.com/releases/2026/06/10/patch-release-gitlab-19-0-2-released/. These are the exact fixed versions confirmed by the GitLab release announcement dated 2026-06-10. If immediate upgrade is not feasible, the primary compensating control is to disable the Service Desk feature on the affected GitLab instance, which removes the inbound email processing pathway that this vulnerability targets; note that disabling Service Desk will prevent all inbound issue creation via email until the upgrade is applied. Restricting who can send email to Service Desk addresses (e.g., allowlisting known sender domains via email routing controls) provides an additional layer of defense but should not substitute for patching, as spoofed sender addresses may still satisfy naive filters.