# CVE-2025-0514: Executable hyperlink Windows path targets executed unconditionally on activation

> Attackers can execute arbitrary Windows executables via malicious hyperlinks in LibreOffice documents, requiring user activation.

- **Severity:** High 7.2 (`CVSS:4.0/AV:L/AC:H/AT:N/PR:N/UI:P/VC:H/VI:L/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Feb 2025
- **Updated:** 25 Feb 2025
- **Also known as:** GHSA-f6mr-g7jq-gx82

## What is CVE-2025-0514?

CVE-2025-0514 is a high-severity code injection vulnerability in Libreoffice Libreoffice, published on 25 Feb 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

Improper Input Validation vulnerability in The Document Foundation LibreOffice allows Windows Executable hyperlink  targets to be executed unconditionally on activation.This issue affects LibreOffice: from 24.8 before < 24.8.5.

Weakness: CWE-20 (Improper Input Validation)

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

It affects 1 product.


Products: Libreoffice Libreoffice.

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

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

## Is CVE-2025-0514 being exploited?

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

## Other vulnerabilities in Libreoffice Libreoffice

- [CVE-2024-5261](https://insights.sbomify.com/CVE-2024-5261/): TLS certificate are not properly verified when utilizing LibreOfficeKit (critical 10.0)
- [CVE-2019-9855](https://insights.sbomify.com/CVE-2019-9855/): Windows 8.3 path equivalence handling flaw allows LibreLogo script execution (critical 9.8)
- [CVE-2018-14939](https://insights.sbomify.com/CVE-2018-14939/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-8358](https://insights.sbomify.com/CVE-2017-8358/): Memory corruption in n/a (critical 9.8)
- [CVE-2017-7882](https://insights.sbomify.com/CVE-2017-7882/): Memory corruption in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-0514 is a high-severity code injection vulnerability in Libreoffice Libreoffice, published on 25 Feb 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-0514 in the wild and no public exploit code.

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

## Sources

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

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