cve.bz

CVE-2026-116124 gnome libgsf: Heap-based Buffer Overflow

5.3 mediumEPSS 0.4%

Medium (5.3) in gnome libgsf. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

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

CVSS 3.1

6.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
EPSS
0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 37th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-10-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
CWE-122 Heap-based Buffer Overflow
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-116124 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-116124?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-116124?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-116124 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-116124

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-116124](https://cve.bz/cve/badge/CVE-2026-116124.svg)](https://cve.bz/cve/CVE-2026-116124)

HTML:

<a href="https://cve.bz/cve/CVE-2026-116124"><img src="https://cve.bz/cve/badge/CVE-2026-116124.svg" alt="CVE-2026-116124"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
GNOME libgsf1.14.0
GNOME libgsf1.14.1
GNOME libgsf1.14.2
GNOME libgsf1.14.3
GNOME libgsf1.14.4
GNOME libgsf1.14.5
GNOME libgsf1.14.6
GNOME libgsf1.14.7
GNOME libgsf1.14.8
GNOME libgsf1.14.9
GNOME libgsf1.14.10
GNOME libgsf1.14.11
GNOME libgsf1.14.12
GNOME libgsf1.14.13
GNOME libgsf1.14.14
GNOME libgsf1.14.15
GNOME libgsf1.14.16
GNOME libgsf1.14.17
GNOME libgsf1.14.18
GNOME libgsf1.14.19
GNOME libgsf1.14.20
GNOME libgsf1.14.21
GNOME libgsf1.14.22
GNOME libgsf1.14.23
GNOME libgsf1.14.24
GNOME libgsf1.14.25
GNOME libgsf1.14.26
GNOME libgsf1.14.27
GNOME libgsf1.14.28
GNOME libgsf1.14.29
GNOME libgsf1.14.30
GNOME libgsf1.14.31
GNOME libgsf1.14.32
GNOME libgsf1.14.33
GNOME libgsf1.14.34
GNOME libgsf1.14.35
GNOME libgsf1.14.36
GNOME libgsf1.14.37
GNOME libgsf1.14.38
GNOME libgsf1.14.39
GNOME libgsf1.14.40
GNOME libgsf1.14.41
GNOME libgsf1.14.42
GNOME libgsf1.14.43
GNOME libgsf1.14.44
GNOME libgsf1.14.45
GNOME libgsf1.14.46
GNOME libgsf1.14.47
GNOME libgsf1.14.48
GNOME libgsf1.14.49
GNOME libgsf1.14.50
GNOME libgsf1.14.51
GNOME libgsf1.14.52
GNOME libgsf1.14.53
GNOME libgsf1.14.54
GNOME libgsf1.14.55
GNOME libgsf1.14.56
GNOME libgsf1.14.57
GNOME libgsf1.14.58
GNOME libgsf1.14.59
GNOME libgsf1.14.60

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14libgsfno fix listedDEBIAN-CVE-2026-116124
Ubuntu14.04:LTS, 16.04:LTS, 18.04:LTS and 5 morelibgsfno fix listedUBUNTU-CVE-2026-116124
Azure Linux3libgsfno fix listedAZL-111103

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as an Important impact because successful exploitation allows potential code execution or process termination under the privileges of the executing user. In Red Hat Enterprise Linux, libgsf is utilized by graphical utilities and document processing tools to handle structured storage formats. Exploitation requires a user or backend service to parse an untrusted, maliciously formed OLE2 file, meaning the flaw cannot be triggered without direct file ingestion. The blast radius remains limited to the permissions of the invoking application.

Red Hat's mitigation

Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.

--- CME Mitigation Guidance (2026-11-02) ---

Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.

The highest-value action is to prevent untrusted OLE2 document ingestion by applications and backend services linking libgsf: upgrade to libgsf > 1.14.60 (or the fixed Libgsf builds), which fixes heap-based buffer overflow in ole_info_read_metabat during OLE2 parsing, closing crafted OLE2 document file ingestion. Until patched, this is a concern on Linux systems running applications or automated services processing OLE2 files via libgsf, so restrict ingestion of untrusted or externally sourced OLE2 documents across services and user workflows using libgsf. As a compensating measure, randomize user-space memory layouts via ASLR to hinder predictable heap exploitation, enforce full RELRO and PIE to protect Global Offset Tables and binary mappings, deploy Control Flow Integrity or shadow call stacks to block indirect control-flow hijacking, enable FORTIFY_SOURCE to abort processes on detected buffer overflow conditions, confine document parsing processes within restricted SELinux domains in enforcing mode, and restrict parser process filesystem access using Landlock LSM sandboxing. These controls limit blast radius and contain exploitation, but they do not fix the underlying heap-based buffer overflow — apply the upstream patch to fully remediate.

Highest-impact CME: CME-301 SELinux (Enforcing Mode) (medium)

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10libgsfAffected
Red Hat Enterprise Linux 6libgsfNot affected
Red Hat Enterprise Linux 7libgsfAffected
Red Hat Enterprise Linux 8libgsfAffected
Red Hat Enterprise Linux 9libgsfAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-116124.

Attack patterns (CAPEC)

  • CAPEC-92 Forced Integer Overflow Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-119 (12).

References

Check your stackJSON