dbcve.org
RedisDatabase / datastore

CVE-2026-25243

HIGH · 8.8 CVSS v3.1 Published 2026-05-05
Fix available
A fix is available. Upgrade to 8.6.3 or later.
See remediation →
94/100
Remediation priority · Urgent
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
Redis is an in-memory data structure store. In versions of redis-server up to 8.6.3, the RESTORE command does not properly validate serialized values. An authenticated attacker with permission to execute RESTORE can supply a crafted serialized payload that triggers invalid memory access and may lead to remote code execution. A workaround is to restrict access to the RESTORE command with ACL rules. This is patched in version 8.6.3.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 3w ago

Surfaced from public web coverage — external links open in a new tab.

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

The RESTORE command in Redis versions up to 8.6.3 fails to properly validate serialized values during deserialization. An authenticated attacker with RESTORE command permissions can supply a crafted serialized payload that triggers invalid memory access, potentially enabling remote code execution.

MitigationUpgrade Redis server to version 8.6.3 or later, or immediately restrict access to the RESTORE command using ACL rules as a compensating control until patching is feasible.

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
RedisDatabase / datastore
Affected:< 8.6.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 installed Redis version
    Run `redis-cli INFO server` or `redis-cli INFO | grep redis_version` to retrieve the server version
    Affected if The version shown is less than 8.6.3 (for example, 8.6.2, 8.5.x, or earlier)
  2. Verify RESTORE command is available
    Run `redis-cli COMMAND INFO RESTORE` to confirm the command exists in the deployment
    Affected if The command returns information indicating RESTORE is loaded and accessible
  3. Identify users or clients with RESTORE permission
    Run `redis-cli ACL LIST` to list all ACL users and their permissions, then search for users that include the `restore` or `+@restore` permission
    Affected if Any ACL user account has RESTORE command permissions granted (either explicitly or via a category that includes it)
  4. Confirm external access or untrusted user context
    Review ACL rules or application configuration to determine if RESTORE-capable accounts are accessible to authenticated but untrusted users or external clients
    Affected if The RESTORE permission is granted to users who are not fully trusted or who authenticate from untrusted network contexts

You are affected if your Redis version is below 8.6.3 AND any authenticated user or application account has RESTORE command permissions that could be exploited by an attacker.

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

Upgrade Redis server to version 8.6.3 or later, or immediately restrict access to the RESTORE command using ACL rules as a compensating control until patching is feasible.

Recommended fix High confidence

8.6.3

  1. 1. Backup your Redis data and configuration files before upgrading.
  2. 2. Check your current Redis version using: `redis-server --version`
  3. 3. Upgrade Redis to version 8.6.3 or later. For example, using your package manager or compiling from source.
  4. 4. Verify the upgrade was successful by running: `redis-server --version`
  5. 5. Restart the Redis service to apply the new version.
  6. 6. (Optional security hardening) Add an ACL rule to restrict RESTORE command access for additional defense-in-depth, e.g., `ACL SETUSER readonlyuser -@all +@read +@write -restore`

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

Fix this in Redis Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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