CVE-2026-46608: Glances: XML-RPC Multi-Origin CORS Configuration Silently Falls Back to Wildcard (Incomplete Fix for CVE-2026-33533)
(updated )
The Glances XML-RPC server (glances -s) introduced a configurable CORS origin list in version 4.5.3 as a mitigation for CVE 2026-33533. However, the implementation silently falls back to Access-Control-Allow-Origin: * whenever cors_origins contains more than one entry. An operator who configures an explicit two-entry allowlist (e.g. two internal dashboard origins) intending to restrict browser access instead receives the unrestricted wildcard — the same exposure that the original CVE described. A malicious web page served from any origin can issue a CORS simple request to /RPC2 and read the full system monitoring dataset without the victim’s knowledge.
References
- github.com/advisories/GHSA-87qc-fj39-wccr
- github.com/nicolargo/glances
- github.com/nicolargo/glances/releases/tag/v4.5.5
- github.com/nicolargo/glances/security/advisories/GHSA-87qc-fj39-wccr
- github.com/pypa/advisory-database/tree/main/vulns/glances/PYSEC-2026-2495.yaml
- nvd.nist.gov/vuln/detail/CVE-2026-46608
- pypi.org/project/glances
Code Behaviors & Features
Detect and mitigate CVE-2026-46608 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →