Memory disclosure or crash via unterminated extensions
Published Sep 17, 2026 · Updated Sep 17, 2026
Out-of-bounds read in Redis Community allows adjacent unauthenticated attackers to disclose memory or crash clustered Redis nodes. The cluster-bus parser validates extension padding and packet length but passes HOSTNAME and HUMAN_NODENAME data to C-string consumers without requiring a terminating NUL byte. Exploitation requires access to a clustered node's bus port and a valid target node ID; impact is bounded to memory disclosure or process crash.
Summary
What happened
Out-of-bounds read in Redis Community allows adjacent unauthenticated attackers to disclose memory or crash clustered Redis nodes. The cluster-bus parser validates extension padding and packet length but passes HOSTNAME and HUMAN_NODENAME data to C-string consumers without requiring a terminating NUL byte. Exploitation requires access to a clustered node's bus port and a valid target node ID; impact is bounded to memory disclosure or process crash.
The record
- CVE
- CVE-2026-92925
- Published
- Sep 17, 2026
- Updated
- Sep 17, 2026
- Vendor
- Commonhaus Foundation
- Product
- Red Hat Enterprise Linux AI
- Classifications
- CWE-125, T1210
- Attack vector
- adjacent
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 17, 2026CVE publishedPublication date reported by the CVE source.
- Sep 17, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started