# CVE-2025-13524: Information disclosure in Wickr

> An attacker can continue receiving audio from a victim after the call window is closed due to improper resource release in AWS Wickr desktop clients.

- **Severity:** Medium 6.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Nov 2025
- **Updated:** 21 Nov 2025
- **Also known as:** GHSA-c6ch-vfqm-whrq

## What is CVE-2025-13524?

CVE-2025-13524 is a medium-severity vulnerability in AWS Wickr, published on 21 Nov 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Improper resource release in the call termination process in AWS Wickr before version 6.62.13 on Windows, macOS and Linux may allow a call participant to continue receiving audio input from another user after they close their call window. This issue occurs under certain conditions, which require the affected user to take a particular action within the application

To mitigate this issue, users should upgrade AWS Wickr, Wickr Gov and Wickr Enterprise desktop version to version 6.62.13.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

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


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

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

## Is CVE-2025-13524 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13524 is a medium-severity vulnerability in AWS Wickr, published on 21 Nov 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-13524 in the wild and no public exploit code.

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

## Sources

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

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