Skip to main content
Menu
CVEs

CVE

The Document Foundation LibreOffice code execution via crafted web query files

Affects LibreOffice 26.2 before 26.2.7 and 26.8 before 26.8.2 when a crafted web query file is given on the command line. Fixed in 26.2.7 and 26.8.2.

CVE-2026-108169EUVD-2026-126514GHSA-WRQJ-4FMF-MWFM

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

7.3HighCNA
Exploited
No known exploitation
Fix
Fixed in < 26.2.7, < 26.8.2
Who is exposed
Specific setups only

Do first: Check whether your setup matches what the bug needs. The web query file is given on LibreOffice's command line, such as when a file manager or another program opens it with LibreOffice.

Published
Last modified
Reference
Last checked
13/100 · provisional
Specific setups only
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: no
  • Technical impact: total

Summary

LibreOffice can be tricked into running code through a crafted web query file (.iqy) when that file is opened from the command line, for example by a file manager. The attacker needs a local way to get the file opened, and the victim must take an action such as opening it, with no login required.

Original description

LibreOffice can open a web query file (.iqy), which names a web page to import into a spreadsheet, when the file is given on its command line, for example when a file manager or another program opens the file with LibreOffice. The address in such a file was used without the checks that apply to an address given on the command line directly, so a crafted file could make LibreOffice do something other than open a web page, up to running code. In fixed versions only an http or https address is taken from a web query file.

cve.now Index

13Pcve.now Index 13 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure5/25Specific setups only
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity8.3/10CVSS 7.3, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 63 if added to CISA KEV
  • Would score about 58 if CISA's SSVC rates exploitation active
  • Would score about 23 if CISA's SSVC rates it automatable

What to do

  • Check whether your setup matches what the bug needs.

    The web query file is given on LibreOffice's command line, such as when a file manager or another program opens it with LibreOffice.
  • Upgrade to a fixed version: < 26.2.7, < 26.8.2.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-108169 (Code execution through web query files given on the command line), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-108169 (entry last updated 2026-11-17):
Affected:
- The Document Foundation LibreOffice: from 26.2, fixed in < 26.2.7; from 26.8, fixed in < 26.8.2
Fixed versions: < 26.2.7, < 26.8.2.
Conditions (all must be true for the bug to be hit):
- The web query file is given on LibreOffice's command line, such as when a file manager or another program opens it with LibreOffice. (source: https://www.libreoffice.org/security/#cve-2026-108169)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, no login, a user action.
CISA KEV: CVE-2026-108169 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-108169 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.libreoffice.org/about-us/security/advisories/cve-2026-108169
- https://www.libreoffice.org/security/#cve-2026-108169
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-108169
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-108169"}.

Timeline

  1. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: total

  2. CVE published
  3. First seen by cve.now1 day
  4. Record last updated

Affected versions

  • The Document Foundation LibreOffice

    From 26.2 · fixed in < 26.2.7; From 26.8 · fixed in < 26.8.2

Evidence 3

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Link

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-108169

Is CVE-2026-108169 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

A crafted web query file can make LibreOffice do something other than open a web page, up to running code. The problem occurs when the file is given on LibreOffice's command line, such as when a file manager or another program opens it with LibreOffice.Source: libreoffice.org

Which versions are affected by CVE-2026-108169?

LibreOffice: from 26.2 before < 26.2.7; from 26.8 before < 26.8.2.Source: cve.now feed data

Am I affected, and how do I check?

Versions 26.2 before 26.2.7 and 26.8 before 26.8.2 are in the affected ranges. The issue requires the web query file to be given on the command line, so check the installed LibreOffice version number and how files are opened.Source: libreoffice.org

How do I fix CVE-2026-108169?

Upgrade to LibreOffice 26.2.7 or later on the 26.2 line, or to 26.8.2 or later on the 26.8 line.Source: libreoffice.org