CVE-2026-32610

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 73% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

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

Glances is an open-source system cross-platform monitoring tool. Prior to version 4.5.2, the Glances REST API web server ships with a default CORS configuration that sets allow_origins=["*"] combined with allow_credentials=True. When both of these options are enabled together, Starlette's CORSMiddleware reflects the requesting Origin header value in the Access-Control-Allow-Origin response header instead of returning the literal * wildcard. This effectively grants any website the ability to make credentialed cross-origin API requests to the Glances server, enabling cross-site data theft of system monitoring information, configuration secrets, and command line arguments from any user who has an active browser session with a Glances instance. Version 4.5.2 fixes the issue.

CVSS v3
8.1
EG Score
8.1(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
Severity81% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
KEV
Not listed

Published

March 18, 2026

Last Modified

June 17, 2026

Advisory Details (3)

Auto-updated Aug 2, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_release, github.
github Patch Available🟡 PoC Available

Default CORS Configuration Allows Cross-Origin Credential Theft · Advisory · nicolargo/glances · GitHub

https://github.com/nicolargo/glances/security/advisories/GHSA-9jfm-9rc6-2hfq
github_release Patch Available

Glances 4.5.2

Patch available: nicolargo/glances v4.5.2

https://github.com/nicolargo/glances/releases/tag/v4.5.2
github_commit Patch Available

commit 4465169b71d9 (nicolargo/glances)

Patch available: nicolargo/glances v4.5.2 (contains commit 4465169b71d9)

https://github.com/nicolargo/glances/commit/4465169b71d93991f1e49740fe02428291099832

Affected Packages

(4 across 4 ecosystems)
Debian:12(1)
PackageVulnerable rangeFixed inDependents
glances3.3.1.1+dfsg-1 ... 4.5.6+dfsg-1 (14 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
glances4.3.1+dfsg-1 ... 4.5.6+dfsg-1 (8 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
glances4.3.1+dfsg-1, 4.3.3+dfsg-1, 4.5.1+dfsg-14.5.2+dfsg-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
glances1.3.1 ... 4.5.1 (131 versions)4.5.2—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 28× 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-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-10 09:34 UTCEPSS rescore
  9. 2026-09-08 22:00 UTCEPSS rescore
  10. 2026-09-06 13:47 UTCEPSS rescore
  11. 2026-09-06 13:47 UTCEPSS rescore
  12. 2026-09-04 05:06 UTCEPSS rescore
  13. 2026-09-02 18:08 UTCOSV refresh
  14. 2026-09-02 14:11 UTCEPSS rescore
  15. 2026-09-01 13:53 UTCEPSS rescore
  16. 2026-09-01 04:39 UTCEPSS rescore
  17. 2026-09-01 04:39 UTCEPSS rescore
  18. 2026-08-30 19:17 UTCEPSS rescore
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 14:25 UTCEPSS rescore
  22. 2026-08-26 14:46 UTCEPSS rescore
  23. 2026-08-25 13:49 UTCEPSS rescore
  24. 2026-08-24 14:17 UTCEPSS rescore
  25. 2026-08-23 00:19 UTCEPSS rescore
Show 37 more
  1. 2026-08-21 23:49 UTCEPSS rescore
  2. 2026-08-20 22:55 UTCEPSS rescore
  3. 2026-08-20 22:55 UTCEPSS rescore
  4. 2026-08-19 17:03 UTCEPSS rescore
  5. 2026-08-18 13:48 UTCEPSS rescore
  6. 2026-08-17 13:47 UTCEPSS rescore
  7. 2026-08-16 14:56 UTCEPSS rescore
  8. 2026-08-16 11:16 UTCEG score recompute
  9. 2026-08-16 02:14 UTCEPSS rescore
  10. 2026-08-15 01:30 UTCEPSS rescore
  11. 2026-08-14 07:24 UTCEG score recompute
  12. 2026-08-13 22:00 UTCEPSS rescore
  13. 2026-08-12 22:11 UTCEG score recompute
  14. 2026-08-12 13:50 UTCEPSS rescore
  15. 2026-08-11 21:31 UTCEG score recompute
  16. 2026-08-11 04:36 UTCEG score recompute
  17. 2026-08-11 00:00 UTCEPSS rescore
  18. 2026-08-09 19:22 UTCEG score recompute
  19. 2026-08-09 13:46 UTCEPSS rescore
  20. 2026-08-09 06:59 UTCEG score recompute
  21. 2026-08-08 16:37 UTCEPSS rescore
  22. 2026-08-07 17:31 UTCEG score recompute
  23. 2026-08-06 19:30 UTCEG score recompute
  24. 2026-08-06 13:46 UTCEPSS rescore
  25. 2026-08-06 01:38 UTCEG score recompute
  26. 2026-08-05 19:17 UTCEPSS rescore
  27. 2026-08-04 15:10 UTCEPSS rescore
  28. 2026-08-04 10:38 UTCEPSS rescore
  29. 2026-08-04 00:48 UTCEG score recompute
  30. 2026-08-03 10:36 UTCEPSS rescore
  31. 2026-08-02 16:41 UTCEG score recompute
  32. 2026-08-02 02:27 UTCEPSS rescore
  33. 2026-08-01 04:16 UTCEPSS rescore
  34. 2026-07-30 16:28 UTCEPSS rescore
  35. 2026-07-30 01:30 UTCEPSS rescore
  36. 2026-07-27 14:41 UTCEG score recompute
  37. 2026-07-27 14:27 UTCOSV refresh

Frequently asked(5)

What is CVE-2026-32610?
CVE-2026-32610 is a high vulnerability published on March 18, 2026. Glances is an open-source system cross-platform monitoring tool. Prior to version 4.5.2, the Glances REST API web server ships with a default CORS configuration that sets alloworigins=["*"] combined with allowcredentials=True. When both of these options are enabled together, Starlette's…
When was CVE-2026-32610 disclosed?
CVE-2026-32610 was first published in the National Vulnerability Database on March 18, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32610 actively exploited?
CVE-2026-32610 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 72.6% of all scored CVEs.
What is the CVSS score of CVE-2026-32610?
CVE-2026-32610 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-32610?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32610, 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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32610

Explore →

Is Your Infrastructure Affected by CVE-2026-32610?

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

Start Free Scan →Browse All CVEs