CVE-2026-4879

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this weekElevated
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: Elevated riskExposed: 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 16.0 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to view external status check configuration restricted to higher-privileged roles due to missing authorization on a merge request API endpoint.

CVSS v3
4.3
EG Score
4.3(high)
EG Risk
35(Track)
EG Risk 35/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
Severity43% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

August 12, 2026

Last Modified

August 19, 2026

Advisory Details (1)

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-4879(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 23× in last 7d / 26× 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-19 17:04 UTCEPSS rescore
  2. 2026-08-19 16:46 UTCGHSA enrichment
  3. 2026-08-19 15:34 UTCGHSA enrichment
  4. 2026-08-18 15:09 UTCEG score recompute
  5. 2026-08-18 15:08 UTCGHSA enrichment
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-17 15:17 UTCEG score recompute
  8. 2026-08-17 15:17 UTCGHSA enrichment
  9. 2026-08-17 13:47 UTCEPSS rescore
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 14:52 UTCEG score recompute
  12. 2026-08-16 14:52 UTCGHSA enrichment
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-15 14:27 UTCEG score recompute
  15. 2026-08-15 14:27 UTCGHSA enrichment
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 14:01 UTCEG score recompute
  18. 2026-08-14 14:01 UTCGHSA enrichment
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-13 13:36 UTCEG score recompute
  21. 2026-08-13 13:36 UTCGHSA enrichment
  22. 2026-08-13 12:47 UTCEG score recompute
  23. 2026-08-13 12:47 UTCGHSA enrichment
  24. 2026-08-12 20:20 UTCEG score recompute
  25. 2026-08-12 19:21 UTCEG score recompute
Show 1 more
  1. 2026-08-12 19:20 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-4879?
CVE-2026-4879 is a medium vulnerability published on August 12, 2026. GitLab has remediated an issue in GitLab EE affecting all versions from 16.0 before 19.0.6, 19.1 before 19.1.4, and 19.2 before 19.2.2 that under certain conditions could have allowed an authenticated user with developer-role permissions to view external status check configuration restricted to…
When was CVE-2026-4879 disclosed?
CVE-2026-4879 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-4879 actively exploited?
CVE-2026-4879 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 84.3% of all scored CVEs.
What is the CVSS score of CVE-2026-4879?
CVE-2026-4879 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-4879?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-4879, 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-4879

Explore →

Is Your Infrastructure Affected by CVE-2026-4879?

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

Start Free Scan →Browse All CVEs