Skip to main content
VulnerabilityPublished

CVE-2026-68517: nicolargo glances · Permissive Cross-domain Policy with Untrusted Domains

Affects nicolargo glancesSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 4.5.6 when convenient.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.5.6
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade glances and nicolargo/glances to 4.5.6.

Affected software

ProductAffectedFixed in
nicolargoglancesAffected
  • <4.5.6
Fixed in
  • 4.5.6
GitHubnicolargo/glancespkg:github/nicolargo/glancesOther threatsAffected
  • <4.5.6
Fixed in
  • 4.5.6

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Glances to version 4.5.6 or later, where this vulnerability is fixed. No other mitigation is indicated or required according to the provided data.

Description

CVE-2026-68517 is a medium severity vulnerability in the open-source system monitoring tool Glances. Versions prior to 4.5.6 have a permissive cross-domain policy issue in the RESTful API implementation. The vulnerability arises because the CORS origins guard uses exact list equality instead of wildcard membership, allowing a multi-origin list containing a wildcard to retain credentials and expose authenticated API data to untrusted websites. This issue is fixed in version 4.5.6.

References

Community reviews

Loading reviews…