Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

BIT-gitlab-2026-8330: Insertion of Sensitive Information into Log File in GitLab

0
Medium
Published: 06/29/2026 (06/29/2026, 06:02:37 UTC)
Source: GCVE Database
Product: gitlab

Description

GitLab CE/EE versions from 9.3 up to but not including 18.11.6, 19.0 up to 19.0.3, and 19.1 up to 19.1.1 contain a vulnerability where sensitive information could be written to application logs due to insufficient filtering in a CI/CD API endpoint. This issue has been remediated in the specified fixed versions. The vulnerability is rated medium severity and no known exploits are reported in the wild.

Affected software

Bitnamimore threats →ghsa
gitlab
pkg:bitnami/gitlab
Affected versions
>=9.3.0 <18.11.6>=19.0.0 <19.0.3>=19.1.0 <19.1.1

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 06/29/2026, 22:38:34 UTC

Technical Analysis

A vulnerability identified as CVE-2026-8330 affects GitLab Community and Enterprise Editions in versions >=9.3.0 <18.11.6, >=19.0.0 <19.0.3, and >=19.1.0 <19.1.1. Under certain conditions, insufficient filtering in a CI/CD API endpoint could cause sensitive information to be inserted into application log files. This could lead to unintended exposure of sensitive data through logs. The issue has been fixed in versions 18.11.6, 19.0.3, and 19.1.1 respectively.

Potential Impact

Sensitive information may be exposed in application logs due to insufficient filtering in a CI/CD API endpoint. This could potentially lead to unauthorized disclosure of sensitive data if log files are accessed by unauthorized parties. There are no known exploits in the wild at this time.

Mitigation Recommendations

Upgrade affected GitLab CE/EE instances to versions 18.11.6, 19.0.3, or 19.1.1 or later where this issue has been remediated. No additional mitigation steps are indicated by the vendor advisory.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Gcve Source
db.gcve.eu
Osv Id
BIT-gitlab-2026-8330
Osv Schema Version
1.6.2
Aliases
["CVE-2026-8330"]
Ecosystems
["Bitnami"]
Database Specific Severity
Medium
Cvss Version
null

Threat ID: 6a42ed7327e9c79719939242

Added to database: 06/29/2026, 22:10:59 UTC

Last enriched: 06/29/2026, 22:38:34 UTC

Last updated: 06/30/2026, 00:55:15 UTC

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses