# CVE-2025-13947: Webkit: webkitgtk: remote user-assisted information disclosure via file drag-and-drop

> Remote attackers can disclose local file contents via WebKitGTK's unverified file drag-and-drop mechanism, requiring user interaction.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Dec 2025
- **Updated:** 16 Oct 2026
- **Also known as:** DEBIAN-CVE-2025-13947, GHSA-j77f-3hf7-7rvg, UBUNTU-CVE-2025-13947

## What is CVE-2025-13947?

CVE-2025-13947 is a high-severity vulnerability in Red Hat Enterprise Linux 6, published on 3 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

A flaw was found in WebKitGTK. This vulnerability allows remote, user-assisted information disclosure that can reveal any file the user is permitted to read via abusing the file drag-and-drop mechanism where WebKitGTK does not verify that drag operations originate from outside the browser.

Weakness: CWE-346 (Origin Validation Error)

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


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

Apply the vendor's patch.

## Is CVE-2025-13947 being exploited?

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

Public exploit code:

- Private research and validation for WebKitGTK file DnD restore (CVE-2025-13947 follow-up) (github_poc): https://github.com/sirredbeard/WebKitGTK-DND-Fix

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13947 is a high-severity vulnerability in Red Hat Enterprise Linux 6, published on 3 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-13947 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 6. 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-13947/ (Markdown: https://insights.sbomify.com/CVE-2025-13947/index.md)
```

## Sources

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

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