# CVE-2026-63267: LFI and GET SSRF via calcext:data-mappings and csv provider

> Opening a malicious LibreOffice Calc document can trigger Server-Side Request Forgery and Local File Inclusion, allowing attackers to read local files or access internal network resources.

- **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-63267, DEBIAN-CVE-2026-63267, ECHO-8cc6-8bbf-8126, GHSA-2r33-w77m-6p5h, MINI-9q2c-v4vj-4w63, UBUNTU-CVE-2026-63267

## What is CVE-2026-63267?

CVE-2026-63267 is a medium-severity server-side request forgery 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 csv data source, and the link is saved in the document. Such a link was fetched while the document loaded, so opening a document could read a local file into the sheet, or make a request to a host of the document's choosing. In fixed versions external data links are updated under the same link update control as other links in a spreadsheet.

Weakness: CWE-918 (Server-Side Request Forgery), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

Upgrade to a fixed version.

## Is CVE-2026-63267 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-63267 is a medium-severity server-side request forgery 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-63267 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-63267/ (Markdown: https://insights.sbomify.com/CVE-2026-63267/index.md)
```

## Sources

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

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