Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.1amended

OpenClaw: Bonjour/DNS-SD TXT metadata steers CLI routing after failed service resolution

CVE-2026-35659GHSA-rvqr-hrcc-j9vv

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (openclaw 2026.3.22), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm openclaw

    Affected
    < 2026.3.22
    Fixed in
    2026.3.22

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
5.1 · CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-35659: 0.12% estimated exploitation activity in the next 30 days; percentile 1.70 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary Bonjour and DNS-SD TXT metadata could still steer CLI routing even when actual service resolution failed, allowing unresolved hints to influence the chosen target. Affected Packages / Versions - Package: openclaw (npm) - Affected: < 2026.3.22 - Fixed: = 2026.3.22 - Latest released tag checked: v2026.3.23-2 (630f1479c44f78484dfa21bb407cbe6f171dac87) - Latest published npm version checked: 2026.3.23-2 Fix Commit(s) - deecf68b59a9b7eea978e40fd3c2fe543087b569 Release Status The fix shipped in v2026.3.22 and remains present in v2026.3.23 and v2026.3.23-2. Code-Level Confirmation - src/infra/bonjour-discovery.ts now resolves and returns only concrete endpoints instead of falling back to unresolved TXT host and port hints. - src/cli/gateway-cli/discover.ts consumes only the fail-closed resolved endpoint path. OpenClaw thanks @nexrin for reporting.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-rvqr-hrcc-j9vv

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-rvqr-hrcc-j9vv

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-35659

Advisory: OpenClaw: Bonjour/DNS-SD TXT metadata steers CLI routing after failed service resolution
IDs: CVE-2026-35659, GHSA-rvqr-hrcc-j9vv
Record: https://patchnext.com/advisories/cve-2026-35659 (revision 3, source checked 26 Oct 2026, 12:48 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: openclaw 2026.3.22. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm openclaw: affected < 2026.3.22; fixed in 2026.3.22

## Suggested inspection (read-only)
- `npm ls openclaw --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on openclaw.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-rvqr-hrcc-j9vv (OSV record GHSA-rvqr-hrcc-j9vv lists affected ranges: npm openclaw >=0 <2026.3.22 (fixed))
- Verified: https://github.com/advisories/GHSA-rvqr-hrcc-j9vv (GitHub-reviewed advisory GHSA-rvqr-hrcc-j9vv lists affected ranges: npm openclaw >=0 <2026.3.22)

Commands are suggestions: review each one before running it.

Loading voting…