Cyber Resilience

CVE-2025-67733

Lfprojects Valkey ≤ 7.2.12

Published
23 February 2026
Modified
15 July 2026
Patch / advisory
View advisory
CVSS Score v3.1 8.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/A:H
EPSS Score 0.0059 45th percentile
Risk Priority 60 floored blend · peak EPSS

Summary

CVE-2025-67733 is a high-severity Injection (CWE-74) vulnerability in Lfprojects Valkey. Its CVSS base score is 8.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 45th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-67733 is a vulnerability in Valkey, a distributed key-value database forked from Redis. It affects versions prior to 9.0.2, 8.1.6, 8.0.7, and 7.2.12. The issue arises in the error handling code for Lua scripts, which fails to properly handle null characters. This flaw allows a malicious user to inject arbitrary information into the response stream intended for a specific client.

An attacker requires low privileges (PR:L) to exploit the vulnerability over the network (AV:N) with low attack complexity (AC:L) and no user interaction (UI:N). Successful exploitation results in a scope change (S:C), enabling the injection of tampered or corrupted data that affects other users sharing the same connection. Impacts include low integrity violation (I:L) and high availability disruption (A:H), with a CVSS v3.1 base score of 8.5. The vulnerability is classified under CWE-74.

The official Valkey security advisory (GHSA-p876-p7q5-hv2m) confirms that upgrading to versions 9.0.2, 8.1.6, 8.0.7, or 7.2.12 resolves the error handling issue in Lua scripts. No additional mitigations are specified beyond applying these patched releases.

OWASP Top 10 for Web (2025)

A05:2025 Injection

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-74CWE-170

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1221 Template Injection Stealth
Adversaries may create or modify references in user document templates to conceal malicious code or force authentication attempts.
attack.mitre.org →
T1659 Content Injection Initial Access
Adversaries may gain access and continuously communicate with victims by injecting malicious content into systems through online network traffic.
attack.mitre.org →
T1674 Input Injection Execution
Adversaries may simulate keystrokes on a victim’s computer by various means to perform any type of action on behalf of the user, such as launching the command interpreter using keyboard shortcuts, typing an inline script to be executed,…
attack.mitre.org →
T1059 Command and Scripting Interpreter Execution
Adversaries may abuse command and script interpreters to execute commands, scripts, or binaries.
attack.mitre.org →
T1059.001 PowerShell Execution
Adversaries may abuse PowerShell commands and scripts for execution.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-23749Shared CWE-74
CVE-2023-48835Shared CWE-74
CVE-2023-51939Shared CWE-74
CVE-2023-33242Shared CWE-74
CVE-2023-4157Shared CWE-74
CVE-2024-28191Shared CWE-74
CVE-2022-2992Shared CWE-74
CVE-2023-44373Shared CWE-74
CVE-2020-9757Shared CWE-74
CVE-2024-42914Shared CWE-74

Affected Assets

lfprojects
valkey
≤ 7.2.12 · 8.0.0 — 8.0.7 · 8.1.0 — 8.1.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.2.1
  • V1.2.3
  • V1.2.5
  • V1.2.8

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation can discover missing or incorrect string termination during code review or dynamic analysis.

SI-10 Information Input Validation good match

SI-10 directly requires validation of information inputs to reject malformed or special-element content before it reaches downstream parsers.

SA-15 Development Process, Standards, and Tools partial match

Requiring documented development standards and tools can enforce safe string-handling practices that produce correct null termination.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and output encoding that prevent injection flaws.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development catches injection vulnerabilities before release.

A.8.15 Logging partial match
finds

Logging supports detection of injection attempts but does not prevent the weakness.

A.8.16 Monitoring activities partial match
finds

Monitoring activities can identify active injection attacks after they occur.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates input validation and output encoding that directly prevent injection flaws.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for controls against injection attacks in software design.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce injection surfaces but do not prescribe specific neutralization techniques.

References