# CVE-2026-95815: OpenClaw iOS before 2026.8.11 Credential Exposure via Deep-Link URL Logging

> Attackers can extract bearer keys from diagnostic logs to forge deep links and submit agent requests without user confirmation.

- **Severity:** High 7.2 (`CVSS:4.0/AV:L/AC:H/AT:P/PR:N/UI:P/VC:H/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 22 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-5j57-84cx-r295, GHSA-wjj6-g7c3-q75f, MINI-239x-c674-8q95

## What is CVE-2026-95815?

CVE-2026-95815 is a high-severity vulnerability in OpenClaw iOS, published on 22 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

OpenClaw iOS before 2026.8.11 logs complete agent deep-link URLs including persistent bearer keys to unified logs as public diagnostic data. Attackers who obtain diagnostic archives can recover unrotated keys and replay them in forged deep links to submit agent requests without local confirmation prompts.

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

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


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

Upgrade to a fixed version.

## Is CVE-2026-95815 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-95815 is a high-severity vulnerability in OpenClaw iOS, published on 22 Sep 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-95815 in the wild and no public exploit code.

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

## Sources

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

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