# CVE-2025-48066: wire-webapp has no database deletion on client logout

> Failure to delete local database on logout allows attackers with physical access to read sensitive messages and data from the device.

- **Severity:** Medium 6.0 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 22 May 2025
- **Updated:** 22 May 2025
- **Also known as:** GHSA-qc6c-2hh8-qfh8

## What is CVE-2025-48066?

CVE-2025-48066 is a medium-severity vulnerability in wireapp wire-webapp, published on 22 May 2025. 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

wire-webapp is the web application for the open-source messaging service Wire. A bug fix caused a regression causing an issue with function to delete local data. Instructing the client to delete its local database on user logout does not result in deletion. This is the case for both temporary clients (marking the device as a public computer on login) and regular clients instructing the deletion of all personal information and conversations upon logout. Access to the machine is required to access the data. If encryption-at-rest is used, cryptographic material can't be exported. The underlying issue has been fixed with wire-webapp version 2025-05-14-production.0. In order to mitigate potential impact, the database must be manually deleted on devices where the option "This is a public computer" was used prior to log in or a log out with the request to delete local data with the affected versions has happened before.

Weakness: CWE-212 (Improper Removal of Sensitive Information Before Storage or Transfer), CWE-226 (Sensitive Information in Resource Not Removed Before Reuse)

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

It affects 1 product.


Products: Wire Wire-Webapp.

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

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

## Is CVE-2025-48066 being exploited?

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

## Other vulnerabilities in wireapp wire-webapp

- [CVE-2022-29168](https://insights.sbomify.com/CVE-2022-29168/): Cross Site Scripting in Wire Messages (critical 9.6)
- [CVE-2022-24799](https://insights.sbomify.com/CVE-2022-24799/): Cross Site Scripting in Wire Webapp (critical 9.6)
- [CVE-2021-32683](https://insights.sbomify.com/CVE-2021-32683/): XSS through createObjectURL (high 8.8)
- [CVE-2021-21400](https://insights.sbomify.com/CVE-2021-21400/): Entering code in App Lock modal sends input to conversation (high 7.1)
- [CVE-2022-39380](https://insights.sbomify.com/CVE-2022-39380/): wire-webapp contains Improper Handling of Exceptional Conditions leading to a DoS via Markdown Rendering (medium 5.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-48066 is a medium-severity vulnerability in wireapp wire-webapp, published on 22 May 2025. 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-2025-48066 in the wild and no public exploit code.

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

## Sources

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

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