# CVE-2026-108757: Nexting pinclaw through 0.3.0 Missing Authentication via POST /pinclaw/send

> Unauthenticated attackers can inject blind prompts into the main agent session via an unsecured endpoint, potentially leading to code execution or privilege escalation.

- **Severity:** High 7.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-w679-vj8x-2q83

## What is CVE-2026-108757?

CVE-2026-108757 is a high-severity missing authorization vulnerability in Nexting pinclaw, published on 11 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-108757?


## How do I fix CVE-2026-108757?

No fix has been published for CVE-2026-108757 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-108757 being exploited?

There is no known exploitation of CVE-2026-108757 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-108757 and fix it if it is affected.

What it is: CVE-2026-108757 is a high-severity missing authorization vulnerability in Nexting pinclaw, published on 11 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-108757 in the wild and no public exploit code.

Affected product: Nexting pinclaw. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-108757/ (Markdown: https://insights.sbomify.com/CVE-2026-108757/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-108757
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-108757
- OSV: https://osv.dev/vulnerability/CVE-2026-108757

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-108757/
Summaries are generated and may contain mistakes; the official description above is the record.