CVE-2026-16627

CRITICALNVD 9.09.0
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.0 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 78% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
Trending — 4 sources updated this week
9.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.0Exploit: None knownExposed: 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 CE/EE affecting all versions from 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to escalate privileges due to improper sanitization of HTML content rendered in a CI job modal.

CVSS v3
9.0
EG Score
9.0(medium)
EG Risk
41(Track)
EG Risk 41/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity90% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
22%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 19, 2026

Advisory Details (2)

Auto-updated Aug 12, 2026
No patch confirmed yet.
generic

GitLab Patch Release: 19.2.2, 19.1.4, 19.0.6 | GitLab Docs

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

Vendor Advisories for CVE-2026-16627(2)

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 32× in last 7d / 43× 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-08-20 05:05 UTCGHSA enrichment
  2. 2026-08-20 00:46 UTCGHSA enrichment
  3. 2026-08-19 20:25 UTCEG score recompute
  4. 2026-08-19 20:25 UTCGHSA enrichment
  5. 2026-08-19 17:03 UTCEPSS rescore
  6. 2026-08-19 16:04 UTCEG score recompute 1.30
  7. 2026-08-19 16:04 UTCGHSA enrichment
  8. 2026-08-19 16:04 UTCNVD updateCVSS v3 → 9 · severity → CRITICAL
  9. 2026-08-19 03:44 UTCGHSA enrichment
  10. 2026-08-18 15:10 UTCEG score recompute
  11. 2026-08-18 15:10 UTCGHSA enrichment
  12. 2026-08-18 13:48 UTCEPSS rescore
  13. 2026-08-18 11:00 UTCGHSA enrichment
  14. 2026-08-17 22:26 UTCEG score recompute
  15. 2026-08-17 22:26 UTCGHSA enrichment
  16. 2026-08-17 13:47 UTCEPSS rescore
  17. 2026-08-17 09:51 UTCGHSA enrichment
  18. 2026-08-16 21:18 UTCEG score recompute
  19. 2026-08-16 21:18 UTCGHSA enrichment
  20. 2026-08-16 14:56 UTCEPSS rescore
  21. 2026-08-16 08:44 UTCEG score recompute
  22. 2026-08-16 08:44 UTCGHSA enrichment
  23. 2026-08-16 02:14 UTCEPSS rescore
  24. 2026-08-15 20:10 UTCGHSA enrichment
  25. 2026-08-15 07:36 UTCEG score recompute
Show 18 more
  1. 2026-08-15 07:36 UTCGHSA enrichment
  2. 2026-08-15 01:30 UTCEPSS rescore
  3. 2026-08-14 19:01 UTCGHSA enrichment
  4. 2026-08-14 06:27 UTCEG score recompute
  5. 2026-08-14 06:27 UTCGHSA enrichment
  6. 2026-08-13 22:00 UTCEPSS rescore
  7. 2026-08-13 17:53 UTCGHSA enrichment
  8. 2026-08-13 05:19 UTCEG score recompute
  9. 2026-08-13 05:19 UTCGHSA enrichment
  10. 2026-08-13 04:21 UTCEG score recompute
  11. 2026-08-13 04:21 UTCGHSA enrichment
  12. 2026-08-12 19:19 UTCEG score recompute
  13. 2026-08-12 19:19 UTCGHSA enrichment
  14. 2026-08-12 18:56 UTCEG score recompute
  15. 2026-08-12 18:56 UTCGHSA enrichment
  16. 2026-08-12 18:18 UTCEG score recompute
  17. 2026-08-12 18:11 UTCEG score recompute
  18. 2026-08-12 18:11 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-16627?
CVE-2026-16627 is a critical vulnerability published on August 12, 2026. GitLab has remediated an issue in GitLab CE/EE affecting all versions from 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to escalate privileges due to improper sanitization of HTML content rendered in a CI job modal.
When was CVE-2026-16627 disclosed?
CVE-2026-16627 was first published in the National Vulnerability Database on August 12, 2026, with the most recent update on August 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-16627 actively exploited?
CVE-2026-16627 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 77.8% of all scored CVEs.
What is the CVSS score of CVE-2026-16627?
CVE-2026-16627 has a CVSS v3 base score of 9.0 (NVD).
How do I remediate CVE-2026-16627?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16627, 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-16627

Explore →

Is Your Infrastructure Affected by CVE-2026-16627?

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