Answer in brief
CVE-2024-0410 records a Unknown severity vulnerability in Improper Enforcement of Behavioral Workflow in GitLab. The current sources do not mark it as known exploited. The current feed maps gitlab/gitlab (generic), GitLab/GitLab (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps gitlab/gitlab (generic), GitLab/GitLab (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| gitlab/gitlabgeneric | >=15.1 <16.7.6 || >=16.8 <16.8.3 || >=16.9 <16.9.1 | 16.7.6, 16.8.3, 16.9.1 |
| GitLab/GitLabgeneric | >=15.1 <16.7.6 || >=16.8 <16.8.3 || >=16.9 <16.9.1 | 16.7.6, 16.8.3, 16.9.1 |
Published upstream
Feb 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 14, 2026
An authorization bypass vulnerability was discovered in GitLab affecting versions 15.1 prior to 16.7.6, 16.8 prior to 16.8.3, and 16.9 prior to 16.9.1. A developer could bypass CODEOWNERS approvals by creating a merge conflict.
Quoted source text, attributed separately from HOL analysis.
Answer in brief
CVE-2024-0410 records a Unknown severity vulnerability in Improper Enforcement of Behavioral Workflow in GitLab. The current sources do not mark it as known exploited. The current feed maps gitlab/gitlab (generic), GitLab/GitLab (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps gitlab/gitlab (generic), GitLab/GitLab (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| gitlab/gitlabgeneric | >=15.1 <16.7.6 || >=16.8 <16.8.3 || >=16.9 <16.9.1 | 16.7.6, 16.8.3, 16.9.1 |
| GitLab/GitLabgeneric | >=15.1 <16.7.6 || >=16.8 <16.8.3 || >=16.9 <16.9.1 | 16.7.6, 16.8.3, 16.9.1 |
Published upstream
Feb 21, 2024
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Aug 14, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 14, 2026
An authorization bypass vulnerability was discovered in GitLab affecting versions 15.1 prior to 16.7.6, 16.8 prior to 16.8.3, and 16.9 prior to 16.9.1. A developer could bypass CODEOWNERS approvals by creating a merge conflict.
Quoted source text, attributed separately from HOL analysis.