# CVE-2026-93982: OpenPanel through 2.3.0 MCP Authentication Token in Query Parameter Logged Plaintext

> Attackers with log access can steal MCP authentication tokens from plaintext logs to replay requests and access project analytics.

- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Sep 2026
- **Updated:** 2 Oct 2026
- **Also known as:** GHSA-8wx6-g25r-2943, GHSA-xvpp-2hfw-c93c

## What is CVE-2026-93982?

CVE-2026-93982 is a medium-severity vulnerability in Openpanel-dev openpanel, published on 19 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

OpenPanel through 2.3.0 writes Model Context Protocol authentication tokens from URL query parameters to plaintext application logs without redaction. Attackers with access to application stdout or centralized logging systems can capture base64-encoded credentials to replay MCP requests and access project analytics.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

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


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

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

## Is CVE-2026-93982 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93982 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93982 is a medium-severity vulnerability in Openpanel-dev openpanel, published on 19 Sep 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-93982 exists.

Affected product: Openpanel-dev openpanel. 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-93982/ (Markdown: https://insights.sbomify.com/CVE-2026-93982/index.md)
```

## Sources

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

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