dbcve.org
ValkeyApplication · Lfprojects

CVE-2026-27623

HIGH · 7.5 CVSS v3.1 Published 2026-02-23
Fix available
A fix is available. Upgrade to 9.0.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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. Starting in version 9.0.0 and prior to version 9.0.3, a malicious actor with network access to Valkey can cause the system to abort by triggering an assertion. When processing incoming requests, the Valkey system does not properly reset the networking state after processing an empty request. A malicious actor can then send a request that the server incorrectly identifies as breaking server side invariants, which results in the server shutting down. Version 9.0.3 fixes the issue. As an additional mitigation, properly isolate Valkey deployments so that only trusted users have access.

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 9.0.0 through 9.0.2, the networking state is not properly reset after processing an empty request. An attacker with network access can send specially crafted requests that the server misinterprets as invariant violations, triggering an assertion failure that causes the server to abort and shut down.

MitigationUpgrade Valkey to version 9.0.3 or later. Additionally, restrict network access to Valkey instances so only trusted users can connect.

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:>= 9.0.0, < 9.0.3

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Determine installed Valkey version
    Run `valkey-server --version` or `valkey-cli --version` to retrieve the version string
    Affected if The version shown is 9.0.0, 9.0.1, or 9.0.2 (falling within >= 9.0.0 and < 9.0.3)
  2. Check network binding configuration
    Examine the Valkey configuration file (valkey.conf) for the `bind` directive, or run `valkey-cli CONFIG GET bind` to see which network interfaces the server listens on
    Affected if The bind address allows connections from untrusted network segments (e.g., 0.0.0.0 or publicly routable IPs rather than localhost or trusted internal networks)
  3. Verify server is running and accepting connections
    Run `valkey-cli PING` to confirm the server is active and accessible over the network
    Affected if The server responds to commands, meaning it is actively processing network requests and could receive the malicious crafted empty requests

You are affected if you are running Valkey version 9.0.0, 9.0.1, or 9.0.3 and the server is accessible over a network where untrusted users can send requests.

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 9.0.3 or later
Fixed in 9.0.3
Interim mitigation

Upgrade Valkey to version 9.0.3 or later. Additionally, restrict network access to Valkey instances so only trusted users can connect.

Recommended fix High confidence

Valkey 9.0.3 or later

  1. 1. Identify the current running Valkey version using 'valkey-cli INFO server' or 'valkey-server --version'
  2. 2. Create a full backup of Valkey data and configuration files before upgrading
  3. 3. Stop the Valkey service gracefully using 'systemctl stop valkey' or 'valkey-cli SHUTDOWN'
  4. 4. Upgrade Valkey to version 9.0.3 or later using the package manager (e.g., 'apt-get update && apt-get install valkey' or 'yum update valkey')
  5. 5. Verify the upgraded version with 'valkey-server --version' to confirm 9.0.3 or higher is installed
  6. 6. Start the Valkey service using 'systemctl start valkey'
  7. 7. Test that the server is operational with 'valkey-cli PING'
  8. 8. As an additional mitigation, ensure Valkey deployments are network-isolated so only trusted users have access (e.g., firewall rules, bind to localhost, or VPN)
Caveat Minor version upgrade within 9.x series; backward compatibility expected for standard key-value operations

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

Fix this in Valkey Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27623 — 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-2026-27623 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