Is CVE-2026-61699 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-61699 being exploited in the wild.

How severe is CVE-2026-61699?

High severity, with a CVSS score of 8.1, published 4 September 2026.

Which products and versions are affected?

Forgekeep Nebula-Mesh < 0.7.1; github.com/forgekeep/nebula-mesh (Go) < 0.7.1, SEMVER:introduced=0,fixed=0.7.1.

Is there a fix for CVE-2026-61699?

Yes. github.com/forgekeep/nebula-mesh (Go): upgrade to 0.7.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-61699 attacked?

It is attacked over the network, in a software library.

Am I affected by CVE-2026-61699?

Check whether you run Forgekeep Nebula-Mesh or github.com/forgekeep/nebula-mesh (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-61699: forgekeep nebula-mesh certificate revocation failure in agent

Q: Is there a fix for CVE-2026-61699?

Yes. github.com/forgekeep/nebula-mesh (Go): upgrade to 0.7.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-61699 attacked?

It is attacked over the network, in a software library.

Q: Am I affected by CVE-2026-61699?

Check whether you run Forgekeep Nebula-Mesh or github.com/forgekeep/nebula-mesh (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-61699 · Severity: high · CVSS 8.1 · Published 2026-09-04

nebula-mesh is a tool used to manage secure, private networks. A flaw in the software prevents the system from actually revoking access for blocked or compromised users. In practice, this means that even if an administrator 'blocks' a device, that device can continue to access the private network and its sensitive data for up to a year, creating a significant security gap.

Technologies: Forgekeep Nebula-Mesh, github.com/forgekeep/nebula-mesh (Go). Vendors: Forgekeep, Go.

Quick answers

Is CVE-2026-61699 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-61699 being exploited in the wild.
How severe is CVE-2026-61699?: High severity, with a CVSS score of 8.1, published 4 September 2026.
Which products and versions are affected?: Forgekeep Nebula-Mesh < 0.7.1; github.com/forgekeep/nebula-mesh (Go) < 0.7.1, SEMVER:introduced=0,fixed=0.7.1.
Is there a fix for CVE-2026-61699?: Yes. github.com/forgekeep/nebula-mesh (Go): upgrade to 0.7.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-61699 attacked?: It is attacked over the network, in a software library.
Am I affected by CVE-2026-61699?: Check whether you run Forgekeep Nebula-Mesh or github.com/forgekeep/nebula-mesh (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/forgekeep/nebula-mesh (Go): upgrade to 0.7.1 or later
```
go get github.com/forgekeep/nebula-mesh@v0.7.1
```

Technical details

The vulnerability exists because the nebula-mesh agent decodes the 'blocklist' JSON field from the server's update response but subsequently discards it without updating the local configuration. Additionally, the configuration generator lacks the logic to emit the 'pki.blocklist' field into the agent's config.yml. This results in a failure to enforce certificate revocation at the peer level (CWE-299). An attacker with exfiltrated host credentials can maintain network access despite being revoked in the management UI. The issue is resolved in version 0.7.1 by ensuring the blocklist is correctly propagated and applied to the agent's configuration.

Affected products

forgekeep nebula-mesh < 0.7.1

Identifiers

CVE-2026-61699
GHSA-cm26-5974-52h8
GO-2026-5986

Timeline

2026-06-23: disclosed
2026-07-14: advisory
2026-07-14: patched: Fixed in version 0.7.1

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.