Vulnerability in valkey (CVE-2026-27623)
Summary
Vulnerability in valkey (CVE-2026-27623). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 9.0.3 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-27623 has been found in valkey.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade valkey to 9.0.3 or later.
If unsure, ask your IT team or search "valkey CVE-2026-27623" on the vendor's site.
CVE-2026-27623 (valkey) — CWE-20 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 9.0.3 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in valkey.
Check the vendor advisory for the affected versions of valkey.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 9.0.3.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'valkey' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'valkey' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
valkeyを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade valkey to 9.0.3ステージング環境で 9.0.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- Alpine Linux ALPINE-CVE-2026-27623 valkey Fixed in: 9.0.3-r0
References
- advisory github.com
- advisory access.redhat.com
- advisory nvd.nist.gov
- advisory github.com
- report bugzilla.redhat.com
- web security.access.redhat.com