CVE-2026-7492

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 83% 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 — 3 sources updated this week
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: 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 9.1 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 unauthenticated user to determine the existence of a private project due to improper authorization controls on cross-project reference pages.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
24(Track)
EG Risk 24/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
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
17%
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-7492(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 15× in last 7d / 39× 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-27 11:59 UTCEG score recompute
  2. 2026-07-27 11:59 UTCGHSA enrichment
  3. 2026-07-26 14:54 UTCEPSS rescore
  4. 2026-07-26 12:25 UTCEG score recompute
  5. 2026-07-26 12:24 UTCGHSA enrichment
  6. 2026-07-25 14:18 UTCEPSS rescore
  7. 2026-07-24 14:18 UTCEPSS rescore
  8. 2026-07-23 14:18 UTCEPSS rescore
  9. 2026-07-23 14:18 UTCEPSS rescore
  10. 2026-07-23 03:22 UTCEG score recompute▲ 1.00
  11. 2026-07-22 14:08 UTCEPSS rescore
  12. 2026-07-22 14:08 UTCEPSS rescore
  13. 2026-07-21 15:25 UTCEPSS rescore
  14. 2026-07-21 15:25 UTCEPSS rescore
  15. 2026-07-20 17:08 UTCEPSS rescore
  16. 2026-07-19 14:31 UTCEPSS rescore
  17. 2026-07-19 02:29 UTCEPSS rescore
  18. 2026-07-18 10:04 UTCEPSS rescore
  19. 2026-07-16 17:44 UTCGHSA enrichment
  20. 2026-07-16 17:03 UTCEPSS rescore
  21. 2026-07-15 18:10 UTCGHSA enrichment
  22. 2026-07-15 16:57 UTCEPSS rescore
  23. 2026-07-15 02:00 UTCEPSS rescore
  24. 2026-07-14 18:36 UTCGHSA enrichment
  25. 2026-07-13 22:31 UTCEPSS rescore
Show 14 more
  1. 2026-07-13 19:02 UTCGHSA enrichment
  2. 2026-07-13 06:13 UTCEPSS rescore
  3. 2026-07-12 19:29 UTCGHSA enrichment
  4. 2026-07-12 05:46 UTCEPSS rescore
  5. 2026-07-11 19:55 UTCGHSA enrichment
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-11 08:27 UTCEPSS rescore
  8. 2026-07-10 20:21 UTCGHSA enrichment
  9. 2026-07-09 21:46 UTCNVD updateCVSS v3 → 5.3
  10. 2026-07-09 20:48 UTCGHSA enrichment
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-09 19:10 UTCEPSS rescore
  13. 2026-07-08 21:13 UTCEG score recompute
  14. 2026-07-08 21:10 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-7492?
CVE-2026-7492 is a medium vulnerability published on July 8, 2026. GitLab has remediated an issue in GitLab CE/EE affecting all versions from 9.1 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 unauthenticated user to determine the existence of a private project due to improper authorization controls…
When was CVE-2026-7492 disclosed?
CVE-2026-7492 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-7492 actively exploited?
CVE-2026-7492 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 83.1% of all scored CVEs.
What is the CVSS score of CVE-2026-7492?
CVE-2026-7492 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-7492?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7492, 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-7492

Explore →

Is Your Infrastructure Affected by CVE-2026-7492?

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

Start Free Scan →Browse All CVEs