# CVE-2026-63270: Environment/ini-file leaks

> Attackers can exfiltrate sensitive environment or INI file data by tricking users into opening documents with crafted URLs in LibreOffice.

- **Severity:** Medium 6.7 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:P/VC:H/VI:N/VA:N/SC:H/SI:N/SA: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:** Yes
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** BELL-CVE-2026-63270, DEBIAN-CVE-2026-63270, ECHO-a3c2-1cf9-5993, GHSA-p537-j8hg-x628, MINI-qxj8-g55x-p86c, UBUNTU-CVE-2026-63270

## What is CVE-2026-63270?

CVE-2026-63270 is a medium-severity vulnerability in The Document Foundation LibreOffice, published on 5 Oct 2026. 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

URLs could be constructed which expanded environment variable or INI file values, so potentially sensitive information could be exfiltrated to a remote server on opening a document containing such links. The check added for CVE-2024-12426 did not cover every place a document can supply a URL. XForms instance data and the Calc csv and sql data providers still reached the expansion. In fixed versions these places refuse URLs with internal schemes when the URL comes from the document.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-63270?


## How do I fix CVE-2026-63270?

Apply the vendor's patch.

## Is CVE-2026-63270 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-63270 and fix it if it is affected.

What it is: CVE-2026-63270 is a medium-severity vulnerability in The Document Foundation LibreOffice, published on 5 Oct 2026. 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-2026-63270 in the wild and no public exploit code.

Affected product: The Document Foundation 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-2026-63270/ (Markdown: https://insights.sbomify.com/CVE-2026-63270/index.md)
```

## Sources

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

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