GitLab · GitLab · published 2026-09-15

CVE-2026-82837Insertion of Sensitive Information Into Sent Data in GitLab

Routine No exploitation evidence; EPSS 0.2%.

CVE-2026-82837 is not known to be exploited in the wild. EPSS estimates a 0.2% chance of exploitation in the next 30 days, higher than 14% of all CVEs. This GitLab vulnerability: CVSS 5.3 (v3.1), attacks can be automated. Fixed upstream in GitLab 19.3.2, 19.2.6, 19.1.8. Routine: patch when convenient.

Share this

Remediation#

Fixed upstream in GitLab 19.3.2, 19.2.6, 19.1.8.

Patch events

  1. Patch todaySecurity release

    DevOpsGitLab

    GitLab security releases: 19.3.2, 19.2.6, 19.1.8

    Upgrade to 19.3.219.2.619.1.8

    Why: CVE-2026-85706: Known exploited (CISA KEV) and CISA requires forensic triage: patch and check for compromise.

Exploit intelligence#

SignalValueSource
Known exploitedNoCISA KEV
Ransomware use—CISA KEV
EPSS (30-day exploitation probability)0.2% (14th pct)FIRST EPSS v2026.06.15
CVSS base score5.3 (v3.1)
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
CNA / CISA ADP
SSVC exploitationnoneCISA Vulnrichment
SSVC automatableYesCISA Vulnrichment
SSVC technical impactpartialCISA Vulnrichment

Affected versions (from the CVE record)#

Description (from the CVE record)#

GitLab has remediated an issue in GitLab CE/EE affecting all versions from 10.1.0 before 19.1.8, 19.2 before 19.2.6, and 19.3 before 19.3.2 that certain conditions could have allowed an authenticated user to access sensitive credentials and tokens without transiting the expected proxy due to improper authorization checks on internal data emission endpoints.

Quoted from the CVE Program record.

Elsewhere#

Distro status: Debian · Ubuntu · Red Hat · Alpine

Something wrong on this page?
Anonymous. Reports are checked against the primary source.

Also on today's list

See today's list → · Coming up →