# CVE-2025-67733: Valkey Affected by RESP Protocol Injection via Lua error_reply

> Attackers can inject arbitrary data into client responses via Lua script error handling, potentially corrupting or tampering with data returned to other users.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Feb 2026
- **Updated:** 15 Jul 2026
- **Also known as:** ALPINE-CVE-2025-67733, AZL-78317, BELL-CVE-2025-67733, BIT-valkey-2025-67733, DEBIAN-CVE-2025-67733, GHSA-p876-p7q5-hv2m, UBUNTU-CVE-2025-67733, USN-8106-1

## What is CVE-2025-67733?

CVE-2025-67733 is a high-severity vulnerability in valkey-io valkey, published on 23 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Valkey is a distributed key-value database. Prior to versions 9.0.2, 8.1.6, 8.0.7, and 7.2.12, a malicious user can use scripting commands to inject arbitrary information into the response stream for the given client, potentially corrupting or returning tampered data to other users on the same connection. The error handling code for lua scripts does not properly handle null characters. Versions 9.0.2, 8.1.6, 8.0.7, and 7.2.12 fix the issue.

Weakness: CWE-170 (Improper Null Termination), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2025-67733?

1 open source package ship an affected version, including valkey. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `valkey` | Bitnami | All versions | 7.2.12, 8.0.7, 8.1.6, 9.0.2 |

Products: Lfprojects Valkey.

## How do I fix CVE-2025-67733?

Upgrade valkey to a fixed version for your release line: 7.2.12, 8.0.7, 8.1.6 or 9.0.2.

## Is CVE-2025-67733 being exploited?

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

Public exploit code:

- Redis/Valkey RESP Injection PoC (CVE-2025-67733) (github_poc): https://github.com/JYlab/CVE-2025-67733

## Other vulnerabilities in valkey-io valkey

- [CVE-2025-49844](https://insights.sbomify.com/CVE-2025-49844/): Redis Lua Use-After-Free may lead to remote code execution (critical 10.0)
- [CVE-2026-21863](https://insights.sbomify.com/CVE-2026-21863/): Malformed Valkey Cluster bus message can lead to Remote DoS (high 7.5)
- [CVE-2026-27623](https://insights.sbomify.com/CVE-2026-27623/): Valkey has Pre-Authentication DOS from malformed RESP request (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-67733 and fix it if it is affected.

What it is: CVE-2025-67733 is a high-severity vulnerability in valkey-io valkey, published on 23 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-67733 in the wild and no public exploit code.

Affected packages and fixed versions:
- valkey (Bitnami): affected all versions; fixed in 7.2.12, 8.0.7, 8.1.6, 9.0.2

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

## Sources

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

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