CVE-2026-36848

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

Score 7.5 from GitHub Security Advisory (severity: HIGH) published 2026-06-29. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 7.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this weekElevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

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

Gigamon GVOS v5.16.1 and below is vulnerable to Directory Traversal in the GVOS H-VUE subsystem.

CVSS v3
7.5
EG Score
7.5(high)
EPSS
48.5%
KEV
Not listed

Published

June 29, 2026

Last Modified

June 30, 2026

Advisory Details (2)

Auto-updated Jun 29, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

GitHub - calligraf0/CVE-2026-36848: Gigamon Unauth RCE (CVE-2026-36848) · GitHub

https://github.com/calligraf0/CVE-2026-36848
generic

Gigamon End of Sale (EOS) and End Of Life (EOL) Policy | Gigamon

https://www.gigamon.com/support/policies/eol-policy.html

Vendor Advisories for CVE-2026-36848(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 26× in last 7d / 30× 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-07 00:01 UTCEG score recompute
  2. 2026-07-07 00:01 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 11:55 UTCEG score recompute
  6. 2026-07-06 11:55 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 23:45 UTCEG score recompute
  10. 2026-07-05 23:45 UTCGHSA enrichment
  11. 2026-07-05 11:39 UTCEG score recompute
  12. 2026-07-05 11:39 UTCGHSA enrichment
  13. 2026-07-05 02:30 UTCEPSS rescore
  14. 2026-07-04 23:27 UTCEG score recompute
  15. 2026-07-04 23:27 UTCGHSA enrichment
  16. 2026-07-04 11:21 UTCEG score recompute
  17. 2026-07-04 11:21 UTCGHSA enrichment
  18. 2026-07-04 06:31 UTCEPSS rescore
  19. 2026-07-03 23:15 UTCEG score recompute
  20. 2026-07-03 23:15 UTCGHSA enrichment
  21. 2026-07-03 11:06 UTCEG score recompute
  22. 2026-07-03 11:06 UTCGHSA enrichment
  23. 2026-07-02 22:59 UTCEG score recompute▲ 7.50
  24. 2026-07-02 22:58 UTCGHSA enrichment
  25. 2026-07-01 15:06 UTCEPSS rescore
Show 5 more
  1. 2026-06-30 23:22 UTCEPSS rescore
  2. 2026-06-29 20:17 UTCMITRE cvelistV5CVSS v3 → 7.5 · severity → HIGH
  3. 2026-06-29 19:26 UTCNVD update
  4. 2026-06-29 18:05 UTCEG score recompute
  5. 2026-06-29 18:02 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-36848?
CVE-2026-36848 is a high vulnerability published on June 29, 2026. Gigamon GVOS v5.16.1 and below is vulnerable to Directory Traversal in the GVOS H-VUE subsystem.
When was CVE-2026-36848 disclosed?
CVE-2026-36848 was first published in the National Vulnerability Database on June 29, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-36848 actively exploited?
CVE-2026-36848 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 48.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-36848?
CVE-2026-36848 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-36848?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-36848, 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-36848

Explore →

Is Your Infrastructure Affected by CVE-2026-36848?

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

Start Free Scan →Browse All CVEs