dbcve.org
ValkeyApplication · Lfprojects

CVE-2025-67733

HIGH · 7.1 CVSS v3.1 Published 2026-02-23
Fix available
A fix is available. Upgrade to 7.2.12 / 8.0.7 or later.
See remediation →
77/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Valkey versions prior to 9.0.2, 8.1.6, 8.0.7, and 7.2.12, the Lua scripting error handling code fails to properly sanitize null characters in error messages. A malicious authenticated user can exploit this by crafting Lua scripts that inject arbitrary data into the response stream, corrupting or tampering with data returned to other users on the same connection.

MitigationUpgrade Valkey to versions 9.0.2, 8.1.6, 8.0.7, or 7.2.12. If immediate patching is not feasible, restrict Lua script execution to trusted users or consider disabling Lua scripting via configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ValkeyApplication
Affected:< 7.2.12>= 8.0.0, < 8.0.7>= 8.1.0, < 8.1.6>= 9.0.0, < 9.0.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Valkey version
    Run `valkey-cli --version` or `redis-server --version` to identify the installed version
    Affected if The version is less than 7.2.12, or falls between 8.0.0-8.0.6, 8.1.0-8.1.5, or 9.0.0-9.0.1
  2. Verify Lua scripting is enabled
    Run `valkey-cli CONFIG GET enable-lua-scripting` or check the configuration file for `enable-lua-scripting` directive
    Affected if Lua scripting is enabled (value is not 0 or not set to no)
  3. Check Lua time limit configuration
    Run `valkey-cli CONFIG GET lua-time-limit` to confirm Lua execution is permitted
    Affected if Lua execution is permitted (default is 5000ms, a non-zero value indicates Lua scripts can run)
  4. Confirm authenticated user access
    Review access control settings via `valkey-cli CONFIG GET requirepass` and user definitions via `valkey-cli ACL LIST`
    Affected if Authentication is enabled but users with SCRIPT or EXEC permissions exist, as the flaw requires a malicious authenticated user to execute Lua scripts

The environment is affected if Valkey version is in the vulnerable range AND Lua scripting is enabled, allowing a malicious authenticated user to inject data via crafted Lua error messages.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 7.2.12 / 8.0.7 / 8.1.6 or later
Fixed in 7.2.128.0.78.1.6
Interim mitigation

Upgrade Valkey to versions 9.0.2, 8.1.6, 8.0.7, or 7.2.12. If immediate patching is not feasible, restrict Lua script execution to trusted users or consider disabling Lua scripting via configuration.

Recommended fix High confidence

Upgrade to 7.2.12 (for 7.x), 8.0.7 (for 8.0.x), 8.1.6 (for 8.1.x), or 9.0.2 (for 9.x) depending on your current major version branch

  1. 1. Identify the currently installed Valkey version using 'valkey-cli INFO server' or 'redis-cli INFO server'.
  2. 2. Determine which upgrade path applies based on your current major version branch.
  3. 3. For Valkey 7.x users: Upgrade to version 7.2.12 or later.
  4. 4. For Valkey 8.0.x users: Upgrade to version 8.0.7 or later.
  5. 5. For Valkey 8.1.x users: Upgrade to version 8.1.6 or later.
  6. 6. For Valkey 9.x users: Upgrade to version 9.0.2 or later.
  7. 7. Use your package manager or compile from source to install the fixed version.
  8. 8. After upgrade, verify the server starts successfully and test Lua scripting functionality.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Valkey Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-67733 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-67733 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data