---
id: "CVE-2026-116124"
kind: "vulnerability"
aliases: ["CVE-2026-116124"]
title: "GNOME libgsf: heap overflow in OLE2 parser lets remote files corrupt memory"
severity: "high"
cvss: 7.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["document-processing", "gnome", "libgsf", "package", "self-hosted"]
not_affected_if: ["no-libgsf-installed", "trusted-files-only"]
published_at: "2026-10-26T07:17:09+00:00"
first_seen_at: "2026-10-26T07:28:50+00:00"
updated_at: "2026-10-26T07:29:54+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-116124", "first_seen_at": "2026-10-26T07:28:50+00:00"}]
---

# GNOME libgsf: heap overflow in OLE2 parser lets remote files corrupt memory

GNOME libgsf up to 1.14.60 has a heap-based buffer overflow in the OLE2 parser function ole_info_read_metabat, which handles crafted Office-style compound files. An attacker who can get a malicious file opened by an application using libgsf can corrupt memory, which may lead to code execution.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed libgsf version with `pkg-config --modversion libgsf-1` and compare it to `1.14.60`.
- Find applications that link libgsf, for example with `ldd` on the binaries that parse OLE or Office files.

## Fix

- Move libgsf past `1.14.60` to a release that includes upstream commit `a8e25560b74f84c3f86df6ca0ac59195fa5af68a`.
- Until patched, avoid opening untrusted OLE2 or Office files with applications that use libgsf.

## Timeline

- 2026-10-26T07:28:50+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-116124

## From the sources

A security vulnerability has been detected in GNOME libgsf up to 1.14.60. The impacted element is the function ole_info_read_metabat of the file gsf/gsf-infile-msole.c of the component OLE2 Parser. The manipulation leads to heap-based buffer overflow. The attack can be initiated remotely. The identifier of the patch is a8e25560b74f84c3f86df6ca0ac59195fa5af68a. It is recommended to apply a patch to fix this issue.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_