dbcve.org
RedisDatabase / datastore

CVE-2025-27151

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-29
Fix available
A fix is available. Upgrade to 7.2.9 / 7.4.4 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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. In versions starting from 7.0.0 to before 8.0.2, a stack-based buffer overflow exists in redis-check-aof due to the use of memcpy with strlen(filepath) when copying a user-supplied file path into a fixed-size stack buffer. This allows an attacker to overflow the stack and potentially achieve code execution. This issue has been patched in version 8.0.2.

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

A stack-based buffer overflow vulnerability exists in redis-check-aof for Redis versions 7.0.0 through 8.0.1. The flaw stems from using memcpy with strlen(filepath) to copy a user-supplied file path into a fixed-size stack buffer without proper bounds checking, allowing an attacker to overflow the stack and potentially achieve code execution.

MitigationUpgrade Redis to version 8.0.2 or later to patch the vulnerability. If immediate upgrade is not possible, restrict access to redis-check-aof and avoid processing untrusted AOF files.

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:>= 7.0.0, < 7.2.9>= 7.4.0, < 7.4.4>= 8.0.0, < 8.0.2

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Determine installed Redis version
    Run 'redis-server --version' or 'redis-cli INFO server' to obtain the Redis version number
    Affected if The version falls within 7.0.0 to 7.2.8, 7.4.0 to 7.4.3, or 8.0.0 to 8.0.1
  2. Locate redis-check-aof binary
    Run 'which redis-check-aof' or check common paths like /usr/bin/redis-check-aof to confirm the tool is present on the system
    Affected if redis-check-aof exists and is executable on the host
  3. Assess AOF file processing exposure
    Review scripts, cron jobs, or automated processes that invoke redis-check-aof, and identify whether they process AOF files from untrusted or user-controlled sources
    Affected if redis-check-aof is used to process AOF files that originate from untrusted or external sources without validation

You are affected if your Redis version is 7.0.0-7.2.8, 7.4.0-7.4.3, or 8.0.0-8.0.1 AND you use redis-check-aof to process AOF files from untrusted sources.

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 7.2.9 / 7.4.4 / 8.0.2 or later
Fixed in 7.2.97.4.48.0.2
Vendor patch github.com →
Interim mitigation

Upgrade Redis to version 8.0.2 or later to patch the vulnerability. If immediate upgrade is not possible, restrict access to redis-check-aof and avoid processing untrusted AOF files.

Recommended fix High confidence

8.0.2 or later (recommended: latest 8.0.x stable release)

  1. 1. Identify the current Redis version installed using `redis-server --version` or `redis-cli INFO server`
  2. 2. Based on your current version branch, plan upgrade to one of the fixed versions: 7.2.9+, 7.4.4+, or 8.0.2+
  3. 3. Before upgrading, backup your Redis data and configuration files (`redis-cli BGSAVE` and copy redis.conf)
  4. 4. For package managers: run `apt update && apt install redis-server` (Debian/Ubuntu) or `yum update redis` (RHEL/CentOS)
  5. 5. Alternatively, download the specific version from https://redis.io/downloads/ and upgrade manually
  6. 6. After upgrade, verify the new version with `redis-server --version`
  7. 7. Restart the Redis service to ensure the patched binary is running: `systemctl restart redis-server` or `service redis-server restart`
  8. 8. Test that redis-check-aof works correctly with `redis-check-aof --check <your-aof-file>`
Caveat Redis 8.0 includes new features and some configuration changes; review release notes for breaking changes between 7.x and 8.0

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

Fix this in Redis Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
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,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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