CVE-2025-2867· NVD / CVE Program· CNA GitLab

Improper Control of Generation of Code ('Code Injection') in GitLab

Noroxi assessment

Priority: Monitor (action score 26/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: GitLab GitLab 17.10.1, 17.8.6, 17.9.3.
Severity is disputed: the assigning authority (CNA) scores it 4.4, NVD 6.5.

Low priority for now. Upgrade to GitLab GitLab 17.10.1, 17.8.6, 17.9.3 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

An issue has been discovered in the GitLab Duo with Amazon Q affecting all versions from 17.8 before 17.8.6, 17.9 before 17.9.3, and 17.10 before 17.10.1. A specifically crafted issue could manipulate AI-assisted development features to potentially expose sensitive project data to unauthorized users.

MediumCVSS 6.5 · v3.1—No exploit Fix available

Published: Mar 27, 2025
Updated: Jun 17, 2026
EPSS: 0.2% · 11th percentile
CWE: CWE-94

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 26 / 40 · 6.5 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.2%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 6.5
CNA · GitLab: 4.4; 2.1 point gap

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

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
gitlab	gitlab	cpe:2.3:a:gitlab:gitlab

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

gitlab gitlab17.8.0 and later · before 17.8.6
gitlab gitlab17.9.0 and later · before 17.9.3
gitlab gitlab17.10.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitLab). Independent of NVD's CPE analysis and usually ahead of it.

GitLab GitLab
- 17.8 and later · before 17.8.6affected · semver
- 17.9 and later · before 17.9.3affected · semver
- 17.10 and later · before 17.10.1affected · semver

Same product

gitlab: all records

Other highest-scoring records for the same primary product.

CVE-2021-22205An issue has been discovered in GitLab CE/EE affecting all versions starting from 11.9.KEV
100Now
CVE-2026-85706Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in GitLabKEV
98Now
CVE-2023-7028Weak Password Recovery Mechanism for Forgotten Password in GitLabKEV
97Now

Published before and after this one in the same product

← EarlierCVE-2025-2242Mar 27, 2025 · Incorrect Authorization in GitLab
35Monitor
← EarlierCVE-2025-2255Mar 27, 2025 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in GitLab
21Monitor
Later →CVE-2024-10307Mar 28, 2025 · Allocation of Resources Without Limits or Throttling in GitLab
22Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
GitLab GitLab	17.10.1	Vendor (CNA)
GitLab GitLab	17.8.6	Vendor (CNA)
GitLab GitLab	17.9.3	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

This vulnerability has been discovered internally by GitLab team member Félix Veillette-Potvinfinder

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-19478508 days apartImproper Control of Generation of Code ('Code Injection') in GitLab
54Plan
CVE-2023-5226482 days apartImproper Control of Generation of Code ('Code Injection') in GitLab
30Monitor
CVE-2024-3958231 days apartImproper Control of Generation of Code ('Code Injection') in GitLab
26Monitor
CVE-2023-6051468 days apartImproper Control of Generation of Code ('Code Injection') in GitLab
26Monitor
CVE-2026-1516377 days apartImproper Control of Generation of Code ('Code Injection') in GitLab
22Monitor
CVE-2023-5512468 days apartImproper Control of Generation of Code ('Code Injection') in GitLab
22Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2025-054943 days apartAuthentication Bypass Using an Alternate Path or Channel in GitLab
27Monitor
CVE-2025-175491 days apartMissing Authentication for Critical Function in GitLab
21Monitor
CVE-2025-060556 days apartWeak Authentication in GitLab
17Monitor

Bug bounty scope

GitLabHackerOne · paid

The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: none
Availability: none

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: None
Availability impact: None

Weakness class (CWE)

CWE-94 · Improper Control of Generation of Code ('Code Injection')

CVSS vector

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

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

Change log

Fix✗ → ✓Sep 28, 2026, 10:10 PM UTC

For records you follow, these changes also arrive as notifications. →

References

gitlab.com/gitlab-org/gitlab/-/issues/512509

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records