How many CVEs have patched toSafeStrings?

1 published CVEs changed toSafeStrings in forgekeep/nebula-mesh, in 1 distinct patches totalling 11 changed lines, between 2026 and 2026.

What is the latest CVE that changed toSafeStrings?

CVE-2026-61699 (nebula-mesh: Certificate revocation is never enforced at the mesh), published 2026-09-04, changed lines 304 to 314 of internal/configgen/marshal.go.

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

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

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

toSafeStrings

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

internal/configgen/marshal.go

Last patched September 4, 2026

1

CVEs

That changed this function

1

Distinct patches

Backports counted once

11

Lines changed

Added plus removed

2026

Years

By CVE publication date

Overview

toSafeStrings in forgekeep/nebula-mesh was changed by 1 published CVE fixes in 2026, in 1 distinct patches that added or removed 11 lines in total.

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

CVEs that patched it

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

nebula-mesh: Certificate revocation is never enforced at the mesh
CVE-2026-61699 · lines 304–314 · +11 −0
High · CVSS 8.1
EPSS 0.4%2026-09-04

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.

1buildConfiginternal/configgen/marshal.go1 CVEs · 1 patches2026

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 toSafeStrings.

How many CVEs have patched toSafeStrings?: 1 published CVEs changed toSafeStrings in forgekeep/nebula-mesh, in 1 distinct patches totalling 11 changed lines, between 2026 and 2026.
What is the latest CVE that changed toSafeStrings?: CVE-2026-61699 (nebula-mesh: Certificate revocation is never enforced at the mesh), published 2026-09-04, changed lines 304 to 314 of internal/configgen/marshal.go.
How does toSafeStrings compare to the rest of forgekeep/nebula-mesh?: forgekeep/nebula-mesh has 14 CVEs with a located fix in total; 1 of them changed toSafeStrings.
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