# Glances: XML-RPC Multi-Origin CORS Configuration Silently Falls Back to Wildcard (Incomplete Fix for CVE-2026-33533)

Advisory record · `GHSA-87qc-fj39-wccr`

- **Identifiers:** `GHSA-87qc-fj39-wccr` · `CVE-2026-46608` · `PYSEC-2026-2495`
- **State:** Confirmed
- **Severity:** CVSS 7.4 High
- **Critical:** No
- **Weakness (CWE):** [CWE-183](https://cwe.mitre.org/data/definitions/183.html) · [CWE-942](https://cwe.mitre.org/data/definitions/942.html)
- **Tags:** [CWE-183](https://agentprime.io/advisories/tag/cwe-183.md) · [CWE-942](https://agentprime.io/advisories/tag/cwe-942.md)
- **Published:** 22 Jun 2026
- **Updated:** 21 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 22 Jun 2026, 21:27 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `glances` (PyPI): affected `<4.5.5`; fixed in `4.5.5`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The Glances XML-RPC server (glances -s) in versions before 4.5.5 always sends Access-Control-Allow-Origin as a wildcard when cors_origins lists more than one origin, so an explicit allowlist does not restrict browser access. An attacker who can get a victim's browser to visit a malicious web page can send a cross-origin request and read the system monitoring data, including process command lines. Upgrade to Glances 4.5.5 or later, which fixes the issue.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.4 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0040, the 34th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:42 UTC: First seen by agentprime
- 31 Oct 2026, 14:42 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-87qc-fj39-wccr)

## Sources

- [GitHub Advisory Database: GHSA-87qc-fj39-wccr](https://github.com/advisories/GHSA-87qc-fj39-wccr)
- [OSV: GHSA-87qc-fj39-wccr](https://osv.dev/vulnerability/GHSA-87qc-fj39-wccr)
- <https://github.com/nicolargo/glances/security/advisories/GHSA-87qc-fj39-wccr>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-46608>
- <https://github.com/advisories/GHSA-87qc-fj39-wccr>
- <https://github.com/nicolargo/glances>
- <https://github.com/nicolargo/glances/releases/tag/v4.5.5>
- <https://github.com/pypa/advisory-database/tree/main/vulns/glances/PYSEC-2026-2495.yaml>
- <https://pypi.org/project/glances>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-87qc-fj39-wccr>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-87qc-fj39-wccr/>. Everything for agents: <https://agentprime.io/llms.txt>.