# CVE-2026-115207: Patch: filename validation bypass in reversal fallback allows file creation outside the working directory


- **Severity:** Medium 5.5 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 22 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-115207, ECHO-63dc-00f6-c1c4, GHSA-m74w-h57v-xv36, OESA-2026-4617, OESA-2026-4618, OESA-2026-4619, OESA-2026-4620, UBUNTU-CVE-2026-115207, openSUSE-SU-2026:12302-1

## What is CVE-2026-115207?

CVE-2026-115207 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 22 Oct 2026. 

### Official description

A flaw was found in GNU patch. An attacker can achieve arbitrary file creation outside the intended working directory by enticing a user or automated workflow to apply a specially crafted patch file. Due to missing validation during automatic patch reversal, absolute file paths in patch headers are accepted rather than rejected. Consequently, the utility can create files in arbitrary locations with the permissions of the executing user.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `patch` | openSUSE:Tumbleweed | All versions | 2.8.1-1.1 |

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

Upgrade to a fixed version.

## Is CVE-2026-115207 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-115207 is a medium-severity vulnerability in Red Hat Enterprise Linux 10, published on 22 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-115207 in the wild and no public exploit code.

Affected product: Red Hat Enterprise Linux 10. 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-115207/ (Markdown: https://insights.sbomify.com/CVE-2026-115207/index.md)
```

## Sources

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

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