Severity: High (CVSS 7.1)
Affected Systems: Redhat Ai Inference Server; Redhat Ansible Automation Platform; Redhat Confidential Compute Attestation; Redhat Connectivity Link; Redhat Enterprise Linux Ai; Redhat Logging; Redhat Openshift; Redhat Openshift Ai
Overview
Redis: redis: out-of-bounds read via crafted cluster bus packets
A high vulnerability identified as CVE-2026-92925 has been disclosed.
A flaw was found in Redis community. The cluster bus packet parser, responsible for handling PING, PONG, and MEET packets, fails to properly validate string-carrying extensions for null-termination. This oversight allows a remote attacker to craft a malicious packet, leading to an out-of-bounds read when the packet's payload is processed. Successful exploitation of this vulnerability could result in the disclosure of sensitive information or a remote denial of service (DoS).
Risk
CVSS and CISA data indicate the following:
- Review the OpenCVE and vendor advisory for exploit conditions and impact
OpenCVE Analysis
CVSS v4.0 N/ACVSS v3.1 7.1 HighCVSS v3.0 N/ACVSS v2 N/AKEV noEPSS noSSVC yes
- OpenCVE title: Redis: redis: out-of-bounds read via crafted cluster bus packets
- Severity score: High (CVSS 7.1)
- SSVC Automatable: no
- SSVC Exploitation: none
- SSVC Technical Impact: partial
- Weaknesses: CWE-125
| Attack Vector | Adjacent |
| Attack Complexity | Low |
| Privileges Required | None |
| User Interaction | None |
| Scope | Unchanged |
| Confidentiality Impact | Low |
| Integrity Impact | None |
| Availability Impact | High |
Required Action
Review the OpenCVE detail page and linked vendor advisory, then apply the vendor-provided update or mitigation for the affected product.
Prioritize systems where the affected product is internet-facing, handles authentication, or runs with elevated privileges.
Verify Updates
Confirm whether your environment uses the affected product(s): Redhat Ai Inference Server; Redhat Ansible Automation Platform; Redhat Confidential Compute Attestation; Redhat Connectivity Link; Redhat Enterprise Linux Ai; Redhat Logging; Redhat Openshift; Redhat Openshift Ai.
After remediation, verify the installed version against the fixed or unaffected versions listed by the vendor.
Temporary Mitigation (if patch is not available)
Use the mitigation published by the vendor. If no vendor mitigation is available, reduce exposure to the affected product, restrict access to trusted users or networks, and increase monitoring until an update can be applied.
Recommendation
- Use OpenCVE, vendor, and source references as the source of truth for affected versions and remediation
- Patch or mitigate affected products after confirming exposure in your environment
- Monitor affected systems for unusual activity until remediation is complete
Support
If you require assistance, please contact our support team.
Immediate action is strongly recommended to protect your infrastructure.
Source Details
Customer Responsibility and Backups
Before applying updates, mitigations, or configuration changes, customers should take and verify current backups or snapshots of affected systems.
Customers are responsible for managing their servers, validating their own backups, testing changes, and ensuring they can restore services if an update or mitigation causes an issue.
Thursday, September 17, 2026
