How many CVEs have patched handleEnableOperator?

2 published CVEs changed handleEnableOperator in forgekeep/nebula-mesh, in 2 distinct patches totalling 6 changed lines, between 2026 and 2026.

What is the latest CVE that changed handleEnableOperator?

CVE-2026-47726 (nebula-mesh: GET /api/v1/audit-log discloses all entries to any operator), published 2026-07-28, changed lines 103 to 106 of internal/api/operators.go.

How does handleEnableOperator compare to the rest of forgekeep/nebula-mesh?

forgekeep/nebula-mesh has 14 CVEs with a located fix in total; 2 of them changed handleEnableOperator.

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

forgekeep/nebula-mesh

Function

handleEnableOperator

Name: handleEnableOperator in forgekeep/nebula-mesh: CVE fixes
Creator: RadicalNotion.AI
License: https://creativecommons.org/licenses/by-nc/4.0/

internal/api/operators.go

Last patched July 28, 2026

2

CVEs

That changed this function

2

Distinct patches

Backports counted once

6

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

handleEnableOperator in forgekeep/nebula-mesh was changed by 2 published CVE fixes in 2026, in 2 distinct patches that added or removed 6 lines in total.

forgekeep/nebula-mesh has 14 CVEs with a located fix in total, so 14% of them touched this function.

CVEs that patched it

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

nebula-mesh: GET /api/v1/audit-log discloses all entries to any operator
CVE-2026-47726 · lines 103–106 · +4 −0
High · CVSS 7.1
EPSS 0.4%2026-07-28
nebula-mesh: API endpoints lack ownership checks, enabling cross-operator privilege escalation
CVE-2026-47724 · line 104 · +1 −1
Critical · CVSS 9.9
EPSS 0.5%2026-07-23

Get an alert when the next CVE fix lands in forgekeep/nebula-mesh, with the patched functions.

Monitor nebula-mesh CVEs

Other functions in these files

Functions in the same file that CVE fixes also changed.

Other hotspots in the repository

Functions in forgekeep/nebula-mesh changed by the most CVE fixes.

Serve3 CVEs · internal/cli/serve.go handleMobileBundle2 CVEs · internal/api/mobile_bundle.go handleRotateCert2 CVEs · internal/api/hosts.go mintEnrollmentTokenForHost2 CVEs · internal/api/hosts.go handleGetBlocklist2 CVEs · internal/api/hosts.go handleGetAuditLog2 CVEs · internal/api/audit.go

All patched functions in forgekeep/nebula-mesh

Frequently asked questions

Common questions about CVE fixes to handleEnableOperator.

How many CVEs have patched handleEnableOperator?: 2 published CVEs changed handleEnableOperator in forgekeep/nebula-mesh, in 2 distinct patches totalling 6 changed lines, between 2026 and 2026.
What is the latest CVE that changed handleEnableOperator?: CVE-2026-47726 (nebula-mesh: GET /api/v1/audit-log discloses all entries to any operator), published 2026-07-28, changed lines 103 to 106 of internal/api/operators.go.
How does handleEnableOperator compare to the rest of forgekeep/nebula-mesh?: forgekeep/nebula-mesh has 14 CVEs with a located fix in total; 2 of them changed handleEnableOperator.
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 forgekeep/nebula-mesh 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