Use of Less Trusted Source in GitLab

Answer in brief

CVE-2026-92530 records a Medium severity (CVSS 4.3) vulnerability in Use of Less Trusted Source in GitLab. The current sources do not mark it as known exploited. The current feed maps 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.

Published Sep 23, 2026Updated Sep 23, 2026Source checked Sep 24, 2026First seen by HOL Sep 23, 2026Material review Sep 23, 2026

Upstream Advisory

Key facts

Risk: Medium · CVSS 4.3
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

CVSS is 4.3. 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.

Affected scope and exposure questions

The current feed maps GitLab/GitLab (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
GitLab/GitLabgeneric	>=19.1 <19.2.7 \|\| >=19.3 <19.3.3 \|\| >=19.4 <19.4.1	19.2.7, 19.3.3, 19.4.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for GitLab/GitLab.
Review the reported fix. Update GitLab/GitLab to 19.2.7 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 23, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 23, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 23, 2026

Sources and claim methodology

Upstream source description

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.1 before 19.2.7, 19.3 before 19.3.3, and 19.4 before 19.4.1 that under certain conditions could have allowed an authenticated user to spoof merge request authorship and attribute content to arbitrary existing users on the target instance due to improper reliance on ephemeral cache state during Direct Transfer imports.

Quoted source text, attributed separately from HOL analysis.