# CVE-2025-63094: Information disclosure in n/a

> Attackers can access sensitive information via side-channel analysis of the data cache in XiangShan processors due to speculative execution and indirect branch prediction.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Dec 2025
- **Updated:** 18 Dec 2025
- **Also known as:** GHSA-mc7g-hphg-2wrh

## What is CVE-2025-63094?

CVE-2025-63094 is a high-severity vulnerability in n/a, published on 10 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

XiangShan Nanhu V2 and XiangShan Kunmighu V3 were discovered to use speculative execution and indirect branch prediction, allowing attackers to access sensitive information via side-channel analysis of the data cache.

Weakness: CWE-203 (Observable Discrepancy), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Xiangshan Xiangshan.

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

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

## Is CVE-2025-63094 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63094 is a high-severity vulnerability in n/a, published on 10 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-63094 in the wild and no public exploit code.

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

## Sources

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

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