LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25243: redis-server RESTORE invalid memory access may allow remote code execution

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.

HighCVSS 8.8Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

Redis servers before 8.6.3 can mishandle crafted data sent through the RESTORE command. An attacker must already be authenticated and allowed to run RESTORE, but successful exploitation may let them run code on the Redis server. Treat this as urgent for internet-facing, shared, or broadly accessible Redis deployments.

Executive priority

Prioritize patching within the high-severity remediation window, faster for exposed or multi-user Redis environments. The required authentication lowers broad internet worm risk, but the possible code execution impact is severe.

Technical view

The flaw is improper validation of serialized values in redis-server RESTORE, associated with CWE-122. The published CVSS 3.1 score is 8.8: network exploitable, low complexity, low privileges required, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is likely where Redis versions earlier than 8.6.3 are deployed and ACLs permit users or applications to execute RESTORE. Risk is lower when RESTORE is blocked and Redis is tightly network-restricted.

Exploitation context

The bundle does not cite active exploitation, and KEV is false. The attacker needs valid access plus RESTORE permission, so compromised application credentials, overbroad ACLs, or exposed Redis management paths matter most.

Researcher notes

The strongest evidence is the Redis advisory, release reference, CVE record, and Red Hat tracking. The source bundle does not provide exploit details, proof of active exploitation, or affected managed Redis service statements.

Mitigation direction

  • Upgrade redis-server to version 8.6.3 or a vendor-fixed package.
  • Restrict RESTORE with Redis ACL rules where it is not required.
  • Review Red Hat advisories for applicable distribution packages and errata.
  • Limit Redis access to trusted networks and authenticated clients.
  • Audit privileged Redis users and remove unnecessary command permissions.

Validation and detection

  • Inventory Redis instances and confirm versions are 8.6.3 or vendor-fixed.
  • Check ACLs for users or applications with RESTORE permission.
  • Confirm vendor package status against Red Hat advisories if using Red Hat builds.
  • Review Redis logs and telemetry for unexpected RESTORE use.
  • Identify applications that legitimately require DUMP or RESTORE workflows.
Prepared
Confidence
high
Sources
12

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-122: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-25243 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
High
CVSS
8.8 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
21Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
8.8CVSS 3.1HighCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H2.85.9redhat-SADP
7.7CVSS 4.0HighCVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N——GitHub_M

Vulnerability scoring details

Base CVSS 4.0 score

7.7High
CVSS 4.0 vector shape for CVE-2026-25243Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPredis: RESTORE invalid memory access may allow remote code execution
other:Red Hat severity ratingcvssV3_1
  • 2026-05-05T18:01:12.034Z: Reported to Red Hat.
  • 2026-05-05T16:44:57.306Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
redisredis< 8.6.3Listed
Weakness

CWE details

CWE-122

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-122 · source CWE mapping

Heap-based Buffer Overflow

Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.

Open CWE intelligenceSame-CWE CVEs