# CVE-2025-47378: Exposure of Sensitive System Information to an Unauthorized Control Sphere in HLOS

> A cryptographic issue in Qualcomm Snapdragon HLOS allows unauthorized access to the boot loader and certificate chain, exposing sensitive system information.

- **Severity:** High 7.1 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A: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:** 2 Mar 2026
- **Updated:** 3 Mar 2026
- **Also known as:** GHSA-hpq4-rxrf-q4qg

## What is CVE-2025-47378?

CVE-2025-47378 is a high-severity vulnerability in Qualcomm Cologne Firmware, published on 2 Mar 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Cryptographic Issue when a shared VM reference allows HLOS to boot loader and access cert chain.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

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

It affects 74 products.


Products: Qualcomm Cologne Firmware, Qualcomm Fastconnect 6700 Firmware, Qualcomm Fastconnect 6800 Firmware, Qualcomm Fastconnect 6900 Firmware, Qualcomm Fastconnect 7800 Firmware, Qualcomm Lemans Au Lgit Firmware, Qualcomm Lemansau Firmware, Qualcomm Pandeiro Firmware, Qualcomm Qam8255p Firmware, Qualcomm Qamsrv1h Firmware, Qualcomm Qamsrv1m Firmware, Qualcomm Qca6391 Firmware, Qualcomm Qca6595 Firmware, Qualcomm Qca6595au Firmware, Qualcomm Qca6696 Firmware, Qualcomm Qca6698aq Firmware, Qualcomm Qca6797aq Firmware, Qualcomm Qln1083bd Firmware, Qualcomm Qln1086bd Firmware, Qualcomm Qpa1083bd Firmware and 54 more.

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

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

## Is CVE-2025-47378 being exploited?

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

## Other vulnerabilities in Qualcomm Cologne Firmware

- [CVE-2026-25283](https://insights.sbomify.com/CVE-2026-25283/): Stack-based Buffer Overflow in OOBM (high 8.8)
- [CVE-2026-25282](https://insights.sbomify.com/CVE-2026-25282/): Out-of-bounds Read in OOBM (high 7.9)
- [CVE-2026-57555](https://insights.sbomify.com/CVE-2026-57555/): Use After Free in DSP Service (high 7.8)
- [CVE-2026-57559](https://insights.sbomify.com/CVE-2026-57559/): Use After Free in DSP_Services (high 7.8)
- [CVE-2025-59607](https://insights.sbomify.com/CVE-2025-59607/): Untrusted Pointer Dereference in Windows Compute (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-47378 is a high-severity vulnerability in Qualcomm Cologne Firmware, published on 2 Mar 2026. 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-47378 in the wild and no public exploit code.

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

## Sources

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

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