First published: Tue May 13 2025(Updated: )
Low: xterm security update
Affected Software | Affected Version | How to fix |
---|---|---|
Red Hat Enterprise Linux 8 | ||
Red Hat Enterprise Linux Server for IBM z Systems | ||
Red Hat Enterprise Linux for ARM 64 | ||
Red Hat Enterprise Linux for Power, little endian - Extended Update Support | ||
redhat/xterm | <366-10.el9_6 | 366-10.el9_6 |
redhat/xterm | <366-10.el9_6 | 366-10.el9_6 |
redhat/xterm-debuginfo | <366-10.el9_6 | 366-10.el9_6 |
redhat/xterm-debugsource | <366-10.el9_6 | 366-10.el9_6 |
redhat/xterm-resize | <366-10.el9_6 | 366-10.el9_6 |
redhat/xterm-resize-debuginfo | <366-10.el9_6 | 366-10.el9_6 |
redhat/xterm-debuginfo | <366-10.el9_6 | 366-10.el9_6 |
redhat/xterm-debugsource | <366-10.el9_6 | 366-10.el9_6 |
redhat/xterm-resize | <366-10.el9_6 | 366-10.el9_6 |
redhat/xterm-resize-debuginfo | <366-10.el9_6 | 366-10.el9_6 |
redhat/xterm | <366-10.el9_6 | 366-10.el9_6 |
redhat/xterm-debuginfo | <366-10.el9_6 | 366-10.el9_6 |
redhat/xterm-debugsource | <366-10.el9_6 | 366-10.el9_6 |
redhat/xterm-resize | <366-10.el9_6 | 366-10.el9_6 |
redhat/xterm-resize-debuginfo | <366-10.el9_6 | 366-10.el9_6 |
redhat/xterm | <366-10.el9_6.aa | 366-10.el9_6.aa |
redhat/xterm-debuginfo | <366-10.el9_6.aa | 366-10.el9_6.aa |
redhat/xterm-debugsource | <366-10.el9_6.aa | 366-10.el9_6.aa |
redhat/xterm-resize | <366-10.el9_6.aa | 366-10.el9_6.aa |
redhat/xterm-resize-debuginfo | <366-10.el9_6.aa | 366-10.el9_6.aa |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
The severity of RHSA-2025:7427 is classified as low.
RHSA-2025:7427 addresses a security vulnerability in the xterm program that could allow code execution via OSC 50 input sequences.
To fix RHSA-2025:7427, it is recommended to apply the latest security update provided by Red Hat for your affected system.
RHSA-2025:7427 affects multiple versions of Red Hat Enterprise Linux, including those for x86_64, IBM z Systems, ARM 64, and Power, little endian.
Yes, user action is required to mitigate the vulnerability by installing the appropriate updates.