BlackTreeCVE Intelligence
← Back to the CVE catalogue
Full vulnerability report · 2026
CVE-2026-25589High confidence

RedisBloom RESTORE invalid memory access may allow remote code execution

RedisBloom · RedisBloom

Official source article: GitHub GHSA-7862-34PW-44WV ↗. Check the applicable product and release in the original source.

7.7HighCVSS 4.0
Recommended action
Patch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
R
Operational reassessment

Published severity in operational context

Open reassessment dashboard →
Published severityHighOperational priority:High, unchanged from published severity.unchanged

Evidence used

  • No CISA KEV confirmation is currently recorded.
  • EPSS is 0.81% for the current model date.

Compensating controls

  • Validate the affected product branch and deploy the verified fixed release.
  • Restrict the affected network interface to trusted sources where business-safe.
  • Monitor vendor guidance and exploitation sources for a material change.

Verification

  1. Confirm that the asset runs RedisBloom RedisBloom and falls inside the recorded affected range.
  2. Verify the installed build against the product-specific fixed version after deployment.
  3. Validate exposure, authentication requirements and compensating controls in the actual environment.
  4. Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Mitigation target: Within 30 daysRemediation target: Within 180 days

This automated reassessment organises public evidence. It does not know asset exposure, business impact or control effectiveness and does not replace CVSS or a human risk decision.

Cross-source reconciliation

Remediation availability differs by product scope

Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Distribution package intelligence

Release-specific package status

ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.

1 package state
Repository candidate not checked

A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.

Distribution releaseSource packageVendor stateFixed versionEvidence
Ubuntu 24.04 LTSnoble · standard archiveredisUnder evaluationCanonical reports that the package might be affected and still needs evaluation or fixing.Not published in this feedCanonical Ubuntu Security ↗Source updated 5 Oct 2026
Direct vendor intelligence

Authoritative vendor CSAF and VEX advisories

Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.

1 current
CVE-2026-25589 · CSAF 2.0 · revision 3 · finalRed Hat Product SecurityRedisBloom: RESTORE invalid memory access may allow remote code execution
1 known affected

The vendor explicitly identifies these products as affected by this CVE.

  • ansible-automation-platform-27/gateway-rhel9 as a component of Red Hat Ansible Automation Platform 2
Summary
A flaw was found in RedisBloom. An authenticated attacker with permission to execute the RESTORE command on a Redis server with the RedisBloom module loaded can supply a crafted serialized payload that causes an invalid memory access due to an improper validation of serialized values processed through the Redis RESTORE command. This vulnerability can lead to remote code execution.
Remediation
To mitigate this vulnerability, restrict the execution privileges of the RESTORE command exclusively to highly trusted and administrative users by using the appropriate ACL rules.
Optional official sources

National CERT insights
?CERT means Computer Emergency Response Team; CSIRT is the closely related term Computer Security Incident Response Team.

Choose official national sources for this report. Each advisory shows its original language. Your selection is remembered on this device and included in shared links.

Official European source

ENISA European Vulnerability Database

Official EUVD identifiers, advisory evidence and known-exploited context. Missing fields are not treated as evidence of low risk.

1 current
ENISA EUVD identifier

EUVD-2026-27414

No EUVD known-exploited evidence

ENISA has published the identifier mapping but no EUVD description has been stored yet.

EUVD state
Present in the current official mapping
Known exploitation
Not present in the current ENISA EUVD known-exploited dataset. This is not proof of no exploitation.
ENISA score
Not supplied in the stored EUVD record
Advisory evidence
No linked advisory details stored yet
Recommended actionPatch only the product branches with a verified fix

High technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 1 structured product or package state remain unresolved. Apply remediation only to the exact product branch confirmed by its source.

Fix availability varies by product
01

What, why and how

RedisBloom is a probabilistic data structures module for Redis. In all versions of RedisBloom before 2.8.20, the module does not properly validate serialized values processed through the Redis RESTORE command. An authenticated attacker with permission to execute RESTORE on a server with the RedisBloom module loaded 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 issue is fixed in version 2.8.20.

What

RedisBloom is a probabilistic data structures module for Redis. In all versions of RedisBloom before 2.8.20, the module does not properly validate serialized values processed through the Redis RESTORE command. An authenticated attacker with permission to execute RESTORE on a server with the RedisBloom module loaded 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 issue is fixed in version 2.8.20.

Why

A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.

What

RedisBloom is a probabilistic data structures module for Redis. In all versions of RedisBloom before 2.8.20, the module does not properly validate serialized values processed through the Redis RESTORE command. An authenticated attacker with permission to execute RESTORE on a server with the RedisBloom module loaded 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 issue is fixed in version 2.8.20.

Why

A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

How

An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.

02

Exploit reality and attack path

CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.

Observed exploitation
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
No confirmed evidence

No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.

Public PoC / exploit material
?Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.
None recorded

No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.

Likely attack path
a network path → Heap-based Buffer Overflow → execute code or commands in the affected security context
Attack surface
Network
Privileges required
Low: a basic authenticated account is required
User interaction
None
Attack complexity
High: exploitation depends on specific conditions
Security boundary
Not a CVSS 4.0 base metric
Weakness
?CWE means Common Weakness Enumeration: a standard category for the underlying weakness.
CWE-122 ↗

CWE-122: Heap-based Buffer Overflow. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().

CVSS vector
?CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity.
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

Common Vulnerability Scoring System 4.0: the compact vector below is decoded into plain language.

AVNetworkAttack vector: The vulnerable component can be reached over a network.ACHighAttack complexity: Successful exploitation depends on specific conditions outside the attacker's direct control.ATNoneAttack requirements: No additional deployment or execution condition is required.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.VCHighVulnerable-system confidentiality: A successful attack can cause a major loss.VIHighVulnerable-system integrity: A successful attack can cause a major loss.VAHighVulnerable-system availability: A successful attack can cause a major loss.SCNoneSubsequent-system confidentiality: No direct loss is represented by this metric.SINoneSubsequent-system integrity: No direct loss is represented by this metric.SANoneSubsequent-system availability: No direct loss is represented by this metric.
Post-exploitation / living off the land
After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
NetworkRemote code executionCWE-122
A

Official authority intelligence

Only matched European and national findings are included. Language selectors and unavailable sources are omitted.

BSI · German · WID-SEC-2026-1370Redis: Mehrere Schwachstellen ermöglichen Ausführen von beliebigem Programmcode

Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in Redis ausnutzen, um beliebigen Programmcode.

Official advisory ↗
Cyber Security Agency of Singapore · English · CSA-SB-20260506Security Bulletin 06 May 2026

The Cyber Security Agency of Singapore included this CVE in its official Security Bulletin 06 May 2026, published on 6 May 2026. Open the linked bulletin for the product, severity and reference information published in that issue.

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-1249Multiples vulnérabilités dans les produits VMware

ecord?id=CVE-2026-18938 Référence CVE CVE-2026-19032 https://www.cve.org/CVERecord?id=CVE-2026-19032 Référence CVE CVE-2026-19487 https://www.cve.org/CVERecord?id=CVE-2026-19487 Référence CVE CVE-2026-19542 https://www.cve.org/CVERecord?id=CVE-2026-19542 Référence CVE CVE-2026-1965 https://www.cve.org/CVERecord?id=CVE-2026-1965 Référence CVE CVE-2026-19672 https://www.cve.org/CVERecord?id=CVE-2026-19672 Référence CVE CVE-2026-2303 https://www.cve.org/CVERecord?id=CVE-2026-2303 Référence CVE CVE-2026-24051 https://www.cve.org/CVERecord?id=CVE-2026-24051 Référence CVE CVE-2026-25588 https://www.cve.org/CVERecord?id=CVE-2026-25588 Référence CVE CVE-2026-25589 https://www.cve.org/CVERecord?id=CVE-2026-25589 Référence CVE CVE-2026-25679 https://www.cve.org/CVERecord?id=CVE-2026-25679 Référence CVE CVE-2026-25680 https://www.cve.org/CVERecord?id=CVE-2026-25680 Référence CVE CVE-2026-27137 https://www.cve.org/CVERecord?id=CVE-2026-27137 Référence CVE CVE-2026-27138 https://www.cve.org/CVERecord?id=CVE-2026-27138 Référence CVE CVE-2026-27139 https://www.cve.org/CVERecord?id=CVE-2026-27139 Référence CVE CVE-2026-27140 https://www.cve.org/CVERecord?id=CVE-2026-27140 Référence CVE CVE-2026-27142 https://www.cve.org/CVERecord?id=CVE-2026-27142 Référence CVE CVE-2026-27143 https://www.cve.org/CVERecord?id=

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0962Multiples vulnérabilités dans les produits Tenable

rd?id=CVE-2026-2006 Référence CVE CVE-2026-22795 https://www.cve.org/CVERecord?id=CVE-2026-22795 Référence CVE CVE-2026-22796 https://www.cve.org/CVERecord?id=CVE-2026-22796 Référence CVE CVE-2026-23479 https://www.cve.org/CVERecord?id=CVE-2026-23479 Référence CVE CVE-2026-23631 https://www.cve.org/CVERecord?id=CVE-2026-23631 Référence CVE CVE-2026-23918 https://www.cve.org/CVERecord?id=CVE-2026-23918 Référence CVE CVE-2026-24072 https://www.cve.org/CVERecord?id=CVE-2026-24072 Référence CVE CVE-2026-25243 https://www.cve.org/CVERecord?id=CVE-2026-25243 Référence CVE CVE-2026-25588 https://www.cve.org/CVERecord?id=CVE-2026-25588 Référence CVE CVE-2026-25589 https://www.cve.org/CVERecord?id=CVE-2026-25589 Référence CVE CVE-2026-33523 https://www.cve.org/CVERecord?id=CVE-2026-33523 Référence CVE CVE-2026-33857 https://www.cve.org/CVERecord?id=CVE-2026-33857 Référence CVE CVE-2026-34032 https://www.cve.org/CVERecord?id=CVE-2026-34032 Référence CVE CVE-2026-34059 https://www.cve.org/CVERecord?id=CVE-2026-34059 Référence CVE CVE-2026-42371 https://www.cve.org/CVERecord?id=CVE-2026-42371 Référence CVE CVE-2026-6104 https://www.cve.org/CVERecord?id=CVE-2026-6104 Référence CVE CVE-2026-6472 https://www.cve.org/CVERecord?id=CVE-2026-6472 Référence CVE CVE-2026-6473 https://www.cve.org/CVERecord?id=CVE-2

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0905Multiples vulnérabilités dans Tenable Security Center

rd?id=CVE-2026-2006 Référence CVE CVE-2026-22795 https://www.cve.org/CVERecord?id=CVE-2026-22795 Référence CVE CVE-2026-22796 https://www.cve.org/CVERecord?id=CVE-2026-22796 Référence CVE CVE-2026-23479 https://www.cve.org/CVERecord?id=CVE-2026-23479 Référence CVE CVE-2026-23631 https://www.cve.org/CVERecord?id=CVE-2026-23631 Référence CVE CVE-2026-23918 https://www.cve.org/CVERecord?id=CVE-2026-23918 Référence CVE CVE-2026-24072 https://www.cve.org/CVERecord?id=CVE-2026-24072 Référence CVE CVE-2026-25243 https://www.cve.org/CVERecord?id=CVE-2026-25243 Référence CVE CVE-2026-25588 https://www.cve.org/CVERecord?id=CVE-2026-25588 Référence CVE CVE-2026-25589 https://www.cve.org/CVERecord?id=CVE-2026-25589 Référence CVE CVE-2026-33523 https://www.cve.org/CVERecord?id=CVE-2026-33523 Référence CVE CVE-2026-33857 https://www.cve.org/CVERecord?id=CVE-2026-33857 Référence CVE CVE-2026-34032 https://www.cve.org/CVERecord?id=CVE-2026-34032 Référence CVE CVE-2026-34059 https://www.cve.org/CVERecord?id=CVE-2026-34059 Référence CVE CVE-2026-42371 https://www.cve.org/CVERecord?id=CVE-2026-42371 Référence CVE CVE-2026-6104 https://www.cve.org/CVERecord?id=CVE-2026-6104 Référence CVE CVE-2026-6472 https://www.cve.org/CVERecord?id=CVE-2026-6472 Référence CVE CVE-2026-6473 https://www.cve.org/CVERecord?id=CVE-2

Official advisory ↗
CERT-FR · French · CERTFR-2026-AVI-0901Multiples vulnérabilités dans les produits IBM

ecord?id=CVE-2026-23631 Référence CVE CVE-2026-23745 https://www.cve.org/CVERecord?id=CVE-2026-23745 Référence CVE CVE-2026-23865 https://www.cve.org/CVERecord?id=CVE-2026-23865 Référence CVE CVE-2026-2391 https://www.cve.org/CVERecord?id=CVE-2026-2391 Référence CVE CVE-2026-23950 https://www.cve.org/CVERecord?id=CVE-2026-23950 Référence CVE CVE-2026-24051 https://www.cve.org/CVERecord?id=CVE-2026-24051 Référence CVE CVE-2026-24842 https://www.cve.org/CVERecord?id=CVE-2026-24842 Référence CVE CVE-2026-2492 https://www.cve.org/CVERecord?id=CVE-2026-2492 Référence CVE CVE-2026-25243 https://www.cve.org/CVERecord?id=CVE-2026-25243 Référence CVE CVE-2026-25589 https://www.cve.org/CVERecord?id=CVE-2026-25589 Référence CVE CVE-2026-25639 https://www.cve.org/CVERecord?id=CVE-2026-25639 Référence CVE CVE-2026-25645 https://www.cve.org/CVERecord?id=CVE-2026-25645 Référence CVE CVE-2026-25680 https://www.cve.org/CVERecord?id=CVE-2026-25680 Référence CVE CVE-2026-25681 https://www.cve.org/CVERecord?id=CVE-2026-25681 Référence CVE CVE-2026-26960 https://www.cve.org/CVERecord?id=CVE-2026-26960 Référence CVE CVE-2026-26996 https://www.cve.org/CVERecord?id=CVE-2026-26996 Référence CVE CVE-2026-27136 https://www.cve.org/CVERecord?id=CVE-2026-27136 Référence CVE CVE-2026-27199 https://www.cve.org/CVERecord?id=

Official advisory ↗
JVN iPedia · Japanese · JVNDB-2026-014455RedisBloomにおけるヒープベースのバッファオーバーフローの脆弱性

RedisBloomはRedis用の確率的データ構造モジュールです。RedisBloomのすべてのバージョン2.8.20以前において、モジュールはRedisのRESTOREコマンドを通じて処理されるシリアライズされた値を適切に検証しません。RedisBloomモジュールがロードされたサーバーでRESTOREを実行する権限を持つ認証済みの攻撃者は、不正なメモリアクセスを引き起こし、リモートコードを実行できる細工されたシリアライズペイロードを提供できます。回避策としては、ACLルールでRESTOREコマンドへのアクセスを制限してください。この問題はバージョン2.8.20で修正されました。

Official advisory ↗
03

Patch and workaround

Operational remediation based on structured source evidence.

Status
?Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change.
Fix availability varies by product
Affected
ansible-automation-platform-27/gateway-rhel9 as a component of Red Hat Ansible Automation Platform 2
Fixed
2.8.20.
Action
Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
Workaround
To mitigate this vulnerability, restrict the execution privileges of the RESTORE command exclusively to highly trusted and administrative users by using the appropriate ACL rules.
04

Evidence and provenance

Published 5 May 2026 · Last source change 5 May 2026, 18:49 UTC · CWE-122 · Heap-based Buffer Overflow

CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source
?The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.
FIRST · tracked since 2026-08-14
European sourceENISA EUVD · EUVD-2026-27414
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD enriched

Core structured fields are present and their contributing authorities are shown above.

Material change intelligence

What changed after publication

View recent updates ↗
  1. Affected versionsThe structured affected or fixed version information changed.
    Before
    mta/mta-solution-server-rhel9 as a component of Migration Toolkit for Applications 8; ansible-automation-platform-27/gateway-rhel9 as a component of Red Hat Ansible Automation Platform 2
    After
    ansible-automation-platform-27/gateway-rhel9 as a component of Red Hat Ansible Automation Platform 2
    Red Hat Product Security ↗
  2. Affected versionsThe structured affected or fixed version information changed.
    Before
    mta/mta-solution-server-rhel9 as a component of Migration Toolkit for Applications 8; pen-drive/pen-drive-scanner-rhel9 as a component of Pen Drive Powered by Red Hat Lightspeed; ansible-automation-platform-27/gateway-rhel9 as a component of Red Hat Ansible Automation Platform 2
    After
    mta/mta-solution-server-rhel9 as a component of Migration Toolkit for Applications 8; ansible-automation-platform-27/gateway-rhel9 as a component of Red Hat Ansible Automation Platform 2
    Red Hat Product Security ↗
  3. Vendor guidanceAuthoritative vendor guidance changed from remediation: access.redhat.com/CVE-2026-25589 to remediation: access.redhat.com/CVE-2026-25589.
    Before
    remediation: access.redhat.com/CVE-2026-25589
    After
    remediation: access.redhat.com/CVE-2026-25589
    Red Hat Product Security ↗
  4. Remediation statusRemediation status changed from Awaiting fix to Mitigation available.
    Before
    Awaiting fix
    After
    Mitigation available
    Red Hat Product Security ↗
  5. Affected versionsThe structured affected or fixed version information changed.
    Before
    After
    mta/mta-solution-server-rhel9 as a component of Migration Toolkit for Applications 8; pen-drive/pen-drive-scanner-rhel9 as a component of Pen Drive Powered by Red Hat Lightspeed; ansible-automation-platform-27/gateway-rhel9 as a component of Red Hat Ansible Automation Platform 2
    Red Hat Product Security ↗
Material fields only · duplicate refreshes suppressed · history retained for the configured operational retention period
Technical terms and abbreviations used in this report
CVE
Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
CVSS
Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
EPSS
Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
CWE
Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
CNA
CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
CISA ADP
Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
NVD
National Vulnerability Database: NIST's enrichment service for CVE records.
CERT / CSIRT
A computer security incident response team that publishes warnings or coordinates incident response.
PoC
Proof of concept: public material that demonstrates or helps reproduce exploitation.
CSAF
Common Security Advisory Framework: a machine-readable format for security advisories.
LoTL
Living off the land: abuse of legitimate tools or system functions during an attack.
Free version - for non-commercial use only.CVE-2026-25589 · cve.blacktree.nl