CyberSecBulletin
CVE-2025-67733NVD status: Modified

valkey: Improper Neutralization of Special Elements in Output Used by a Downstream Component

CVE-2025-67733 is a high-severity improper neutralization of special elements in output used by a downstream component vulnerability in valkey from Valkey-io, with a CVSS 3.1 base score of 7.1 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, without any action from a user. Affected valkey versions: < 7.2.12; >= 8.0.0, < 8.0.7; >= 8.1.0, < 8.1.6, and others listed below. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.82% chance of exploitation within 30 days, higher than 58% of scored CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Check which version of valkey you run against the affected versions below, and install the vendor's latest release.
  2. Read the advisory on github.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
Valkey-iovalkey< 7.2.12; >= 8.0.0, < 8.0.7; >= 8.1.0, < 8.1.6; >= 9.0.0, < 9.0.2Not stated
Red HatRed Hat Enterprise Linux 10Not specified in the recordNot stated
Red HatRed Hat Enterprise Linux 10.0 Extended Update SupportNot specified in the recordNot stated
Red HatRed Hat Enterprise Linux 9Not specified in the recordNot stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
LowA basic user account is enough.
User interaction
NoneNo action by a victim is required.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
NoneNo data is disclosed.
Integrity
LowLimited modification of data is possible.
Availability
HighThe component can be taken down completely.

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H. Scored by NVD.

Scoring systemScoreSeverityScored by
CVSS 3.18.5HighCNA (github.com)
CVSS 3.17.1HighNVD
CVSS 3.17.1HighCNA

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.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Improper Neutralization of Special Elements in Output Used by a Downstream Component

The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.

How developers prevent this class of flaw

  • Programming languages and supporting technologies might be chosen which are not subject to these issues.
  • Utilize an appropriate mix of allowlist and denylist parsing to filter control-plane syntax from all input.

More Improper Neutralization of Special Elements in Output Used by a Downstream Component vulnerabilities (CWE-74)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in valkey

All valkey vulnerabilities

Recent Improper Neutralization of Special Elements in Output Used by a Downstream Component vulnerabilities

Spotted an error? Tell us.