Back to the CVE list
CVE-2026-101168

Insertion of Sensitive Information into Log File in GitLab

CVSS score

6.2

EPSS probability

%0.2

Risk score

0.0

Published

20 h ago

OverviewPublic Exploits (0)NewsroomVulnerability Timeline
Patch status has not yet been verified

Resmî kaynaklarda yeterli kanıt bulunamadı. Bu sonuç “yama yok” anlamına gelmez.

Impact on My Inventory

Only the personal products you have added to your account are assessed; an organisation's inventory does not appear here.

Checking session…

Vulnerability description

CVE AI research

The stored explanation is shown at once; refreshing evaluates the sources again.

DayBreach AI Explanation

Verified against sources

Sensitive Information Insertion into Log File in GitLab Pages

Sources read

2

Source agreement

Tam uyum

Evidence confidence

%63

Short explanation

An issue in GitLab CE and EE allows an authenticated user with access to GitLab Pages log data to obtain access tokens and other secrets under certain conditions, due to the insertion of sensitive request data into log files and error tracking events.

Why does it matter?

This vulnerability allows authorized users to acquire sensitive access tokens and secrets, leading to confidentiality breaches.

What should be done?

  • Follow vendor advisories
  • Review log file access permissions
Chain of evidence and sources2 verified claims

GitLab CE/EE sürümlerinde hassas istek verileri günlük dosyalarına ve hata izleme olaylarına eklenmektedir.

S0 · daybreach-canonicalS1 · cvelistS2 · nvd

Bu durum, belirli koşullar altında erişim belirteçlerinin ve diğer sırların elde edilmesine yol açabilir.

S0 · daybreach-canonicalS1 · cvelistS2 · nvd
Show the technical text from the sources

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 12.0 before 19.2.8, 19.3 before 19.3.5, and 19.4 before 19.4.2 that, under certain conditions, could have allowed an authenticated user with access to GitLab Pages log data to obtain access tokens and other secrets, due to insertion of sensitive request data into log files and error tracking events.

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

CWE: CWE-532

Explanation produced with the local gemini-flash-lite-latest model. Numerical metrics and the KEV, patch and exploit statuses are not determined by AI.

IMPACT: Affected Products and Software

Affected Products

The following products are affected by CVE-2026-101168 vulnerability. Where our threat engine knows the exact affected versions, they are listed below.

IDVENDORPRODUCTACTION
1gitlabgitlab View
Total affected vendors: 1|Products: 1

RED HAT CSAF/VEX: Product Impact Check

Red Hat has not yet published a CSAF/VEX impact record for this CVE. This does not mean “not affected”.

SCORING: CVSS from Multiple Sources

CVSS Scores

The Common Vulnerability Scoring System is a standardised framework for assessing the severity of vulnerabilities in software and systems. We collect and display CVSS scores from several sources for each CVE.

SCOREVERSIONSEVERITYVECTORSOURCE
6.2CVSS V31MEDIUMCVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:NNVD
6.2CVSS V3_1MEDIUMCVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:NCVE CNA

Patch and Remediation Guide

Solution & Remediation Advisory

Patch status unknown

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Confirm the affected product and version against the source evidence above.
Restrict access to internet-facing services and apply network segmentation.
Until a patch is confirmed, follow the vendor advisory; do not read an unknown status as “no patch”.
Monitor server logs and network endpoints for signs of anomalous execution.

Public exploit and active exploitation status

Verified exploit intelligence

No verified public PoC, exploit repository or Metasploit module has been found for this CVE yet.

Weakness Classification and Attack Patterns (CWE & CAPEC)

CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorises the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-101168 is associated with the following CWEs:

CWE-532: Common Weakness Enumeration Entry CWE-532

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-101168 weaknesses.

CAPEC-66: SQL InjectionCAPEC-126: Path TraversalCAPEC-28: OS Command Injection

Attack Vector and Accessibility

ExposureBitişik ağ
PermissionsHigh
UserGerekmiyor

Official Sources and Advisories

https://gitlab.com/gitlab-org/gitlab-pages/-/work_items/1187vendor-advisoryhttps://docs.gitlab.com/releases/patches/patch-release-gitlab-19-4-2-released/vendor-advisory

CVSS Vector Radar Chart

6.2 / 10
Attack VectorAdjacentComplexityLowPrivilegesHighUser Interact.NoneConfidentialityLowIntegrityNoneAvailabilityNone

Vulnerability Scoring Details

CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N
Attack VectorAdjacent network
Attack ComplexityLow
Privileges RequiredHigh privileges
User InteractionNone required
Confidentiality (Gizlilik)Low
Integrity (Bütünlük)None
Availability (Erişilebilirlik)None

Yama durumu bilinmiyor

İncelenen resmî kaynaklarda yama durumu doğrulanamadı. Bu sonuç “yama yok” anlamına gelmez.

Follow the vendor

G
gitlab logo
gitlab

Weakness Type (CWE & CAPEC)

CWE-532

Similar Vulnerabilities

Get this vulnerability through the API

Affected products, version ranges, exploitation status and patch information in a single request, with a free key.

Get a free keyDocumentation
curl -H "x-api-key: $DAYBREACH_API_KEY" \
  "https://api.daybreach.dev/api/v1/intel/cves/CVE-2026-101168"