How many CVEs have patched allow_operators?

1 published CVEs changed allow_operators in nicolargo/glances, in 1 distinct patches totalling 13 changed lines, between 2026 and 2026.

What is the latest CVE that changed allow_operators?

CVE-2026-68519 (Glances: `--disable-config-exec` does not cover on-alert action commands (incomplete fix of CVE-2026-53925)), published 2026-08-17, changed lines 87 to 99 of glances/actions.py.

How does allow_operators compare to the rest of nicolargo/glances?

nicolargo/glances has 21 CVEs with a located fix in total; 1 of them changed allow_operators.

What do the line numbers refer to?

Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

RadicalNotion.AI

Log in Create an account

nicolargo/glances

Function

allow_operators

Name: allow_operators in nicolargo/glances: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

glances/actions.py

Last patched August 17, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

13

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

allow_operators in nicolargo/glances was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 13 lines in total.

nicolargo/glances has 21 CVEs with a located fix in total, so 5% of them touched this function.

CVEs that patched it

Every published CVE whose fix changed allow_operators, newest first, with the lines each fix touched.

Glances: `--disable-config-exec` does not cover on-alert action commands (incomplete fix of CVE-2026-53925)
CVE-2026-68519 · lines 87–99 · +13 −0
High · CVSS 7.1
EPSS 0.2%2026-08-17

Get an alert when the next CVE fix lands in nicolargo/glances, with the patched functions.

Monitor glances CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in nicolargo/glances changed by the most CVE fixes.

_router4 CVEs · glances/outputs/glances_restful_api.py run3 CVEs · glances/actions.py __init__3 CVEs · glances/outputs/glances_restful_api.py _sanitize_value2 CVEs · glances/actions.py as_dict_secure2 CVEs · glances/config.py _api_config_section_item2 CVEs · glances/outputs/glances_restful_api.py

All patched functions in nicolargo/glances

Frequently asked questions

Common questions about CVE fixes to allow_operators.

How many CVEs have patched allow_operators?: 1 published CVEs changed allow_operators in nicolargo/glances, in 1 distinct patches totalling 13 changed lines, between 2026 and 2026.
What is the latest CVE that changed allow_operators?: CVE-2026-68519 (Glances: `--disable-config-exec` does not cover on-alert action commands (incomplete fix of CVE-2026-53925)), published 2026-08-17, changed lines 87 to 99 of glances/actions.py.
How does allow_operators compare to the rest of nicolargo/glances?: nicolargo/glances has 21 CVEs with a located fix in total; 1 of them changed allow_operators.
What do the line numbers refer to?: Line numbers are in the fixed version of the file, as the upstream patch left it. A CVE whose fix was backported to several branches is listed once, with the lines from the upstream commit.

References

Fix locations are computed by RadicalNotion.AI from the upstream patch diff of each CVE. CVE data is sourced from the CVE Program.

Track nicolargo/glances CVEs

Get an alert when a new CVE lands in this repository, with the patched functions and AI-written remediation guidance.

Create an account See pricing