# CVE-2026-125361: Tencent BrowserSkill through 0.4.2 Missing Authentication in Local WebSocket Transport


- **Severity:** High 7.2 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 9 Nov 2026
- **Also known as:** GHSA-5pfr-frx5-hqwp

## What is CVE-2026-125361?

CVE-2026-125361 is a high-severity vulnerability in Tencent BrowserSkill, published on 9 Nov 2026. 

### Official description

Tencent BrowserSkill through 0.4.2 contains a missing authentication vulnerability that allows local attackers to impersonate the bsk daemon because remoteSocket() connects to the loopback WebSocket without credentials or peer verification. Attackers who bind the daemon port before it starts or after it exits receive the extension's full tool surface, including evaluate, to run JavaScript through CDP in logged-in browser tabs.

Weakness: CWE-923 (Improper Restriction of Communication Channel to Intended Endpoints)

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


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

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

## Is CVE-2026-125361 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125361 is a high-severity vulnerability in Tencent BrowserSkill, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-125361 in the wild and no public exploit code.

Affected product: Tencent BrowserSkill. 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-125361/ (Markdown: https://insights.sbomify.com/CVE-2026-125361/index.md)
```

## Sources

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

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