# CVE-2026-63268: LFI via calcext:data-mappings, sql provider and sdbc:flat:file:// db href

> An attacker can read local text files into a spreadsheet by crafting a document with a malicious SQL data link, exposing sensitive local data.

- **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-63268, DEBIAN-CVE-2026-63268, ECHO-9bb6-16d7-0730, GHSA-rvj5-mfwr-769g, MINI-pw8m-g9qw-525q, UBUNTU-CVE-2026-63268

## What is CVE-2026-63268?

CVE-2026-63268 is a medium-severity path traversal 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

LibreOffice Calc can link a cell range to an external data source, and the link is saved in the document. A link of the sql type could name a folder of local text files as a database, so opening a document could read a local text file into the sheet. In fixed versions only the csv, html and xml data providers are restored when a document is loaded.

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

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


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

Apply the vendor's patch.

## Is CVE-2026-63268 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-63268 is a medium-severity path traversal 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-63268 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-63268/ (Markdown: https://insights.sbomify.com/CVE-2026-63268/index.md)
```

## Sources

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

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