Vulnerability in Nexting pinclaw OpenClaw channel plugin (CVE-2026-108757)
Summary
Vulnerability in Nexting pinclaw OpenClaw channel plugin (CVE-2026-108757). Data can be tampered with by attackers. Exploitable via POST /pinclaw/send..
Original description
The description as published by the source.
Nexting pinclaw OpenClaw channel plugin through 0.3.0 contains a missing authentication vulnerability in src/core/http-router.ts that skips the authToken check on POST /pinclaw/send. Unauthenticated attackers reaching port 18790, which binds all interfaces by default, can inject blind prompts into the user's main OpenClaw agent session as user instructions.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-108757 has been found in Nexting pinclaw OpenClaw channel plugin.
Attackers can target a specific entry point like POST /pinclaw/send. over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 6.5/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Nexting pinclaw OpenClaw channel plugin CVE-2026-108757" on the vendor's site.
CVE-2026-108757 (Nexting pinclaw OpenClaw channel plugin) — CWE-306 / CVSS v3 6.5
Attack vector: adjacent-network / unauthenticated / no user interaction
Attack surface: POST /pinclaw/send.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-306) exists in Nexting pinclaw OpenClaw channel plugin. Attackers reach the vulnerable code path via POST /pinclaw/send. without authentication.
Check the vendor advisory for the affected versions of Nexting pinclaw OpenClaw channel plugin. Attack surface: POST /pinclaw/send..
Severity: Medium (CVSS 6.5/10). Data can be tampered with by attackers.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /pinclaw/send. requests with malformed payloads or SQL meta-characters. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで Nexting pinclaw OpenClaw channel plugin を使っているサービスとバージョンを洗い出す。
-
2Hunt for indicators of compromise detect
grep 'POST /pinclaw/send.' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /pinclaw/send.への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Post-deployment verification verify
Replay attack against POST /pinclaw/send. on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。