dbcve.org
RedisDatabase / datastore

CVE-2025-49844

CRITICAL · 9.9 CVSS v3.1 Published 2025-10-03
Fix available
A fix is available. Upgrade to 6.2.20 / 7.2.11 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS Remotely reachable Zero-click Patch available

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 open source, in-memory database that persists on disk. Versions 8.2.1 and below allow an authenticated user to use a specially crafted Lua script to manipulate the garbage collector, trigger a use-after-free and potentially lead to remote code execution. The problem exists in all versions of Redis with Lua scripting. This issue is fixed in version 8.2.2. To workaround this issue without patching the redis-server executable is to prevent users from executing Lua scripts. This can be done using ACL to restrict EVAL and EVALSHA commands.

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

Redis versions 8.2.1 and below contain a use-after-free vulnerability in the Lua scripting subsystem where an authenticated user can manipulate the garbage collector through a specially crafted Lua script to achieve remote code execution. The vulnerability affects all Redis deployments with Lua scripting enabled.

MitigationPrimary remediation is to upgrade Redis to version 8.2.2. Alternatively, if upgrading is not immediately feasible, use Redis ACLs to restrict or disable the EVAL and EVALSHA commands to prevent Lua script execution.

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:< 6.2.20>= 7.0, < 7.2.11>= 7.4.0, < 7.4.6>= 8.0.0, < 8.0.4>= 8.2.0, < 8.2.2
ValkeyApplication
Affected:< 7.2.11>= 8.0.0, < 8.0.6>= 8.1.0, < 8.1.4

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/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 or Valkey version
    Run `redis-server --version` or `redis-cli INFO server` and look for the `redis_version` field
    Affected if The version falls within any of these ranges: Redis < 6.2.20, >= 7.0 < 7.2.11, >= 7.4.0 < 7.4.6, >= 8.0.0 < 8.0.4, >= 8.2.0 < 8.2.2; or Valkey < 7.2.11, >= 8.0.0 < 8.0.6, >= 8.1.0 < 8.1.4
  2. Verify Lua scripting is enabled
    Run `redis-cli CONFIG GET lua-time-limit` - if it returns a value, Lua scripting is enabled; or try running `redis-cli EVAL 'return 1' 0`
    Affected if Lua scripting is enabled (the command returns a result rather than an error indicating scripting is disabled)
  3. Check if EVAL/EVALSHA commands are accessible to users
    Run `redis-cli ACL LIST` and look for rules containing `eval` or `~eval*` permissions; or run `redis-cli COMMAND INFO EVAL` to check command availability
    Affected if Users with access to the server have permissions to run EVAL or EVALSHA commands (no restrictions on these commands in ACL rules)

You are affected if your Redis or Valkey version is within the affected ranges AND Lua scripting is enabled AND users can execute EVAL/EVALSHA commands.

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 6.2.20 / 7.2.11 / 7.4.6 or later
Fixed in 6.2.207.2.117.4.6
Vendor patch github.com →
Interim mitigation

Primary remediation is to upgrade Redis to version 8.2.2. Alternatively, if upgrading is not immediately feasible, use Redis ACLs to restrict or disable the EVAL and EVALSHA commands to prevent Lua script execution.

Recommended fix High confidence

Redis: 8.2.2 (or latest 8.2.x); Valkey: 8.1.4 (or latest 8.1.x) - select the latest patch version for your specific release branch

  1. 1. Identify the current Redis/Valkey version in use by running 'redis-server --version' or 'valkey-server --version'
  2. 2. Determine which release branch your current version belongs to (6.2.x, 7.0.x, 7.2.x, 7.4.x, or 8.0.x-8.2.x)
  3. 3. For Redis: upgrade to the latest version in your branch: 6.2.20, 7.2.11, 7.4.6, or 8.2.2 (or later) depending on your branch
  4. 4. For Valkey: upgrade to the latest version in your branch: 7.2.11, 8.0.6, or 8.1.4 (or later) depending on your branch
  5. 5. Download the appropriate version from the official Redis (redis.io) or Valkey (valkey.io) download page
  6. 6. Stop the Redis/Valkey service: 'systemctl stop redis' or 'systemctl stop valkey'
  7. 7. Install the new version using your system's package manager or compile from source
  8. 8. Start the service: 'systemctl start redis' or 'systemctl start valkey'
Caveat Upgrading across major release branches (e.g., 6.2 to 7.0 or 7.x to 8.x) may introduce compatibility changes; review Redis/Valkey release notes for breaking changes and migration considerations before upgrading

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

Fix this in Redis Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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