CVE-2026-11827

MEDIUMPre-NVD 4.94.9
EchelonGraph scoreHIGH confidence

Score 4.9 from GitHub Security Advisory published 2026-07-08. a secondary CVSS source baseline 4.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.9Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

GitLab has remediated an issue in GitLab EE affecting all versions from 9.5 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user with maintainer-role permissions to obtain another user's stored credentials due to improper authorization controls.

CVSS v3
4.9
EG Score
4.9(high)
EPSS
16.9%
KEV
Not listed

Published

July 8, 2026

Last Modified

July 9, 2026

Advisory Details (1)

Auto-updated Jul 8, 2026
No patch confirmed yet.
generic

GitLab Patch Release: 19.1.2, 19.0.4, 18.11.7 | GitLab Docs

https://docs.gitlab.com/releases/patches/patch-release-gitlab-19-1-2-released/

Vendor Advisories for CVE-2026-11827(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 13× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-12 20:30 UTCEG score recompute
  2. 2026-07-12 20:30 UTCGHSA enrichment
  3. 2026-07-12 05:46 UTCEPSS rescore
  4. 2026-07-11 20:41 UTCEG score recompute
  5. 2026-07-11 20:41 UTCGHSA enrichment
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-10 20:52 UTCEG score recompute
  8. 2026-07-10 20:52 UTCGHSA enrichment
  9. 2026-07-09 21:03 UTCEG score recompute
  10. 2026-07-09 21:03 UTCGHSA enrichment
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-08 21:13 UTCEG score recompute
  13. 2026-07-08 21:10 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-11827?
CVE-2026-11827 is a medium vulnerability published on July 8, 2026. GitLab has remediated an issue in GitLab EE affecting all versions from 9.5 before 18.11.7, 19.0 before 19.0.4, and 19.1 before 19.1.2 that under certain conditions could have allowed an authenticated user with maintainer-role permissions to obtain another user's stored credentials due to improper…
When was CVE-2026-11827 disclosed?
CVE-2026-11827 was first published in the National Vulnerability Database on July 8, 2026, with the most recent update on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11827 actively exploited?
CVE-2026-11827 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 16.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-11827?
CVE-2026-11827 has a CVSS v3 base score of 4.9 (NVD).
How do I remediate CVE-2026-11827?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11827, 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

Explore the affected products and dependency analysis for CVE-2026-11827

Explore →

Is Your Infrastructure Affected by CVE-2026-11827?

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