# CVE-2026-116124: GNOME libgsf OLE2 gsf-infile-msole.c ole_info_read_metabat heap-based overflow


- **Severity:** Medium 5.3 (`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/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 26 Oct 2026
- **Updated:** 29 Oct 2026
- **Also known as:** AZL-111103, DEBIAN-CVE-2026-116124, GHSA-gmh9-5j2c-j4q8, UBUNTU-CVE-2026-116124

## What is CVE-2026-116124?

CVE-2026-116124 is a medium-severity vulnerability in GNOME libgsf, published on 26 Oct 2026. 

### Official description

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.

Weakness: CWE-122 (Heap-based Buffer Overflow), CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

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


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

No fix has been published for CVE-2026-116124 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-116124 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116124 is a medium-severity vulnerability in GNOME libgsf, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116124 in the wild and no public exploit code.

Affected product: GNOME libgsf. 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-116124/ (Markdown: https://insights.sbomify.com/CVE-2026-116124/index.md)
```

## Sources

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

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