CVE-2026-68517 nicolargo CVE debrief

Who should care

Defenders responsible for Glances deployments, security teams, and vulnerability management teams should assess exposure and prioritize upgrading to version 4.5.6 or later. This includes operators and administrators of Glances in their environment, as well as teams responsible for monitoring and incident response.

Why it matters

CVE-2026-68517 is a vulnerability in the Glances open-source system monitoring tool that can lead to exposure of authenticated REST API data. Defenders should prioritize verifying and upgrading to Glances version 4.5.6 or later to mitigate this vulnerability.

• Potential exposure of authenticated REST API data to untrusted websites
• Risk of unauthorized access to sensitive data
• Need for verification and upgrade to Glances version 4.5.6 or later

Technical summary

The cors_origins guard in glances/outputs/glances_restful_api.py uses exact list equality instead of wildcard membership, allowing a multi-origin list containing the wildcard to retain cors_credentials and expose authenticated REST API data to an untrusted website visited by a previously authenticated user. This issue affects Glances versions prior to 4.5.6 and is fixed in version 4.5.6. The issue can lead to exposure of authenticated REST API data. Defenders should prioritize verifying and upgrading to Glances version 4.5.6 or later to mitigate this vulnerability.

Defensive priority

Defenders should prioritize verifying and upgrading to Glances version 4.5.6 or later to mitigate this vulnerability.

Recommended defensive actions

• Verify and upgrade to Glances version 4.5.6 or later
• Review and adjust CORS configurations to prevent unauthorized access
• Monitor for potential exploitation attempts
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The vulnerability is confirmed in Glances versions prior to 4.5.6. The issue is fixed in version 4.5.6. This issue arises from the cors_origins guard in glances/outputs/glances_restful_api.py, which uses exact list equality instead of wildcard membership. A multi-origin list containing the wildcard can retain cors_credentials and expose authenticated REST API data to an untrusted website visited by a previously authenticated user. Defenders should verify and prioritize upgrading to Glances version 4.5.6 or later to mitigate this risk.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.