# CVE-2026-116612: A flaw was found in GStreamer Editing Services (gst-editing-services).


- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 26 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-116612, GHSA-hq2c-jhr8-9ffr, UBUNTU-CVE-2026-116612

## What is CVE-2026-116612?

CVE-2026-116612 is a high-severity vulnerability in GStreamer project gst-editing-services, published on 26 Oct 2026. 

### Official description

A flaw was found in GStreamer Editing Services (gst-editing-services). A GES project file can embed an arbitrary GStreamer pipeline description as an effect definition. When such a file is loaded, either explicitly by an editing application or automatically by a media player or file-manager thumbnailing service that uses GStreamer autoplugging, the pipeline description is parsed and instantiated without restriction on which elements may be used or which properties may be set. A remote attacker who can deliver a crafted project file to a victim's system can trigger reading or writing of arbitrary local files, issue outbound network requests to attacker-controlled servers, or cause the application to crash. Under certain conditions the file-write capability may be leveraged to achieve code execution.

Weakness: CWE-913 (Improper Control of Dynamically-Managed Code Resources)

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


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

Upgrade to a fixed version.

## Is CVE-2026-116612 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-116612 is a high-severity vulnerability in GStreamer project gst-editing-services, published on 26 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-116612 in the wild and no public exploit code.

Affected product: GStreamer project gst-editing-services. 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-116612/ (Markdown: https://insights.sbomify.com/CVE-2026-116612/index.md)
```

## Sources

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

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