CVE-2026-7471

LOWNVD 3.53.5
EchelonGraph scoreMEDIUM confidence

Score 3.5 from GitHub Security Advisory (severity: LOW) published 2026-05-14. NVD baseline CVSS 3.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
3.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 3.5Exploit: 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 18.8 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user with control of a virtual registry upstream to make requests to internal hosts due to improper validation.

CVSS v3
3.5
EG Score
3.5(medium)
EPSS
6.7%
KEV
Not listed

Published

May 14, 2026

Last Modified

May 14, 2026

Vendor Advisories for CVE-2026-7471(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 8× in last 7d / 50× 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-06 16:27 UTCEPSS rescore
  2. 2026-07-06 16:27 UTCEPSS rescore
  3. 2026-07-05 02:31 UTCEPSS rescore
  4. 2026-07-05 02:30 UTCEPSS rescore
  5. 2026-07-04 06:31 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-01 15:07 UTCEPSS rescore
  8. 2026-06-30 23:22 UTCEPSS rescore
  9. 2026-06-29 21:58 UTCEG score recompute
  10. 2026-06-29 21:58 UTCGHSA enrichment
  11. 2026-06-29 14:06 UTCEPSS rescore
  12. 2026-06-28 14:07 UTCEPSS rescore
  13. 2026-06-28 04:56 UTCEPSS rescore
  14. 2026-06-27 03:08 UTCEPSS rescore
  15. 2026-06-25 19:24 UTCEG score recompute
  16. 2026-06-25 19:24 UTCGHSA enrichment
  17. 2026-06-25 13:50 UTCEPSS rescore
  18. 2026-06-24 14:05 UTCEPSS rescore
  19. 2026-06-23 21:33 UTCEPSS rescore
  20. 2026-06-22 14:25 UTCEPSS rescore
  21. 2026-06-22 14:25 UTCEPSS rescore
  22. 2026-06-21 14:56 UTCEPSS rescore
  23. 2026-06-21 14:56 UTCEPSS rescore
  24. 2026-06-21 01:59 UTCEPSS rescore
  25. 2026-06-21 01:59 UTCEPSS rescore
Show 49 more
  1. 2026-06-19 19:26 UTCEPSS rescore
  2. 2026-06-19 19:26 UTCEPSS rescore
  3. 2026-06-18 17:52 UTCEPSS rescore
  4. 2026-06-18 17:52 UTCEPSS rescore
  5. 2026-06-17 17:53 UTCEPSS rescore
  6. 2026-06-17 02:08 UTCEG score recompute
  7. 2026-06-17 02:08 UTCGHSA enrichment
  8. 2026-06-16 17:53 UTCEPSS rescore
  9. 2026-06-15 17:49 UTCEPSS rescore
  10. 2026-06-15 17:49 UTCEPSS rescore
  11. 2026-06-14 23:18 UTCEPSS rescore
  12. 2026-06-13 23:36 UTCEG score recompute
  13. 2026-06-13 23:36 UTCGHSA enrichment
  14. 2026-06-13 23:00 UTCEPSS rescore
  15. 2026-06-12 23:12 UTCEPSS rescore
  16. 2026-06-12 23:12 UTCEPSS rescore
  17. 2026-06-11 14:00 UTCEPSS rescore
  18. 2026-06-10 22:19 UTCEPSS rescore
  19. 2026-06-10 13:30 UTCEG score recompute
  20. 2026-06-10 13:29 UTCGHSA enrichment
  21. 2026-06-10 13:22 UTCEPSS rescore
  22. 2026-06-08 14:17 UTCEPSS rescore
  23. 2026-06-07 15:25 UTCEPSS rescore
  24. 2026-06-07 10:57 UTCEG score recompute
  25. 2026-06-07 10:57 UTCGHSA enrichment
  26. 2026-06-06 13:47 UTCEPSS rescore
  27. 2026-06-05 22:47 UTCEPSS rescore
  28. 2026-06-05 06:10 UTCEPSS rescore
  29. 2026-06-04 13:12 UTCEPSS rescore
  30. 2026-06-04 08:26 UTCEG score recompute
  31. 2026-06-04 08:26 UTCGHSA enrichment
  32. 2026-06-02 20:13 UTCEPSS rescore
  33. 2026-06-01 13:52 UTCEPSS rescore
  34. 2026-06-01 05:54 UTCEG score recompute
  35. 2026-06-01 05:54 UTCGHSA enrichment
  36. 2026-05-31 22:30 UTCEPSS rescore
  37. 2026-05-31 00:16 UTCEPSS rescore
  38. 2026-05-29 13:44 UTCEPSS rescore
  39. 2026-05-28 13:44 UTCEPSS rescore
  40. 2026-05-28 13:44 UTCEPSS rescore
  41. 2026-05-27 13:40 UTCEPSS rescore
  42. 2026-05-27 13:40 UTCEPSS rescore
  43. 2026-05-26 13:44 UTCEPSS rescore
  44. 2026-05-26 07:18 UTCEPSS rescore
  45. 2026-05-21 22:43 UTCEPSS rescore
  46. 2026-05-20 22:38 UTCEPSS rescore
  47. 2026-05-20 12:20 UTCEG score recompute
  48. 2026-05-20 12:20 UTCGHSA enrichment
  49. 2026-05-20 11:22 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-7471?
CVE-2026-7471 is a low vulnerability published on May 14, 2026. GitLab has remediated an issue in GitLab EE affecting all versions from 18.8 before 18.9.7, 18.10 before 18.10.6, and 18.11 before 18.11.3 that could have allowed an authenticated user with control of a virtual registry upstream to make requests to internal hosts due to improper validation.
When was CVE-2026-7471 disclosed?
CVE-2026-7471 was first published in the National Vulnerability Database on May 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7471 actively exploited?
CVE-2026-7471 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-7471?
CVE-2026-7471 has a CVSS v3 base score of 3.5 (NVD).
How do I remediate CVE-2026-7471?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7471, 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-7471

Explore →

Is Your Infrastructure Affected by CVE-2026-7471?

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