CVE-2023-4378Public exploitNetwork attack vector

Sentry token disclosure via URL prefix comparison

Published Sep 1, 2023 · Updated Apr 24, 2026

Sensitive-data exposure in GitLab allows remote authenticated users with Maintainer access to obtain a configured Sentry token. ErrorTracking::ListProjectsService compares the saved Sentry API URL with a user-supplied host by prefix, then reuses the saved token in a connection request to the shorter attacker-controlled domain. The flaw requires a configured Sentry integration and project Maintainer access; it exposes the token's read and write access to Sentry without affecting GitLab availability.

CVSS severity5.5
Medium
EPSS probability0.51%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkNot available
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Sensitive-data exposure in GitLab allows remote authenticated users with Maintainer access to obtain a configured Sentry token. ErrorTracking::ListProjectsService compares the saved Sentry API URL with a user-supplied host by prefix, then reuses the saved token in a connection request to the shorter attacker-controlled domain. The flaw requires a configured Sentry integration and project Maintainer access; it exposes the token's read and write access to Sentry without affecting GitLab availability.

The record

CVE
CVE-2023-4378
Published
Sep 1, 2023
Updated
Apr 24, 2026
Vendor
GitLab
Product
GitLab
Classifications
CWE-201
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 1, 2023CVE publishedPublication date reported by the CVE source.
  2. Apr 24, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=11.8 <16.1.5
  2. Affected versionversion=16.2 <16.2.5
  3. Affected versionversion=16.3 <16.3.1

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

GitLab · GitLabversion=11.8 <16.1.5; version=16.2 <16.2.5; version=16.3 <16.3.1

Published CVSS scores

5.5GitLab Inc.CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N
4.3NIST NVDCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitPublished

Weakness, pattern, technique

CWE-201Insertion of Sensitive Information Into Sent Data

Public exploit references

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo