# CVE-2014-125026: Out-of-bounds write in github.com/cloudflare/golz4

> An out-of-bounds write in the Go LZ4 bindings allows arbitrary code execution when processing untrusted input.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Dec 2022
- **Updated:** 11 Apr 2025
- **Also known as:** GHSA-4wp2-8rm2-jgmh, GO-2020-0022

## What is CVE-2014-125026?

CVE-2014-125026 is a critical memory corruption vulnerability in github.com/cloudflare/golz4, published on 27 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LZ4 bindings use a deprecated C API that is vulnerable to memory corruption, which could lead to arbitrary code execution if called with untrusted user input.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2014-125026?

3 open source packages ship an affected version, including github.com/cloudflare/golz4. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/cloudflare/golz4` | Go | All versions | 0.0.0-20140711154735-199f5f787806 |
| `github.com/cloudflare/golz4` | Go | All versions | 0.0.0-20140711154735-199f5f787806 |
| `github.com/cloudflare/golz4` | Go | All versions | 0.0.0-20140711154735-199f5f787806 |

Products: Cloudflare Golz4.

## How do I fix CVE-2014-125026?

Upgrade github.com/cloudflare/golz4 to 0.0.0-20140711154735-199f5f787806 or later.

## Is CVE-2014-125026 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-125026 and fix it if it is affected.

What it is: CVE-2014-125026 is a critical memory corruption vulnerability in github.com/cloudflare/golz4, published on 27 Dec 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-125026 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/cloudflare/golz4 (Go): affected all versions; fixed in 0.0.0-20140711154735-199f5f787806
- github.com/cloudflare/golz4 (Go): affected all versions; fixed in 0.0.0-20140711154735-199f5f787806
- github.com/cloudflare/golz4 (Go): affected all versions; fixed in 0.0.0-20140711154735-199f5f787806

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-2014-125026/ (Markdown: https://insights.sbomify.com/CVE-2014-125026/index.md)
```

## Sources

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

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