# CVE-2025-40680: Encryption of sensitive data in CapillaryScope missing

> Local attackers can read proxy credentials and JWT tokens from the Windows registry due to lack of encryption in CapillaryScope.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:H/VI:L/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:** 24 Jul 2025
- **Updated:** 24 Jul 2025
- **Also known as:** GHSA-3g73-h9cm-2486

## What is CVE-2025-40680?

CVE-2025-40680 is a medium-severity vulnerability in CapillaryScope, published on 24 Jul 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Lack of sensitive data encryption in CapillaryScope v2.5.0 of Capillary io, which stores both the proxy credentials and the JWT session token in plain text within different registry keys on the Windows operating system. Any authenticated local user with read access to the registry can extract these sensitive values.

Weakness: CWE-311 (Missing Encryption of Sensitive Data)

## Which versions are affected by CVE-2025-40680?


## How do I fix CVE-2025-40680?

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

## Is CVE-2025-40680 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-40680 and fix it if it is affected.

What it is: CVE-2025-40680 is a medium-severity vulnerability in CapillaryScope, published on 24 Jul 2025. 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-2025-40680 in the wild and no public exploit code.

Affected product: CapillaryScope. 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-2025-40680/ (Markdown: https://insights.sbomify.com/CVE-2025-40680/index.md)
```

## Sources

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

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