# CVE-2025-14551: Senstive information disclosure was affecting subiquity

> Attackers can obtain sensitive user credentials, such as Wi-Fi passwords, from crash logs generated by the Ubuntu installer during installation failures.

- **Severity:** Low 2.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:L/SI:N/SA:N/E:U`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2026
- **Updated:** 10 Apr 2026
- **Also known as:** GHSA-5p47-92qw-3767, PYSEC-2026-135, UBUNTU-CVE-2025-14551

## What is CVE-2025-14551?

CVE-2025-14551 is a low-severity vulnerability in Canonical Ubuntu, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In Ubuntu, Subiquity version 24.04.4 could leak sensitive user credentials during crash reporting. Upon installation failure, if a user submitted a bug report to Launchpad, Subiquity could include certain user credentials, such as the user's plaintext Wi-Fi password, in the attached logs.

Weakness: CWE-1258 (Exposure of Sensitive System Information Due to Uncleared Debug Information)

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

1 open source package ship an affected version, including subiquity. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `subiquity` | PyPI | All versions to 24.04.4 | None |

Products: Canonical Ubuntu Subiquity.

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

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

## Is CVE-2025-14551 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-14551 is a low-severity vulnerability in Canonical Ubuntu, published on 9 Apr 2026. 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-14551 in the wild and no public exploit code.

Affected packages and fixed versions:
- subiquity (PyPI): affected all versions up to 24.04.4; no fix listed

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

## Sources

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

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