Is there a patch available for CVE-2026-41339?

Yes, a patch is available for CVE-2026-41339. Update the affected software to the latest version immediately.

OpenClaw CVE-2026-41339

Q: What is the CVSS score of CVE-2026-41339?

CVE-2026-41339 has a CVSS 4.0 base score of 5.3 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

EUVD-2026-25323 MEDIUM

Exposure of Sensitive System Information to an Unauthorized Control Sphere (CWE-497)

2026-04-23 VulnCheck

GHSA-r7p2-r9g4-4xph

Information Disclosure Openclaw

5.3

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

5.3 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

4.3 MEDIUM

Network-reachable WebSocket endpoint requires low-privilege authentication; discloses partial filesystem paths only, no integrity or availability impact, no scope change.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Source Code Evidence Fetched

Jul 24, 2026 - 03:27 vuln.today

Analysis Generated

Jul 24, 2026 - 03:27 vuln.today

CVSS changed

Apr 23, 2026 - 22:28 NVD

4.3 (MEDIUM) 5.3 (MEDIUM)

EUVD ID Assigned

Apr 23, 2026 - 22:15 euvd

EUVD-2026-25323

Patch released

Apr 23, 2026 - 22:15 nvd

Patch available

CVE Published

Apr 23, 2026 - 21:57 nvd

MEDIUM 5.3

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

5 npm packages depend on openclaw (5 direct, 0 indirect)

Ecosystem-wide dependent count for version 2026.4.2.

DescriptionCVE.org

OpenClaw before 2026.4.2 exposes configPath and stateDir metadata in Gateway connect success snapshots to non-admin authenticated clients. Non-admin clients can recover host-specific filesystem paths and deployment details, enabling host fingerprinting and facilitating chained attacks.

AnalysisAI

Information disclosure in OpenClaw (npm) before 2026.4.2 allows low-privilege authenticated Gateway clients to recover host filesystem paths and deployment metadata that should be restricted to admin-scoped sessions. The Gateway connect success (hello-ok) snapshot unconditionally included configPath, stateDir, and authMode fields for all authenticated clients regardless of scope, exposing server-side deployment topology. No active exploitation has been identified (EPSS 0.03%, 8th percentile; no CISA KEV listing), but the disclosed paths materially assist host fingerprinting and can lower the cost of subsequent chained attacks against the gateway infrastructure.

Technical ContextAI

OpenClaw is an npm-distributed Gateway server that uses a WebSocket-based connection protocol. On successful authentication, the server emits a hello-ok message carrying a snapshot payload built by buildGatewaySnapshot() in src/gateway/server/health-state.ts. Prior to the fix, this function unconditionally resolved and returned configPath (absolute path to the server config file via createConfigIO().configPath), stateDir (the server state directory constant STATE_DIR), and authMode to every connecting client. CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere) precisely describes the root cause: internal server topology data was placed into a response channel accessible to low-trust principals. The affected CPE is cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*, covering all versions up to 2026.4.1. The fix (commit 676b748) gates these fields behind an includeSensitive flag that is only set when the authenticated session holds ADMIN_SCOPE, as checked in src/gateway/server/ws-connection/message-handler.ts.

RemediationAI

Upgrade the OpenClaw npm package to version 2026.4.2 or later, which gates configPath, stateDir, and authMode fields in Gateway hello-ok snapshots behind admin scope. The fix is confirmed in commit 676b748056b5efca6f1255708e9dd9469edf5e2e (https://github.com/openclaw/openclaw/commit/676b748056b5efca6f1255708e9dd9469edf5e2e) and the GHSA advisory (https://github.com/openclaw/openclaw/security/advisories/GHSA-2f7j-rp58-mr42). If immediate upgrade is not possible, restrict Gateway WebSocket endpoint access to trusted authenticated principals only using network-layer controls (firewall rules, mTLS, VPN enforcement), reducing the population of clients that can trigger the disclosure. This compensating control does not eliminate the vulnerability but narrows the attacker pool to already-trusted users. No code-free mitigation fully removes the path exposure without applying the patch.