ForgeKeep - CraftedSignal Threat Feed

Nebula-Mesh Stores Operator Session Tokens in Plaintext, Enabling Session Hijacking (CVE-2026-53603)

hello@craftedsignal.io — Tue, 14 Jul 2026 20:37:22 +0000

ForgeKeep's nebula-mesh, an application for managing mesh networks, contains a critical vulnerability, CVE-2026-53603, affecting versions up to and including 0.3.7. This flaw stems from the insecure storage of operator session tokens, which are saved in plaintext format within the operator_sessions table of the underlying database. Unlike API keys and enrollment tokens, which are properly hashed, these 32-byte random hex values are directly readable. An attacker who manages to gain read access to the database - through methods such as database backups, snapshots, file copies, or SQL-level disclosure - can easily extract these active session tokens. Once obtained, these tokens can be used to hijack operator sessions, granting unauthorized access to the nebula-mesh management interface without requiring additional authentication. This poses a significant risk as it allows attackers to control the mesh environment and perform malicious operations.

Attack Chain

Attacker gains unauthorized read access to the nebula-mesh application's underlying database through a separate vulnerability (e.g., SQL injection, file system compromise, or weak database credentials).
Attacker queries the operator_sessions table within the compromised database.
Attacker extracts plaintext 32-byte hex session tokens from the token column, specifically from internal/models/operator.go:61.
Attacker uses a stolen session token to forge a cookie, which is then sent to the nebula-mesh operator interface.
The nebula-mesh application authenticates the attacker based on the valid, stolen session token.
Attacker successfully hijacks the operator's session, gaining unauthorized access to the nebula-mesh management interface with the privileges of the compromised operator.
Attacker performs unauthorized actions, such as modifying network configurations, deploying malicious updates, or exfiltrating sensitive data from the mesh environment.

Impact

The successful exploitation of CVE-2026-53603 leads to a complete compromise of the nebula-mesh operator's session. This allows an attacker to gain full control over the affected nebula-mesh environment, bypassing all authentication mechanisms once database read access is achieved. Consequences include unauthorized configuration changes, deployment of malicious code, data exfiltration, or disruption of network operations. Since session tokens are valid for 24 hours, an attacker could maintain unauthorized access for an extended period, potentially leading to persistent control over critical infrastructure. Any organization using affected versions of nebula-mesh faces a high risk of remote code execution, denial of service, or unauthorized data access if their database is compromised.

Recommendation

Immediately apply the patch for CVE-2026-53603 by updating to a version of go/github.com/forgekeep/nebula-mesh greater than 0.3.7.
Restrict and encrypt all database backups and snapshots to prevent unauthorized access to the database where operator_sessions are stored.
Rotate the nebula-mesh operator database credentials and invalidate existing operator sessions after patching to ensure all plaintext tokens are no longer valid.
Implement strong access controls and logging for the database instance hosting the nebula-mesh data, monitoring for unusual query patterns or unauthorized access attempts.

ForgeKeep Nebula-Mesh Certificate Revocation Bypass Vulnerability

hello@craftedsignal.io — Tue, 14 Jul 2026 20:36:00 +0000

A significant security flaw, tracked as CVE-2026-61699, has been identified in ForgeKeep's nebula-mesh, affecting versions prior to 0.7.1. This vulnerability prevents the enforcement of certificate revocation, allowing compromised or offboarded hosts to retain full access to the Nebula mesh network. Despite the Nebula server correctly adding a host's certificate fingerprint to a per-CA blocklist and attempting to distribute this information, the agent fails to process or apply these updates. Furthermore, the configuration generator does not include the pki.blocklist entry in the agent's config.yml. This creates a critical security blind spot, as an attacker who has exfiltrated a host's key and certificate can bypass administrative revocation actions and maintain unauthorized persistence on the network for the remaining lifetime of the certificate, which can be up to 365 days for mobile hosts or 30 days for agent hosts.

Attack Chain

Initial Compromise: An attacker successfully compromises a host within a Nebula mesh environment, gaining initial access through unrelated means (e.g., exploitation of another vulnerability or social engineering).
Credential Exfiltration: The attacker locates and exfiltrates the compromised host's Nebula client certificate (host.crt) and private key (host.key) files, which are used for authentication to the mesh.
Operator Revocation Attempt: Upon detecting the compromise or as part of a routine offboarding process, the network operator initiates a revocation action for the compromised host via the Nebula administrative UI or API.
Server-Side Blocklist Update: The Nebula server correctly processes the revocation, adds the compromised host's certificate fingerprint to its internal per-CA blocklist, and flags other agents for updates.
Agent Update Failure: Neighboring Nebula agents poll the server and receive the blocklist information within the UpdatesResponse, but due to a flaw in internal/agent/poller.go, they decode and then discard this blocklist without applying it to their local configuration.
Configuration Generation Flaw: Even if a configuration re-render is triggered, the configgen component in internal/configgen/marshal.go and internal/configgen/generator.go lacks the necessary fields to include the pki.blocklist entry in the generated config.yml.
Persistence Maintained: The attacker, using the previously exfiltrated host.key and host.crt, continues to operate the compromised host (or a clone) within the Nebula mesh, establishing connections and maintaining full overlay network reachability to all peers, completely bypassing the intended revocation.
Prolonged Unauthorized Access: The attacker retains unauthorized access for the full duration of the host's certificate validity (up to 30 days for agents and 365 days for mobile hosts), as the mesh peers continue to validate and accept the "revoked" certificate.

Impact

The failure to enforce certificate revocation in ForgeKeep's nebula-mesh allows an already compromised host to maintain unauthorized network access and persistence despite administrative actions to block it. This means that a host, once deemed untrustworthy and revoked by an operator, can continue to communicate within the overlay network for an extended period - up to 30 days for agent hosts and 365 days for mobile hosts. An attacker who has exfiltrated the necessary certificate and key material can leverage this flaw to sustain command and control, exfiltrate data, or launch further attacks from a seemingly blocked endpoint. The operational impact is a false sense of security, as the UI/API may show a host as blocked while it retains full mesh connectivity, making it a critical bypass for defense evasion and persistence.

Recommendation

Upgrade immediately: Patch affected ForgeKeep nebula-mesh installations to version 0.7.1 or later to address CVE-2026-61699.
Monitor post-revocation activity: Implement out-of-band monitoring for any network activity originating from hosts that have been administratively revoked, as they may still be active on the Nebula mesh due to CVE-2026-61699.
Review Nebula deployment: Assess the integrity of all Nebula agents to ensure they are correctly updated and capable of processing and applying certificate blocklists.
Implement supplementary controls: Apply additional network access controls (e.g., host-based firewalls, network segmentation) for critical services within the Nebula mesh to provide layered defense against unrevoked compromised nodes.

Nebula-mesh Non-Admin SSRF Bypass via Webhook Configuration

hello@craftedsignal.io — Tue, 14 Jul 2026 20:34:52 +0000

A critical authorization bypass vulnerability (GHSA-7rx3-5wx3-5v76) in ForgeKeep's Nebula-mesh, affecting versions 0.6.0 through 0.7.1, allows non-admin operators to bypass server-side request forgery (SSRF) protection. Specifically, a user with the user role can enable allow_private: true when configuring webhook subscriptions (POST/PATCH /api/v1/webhook-subscriptions), a field that lacks proper administrative access checks. This action forces the Nebula-mesh server's webhook dispatcher to use an unguarded HTTP client, circumventing internal network access controls and enabling connections to private, loopback, or link-local IP addresses. This flaw grants low-privileged attackers the ability to probe internal networks, interact blindly with internal services, and potentially exfiltrate sensitive data, such as cloud IAM credentials, escalating their privileges within the environment.

Attack Chain

A non-admin operator (with user role) obtains a legitimate API key for the Nebula-mesh management interface.
The operator sends an HTTP POST request to /api/v1/webhook-subscriptions, including allow_private: true in the JSON request body, along with a target internal or loopback URL (e.g., http://127.0.0.1:9999/internal-admin).
The Nebula-mesh server processes this request and creates a webhook subscription, persisting the allow_private: true setting without performing an administrative role check.
The operator triggers an event that corresponds to the webhook's subscription criteria (e.g., host.enrolled, host.blocked, host.unblocked) for a resource they legitimately own.
Upon receiving the event, the Nebula-mesh server's webhook dispatcher prepares to send a notification. Due to allow_private: true, it selects an unguarded HTTP client, bypassing the standard SSRF protection mechanisms.
The Nebula-mesh server initiates an outbound HTTP POST request from its own network context to the internal or loopback URL specified by the operator.
The operator can query the status of the created webhook subscription (GET /api/v1/webhook-subscriptions/{id}) to observe last_status and last_error fields, functioning as a reachability oracle for internal services.
Through iterative probing and blind interaction, the attacker can map the internal network, identify vulnerable services, and potentially extract sensitive information like cloud metadata or access control credentials, leading to privilege escalation.

Impact

A successful exploitation grants a non-admin operator server-side request capabilities against internal-only or loopback addresses, completely circumventing the security boundaries enforced for administrators. This exposure enables malicious actors to perform extensive internal network reconnaissance, identify and interact with sensitive internal services that are not typically exposed, and potentially exfiltrate critical information such as cloud IAM credentials from metadata services (depending on the cloud provider's metadata service version, e.g., IMDSv1). The consequence is a significant privilege escalation from a low-privileged user account, allowing for broader unauthorized access and potential control over the Nebula-mesh deployment and its underlying infrastructure.

Recommendation

Patch Nebula-mesh to a version greater than 0.7.1 (or the fix release for GHSA-7rx3-5wx3-5v76) immediately to remediate the vulnerability.
Deploy the Sigma rule Detect Nebula-mesh Server Outbound Connections to Internal/Loopback IPs (SSRF Attempt) to your SIEM to detect suspicious network connections originating from the Nebula-mesh server to private, loopback, or link-local IP addresses.
Implement network segmentation to restrict outbound connections from the Nebula-mesh server to only explicitly authorized and necessary internal services, limiting the impact of any potential SSRF.