CVE-2025-67733: Valkey Affected by RESP Protocol Injection via Lua error_reply
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.
Security readout for executives and security teams
Plain-English summary
Valkey can let an authenticated user corrupt the response stream seen on the same client connection by abusing Lua script error handling. This can cause tampered or confusing data responses and service disruption. The provided sources name fixed Valkey releases, so exposed systems should be updated promptly.
Executive priority
Treat this as a high-priority patching item for Valkey-backed services, especially shared environments. The issue can affect data integrity seen by clients and service availability, but provided sources do not establish active exploitation.
Technical view
Before Valkey 9.0.2, 8.1.6, 8.0.7, and 7.2.12, Lua error_reply handling mishandles null characters, enabling RESP protocol injection. The CVSS 3.1 score is 8.5 with low complexity, required low privileges, changed scope, low integrity impact, and high availability impact.
Likely exposure
Exposure is likely where Valkey runs below the fixed versions and permits users or applications to execute scripting commands. Risk is higher in shared, multi-tenant, or connection-pooled environments where response stream corruption could affect other users sharing a connection.
Exploitation context
The provided bundle does not show CISA KEV listing or cited evidence of active exploitation. Exploitation requires network access and low privileges, not user interaction. Sources describe impact as injection of arbitrary information into the response stream for the given client.
Researcher notes
Focus validation on version ranges and whether Lua scripting is reachable by low-privileged users. The root issue is improper null character handling in Lua error_reply, mapped to CWE-170 and CWE-74. Avoid assuming cross-client impact beyond the same connection described in sources.
Mitigation direction
Upgrade Valkey to 9.0.2, 8.1.6, 8.0.7, or 7.2.12 or later.
Apply applicable Red Hat errata for Red Hat-packaged Valkey deployments.
Prioritize systems where scripting commands are available to untrusted or tenant users.
Review vendor guidance before applying compensating controls not named in advisories.
Validation and detection
Inventory Valkey instances and record exact major and patch versions.
Identify deployments below 7.2.12, 8.0.7, 8.1.6, or 9.0.2.
Review whether applications expose scripting commands to low-privileged users.
Check Red Hat advisory status for affected packaged environments.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-170: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-170 · source CWE mapping
Improper Null Termination
Improper Null Termination represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.