CVE-2023-3102

MEDIUMNVD 5.35.3—

5.3

A sensitive information leak issue has been discovered in GitLab EE affecting all versions starting from 16.0 before 16.0.6, all versions starting from 16.1 before 16.1.1, which allows access to titles of private issue and MR.

CVSS v3: 5.3
EG Score: 5.3(medium)
EPSS: 60.5%
KEV: Not listed

Published

July 21, 2023

Last Modified

November 21, 2024

References (4)

cve@gitlabhttps://gitlab.com/gitlab-org/gitlab/-/issues/414269
cve@gitlabhttps://hackerone.com/reports/2012073
af854a3a-2127-422b-91ae-364da2661108https://gitlab.com/gitlab-org/gitlab/-/issues/414269
af854a3a-2127-422b-91ae-364da2661108https://hackerone.com/reports/2012073

Vendor Advisories for CVE-2023-3102(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

patch-release-gitlab-16-1-1-released
GitLab Security
GitLab Security Release: 16.1.1, 16.0.6, and 15.11.10

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:12 UTCepss_batch
2026-06-02 20:12 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-29 13:43 UTCepss_batch
2026-05-28 13:44 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 13:43 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-26 07:18 UTCepss_batch
2026-05-24 20:49 UTCEG score recompute

Frequently asked(5)

What is CVE-2023-3102?

CVE-2023-3102 is a medium vulnerability published on July 21, 2023. A sensitive information leak issue has been discovered in GitLab EE affecting all versions starting from 16.0 before 16.0.6, all versions starting from 16.1 before 16.1.1, which allows access to titles of private issue and MR.

When was CVE-2023-3102 disclosed?

CVE-2023-3102 was first published in the National Vulnerability Database on July 21, 2023, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2023-3102 actively exploited?

CVE-2023-3102 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 60.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2023-3102?

CVE-2023-3102 has a CVSS v3 base score of 5.3 (NVD).

How do I remediate CVE-2023-3102?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-3102, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-3102

Explore →

Is Your Infrastructure Affected by CVE-2023-3102?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2023-3102

📅 Published

🔄 Last Modified

🔗 References (4)

📣 Vendor Advisories for CVE-2023-3102(1)

Weakness Classification(2)

Data Freshness Timeline

❓ Frequently asked(5)