cve.bz

CVE-2026-34839 nicolargo glances

7.7 highExploit referenceEPSS 0.4%Fix available

High (7.7) in nicolargo glances. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in glances 4.5.4.

On this page
Glances is an open-source system cross-platform monitoring tool. Prior to version 4.5.4, the Glances web server exposes a REST API (`/api/4/*`) that is accessible without authentication and allows cross-origin requests from any origin due to a permissive CORS policy (`Access-Control-Allow-Origin: *`). This allows a malicious website to read sensitive system information from a running Glances instance in the victim’s browser, leading to cross-origin data exfiltration. While a previous advisory exists for XML-RPC CORS issues, this report demonstrates that the REST API (`/api/4/*`) is also affected and exposes significantly more sensitive data. Version 4.5.4 patches the issue.

Severity

CVSS 4.0

7.7 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

CVSS 3.1

6.5 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 37th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: yes · Technical impact: partial, assessed 2026-04-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-306 Missing Authentication for Critical Functionality
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-942 Permissive Cross-domain Security Policy with Untrusted Domains
OWASP Top 10
A01:2025 Broken Access Control, A02:2025 Security Misconfiguration, A07:2025 Authentication Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-34839 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-34839?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-34839?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-34839 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
nicolargo:glancesbefore 4.5.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-gfc2-9qmw-w7vhPyPIglances<4.5.44.5.4
PYSEC-2026-2175PyPIglances<4.5.44.5.4

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13glancesno fix listedDEBIAN-CVE-2026-34839
Debian14glances4.5.4+dfsg-1DEBIAN-CVE-2026-34839
Ubuntu22.04:LTS, 24.04:LTS, 25.10 and 5 moreglancesno fix listedUBUNTU-CVE-2026-34839
openSUSETumbleweedpython-Glances4.5.4-1.1openSUSE-SU-2026:10602-1

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · openSUSE.

Attack patterns (CAPEC)

  • CAPEC-12 Choosing Message Identifier Likelihood: High · Severity: High
  • CAPEC-36 Using Unpublished Interfaces or Functionality Likelihood: Medium · Severity: High
  • CAPEC-62 Cross Site Request Forgery Likelihood: High · Severity: Very High
  • CAPEC-166 Force the System to Reset Values Severity: Medium
  • CAPEC-216 Communication Channel Manipulation

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON