Cross-origin data theft via reflected credentialed CORS
Published Mar 18, 2026 · Updated Mar 18, 2026
Permissive CORS in the Glances REST API before 4.5.2 allows remote attackers to read monitoring and configuration data via browsers. The REST server combines wildcard allowed origins with credential support, causing Starlette middleware to reflect any supplied Origin and authorize cross-origin reads. Exploitation requires a user to visit attacker-controlled content; unauthenticated deployments expose all API data, while protected ones require cached browser credentials.
Summary
What happened
Permissive CORS in the Glances REST API before 4.5.2 allows remote attackers to read monitoring and configuration data via browsers. The REST server combines wildcard allowed origins with credential support, causing Starlette middleware to reflect any supplied Origin and authorize cross-origin reads. Exploitation requires a user to visit attacker-controlled content; unauthenticated deployments expose all API data, while protected ones require cached browser credentials.
The record
- CVE
- CVE-2026-32610
- Published
- Mar 18, 2026
- Updated
- Mar 18, 2026
- Vendor
- Glances Project
- Product
- Glances
- Classifications
- CWE-942, T1189
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 18, 2026CVE publishedPublication date reported by the CVE source.
- Mar 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 4.5.2
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GHSA-9jfm-9rc6-2hfq browser and curl proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo