RHSA-2025:11487HighCVSS 7.8

Red Hat Security Advisory: A Subscription Management tool for finding and reporting Red Hat product usage

Published
July 21, 2025
Last Modified
August 31, 2026

🔗 CVE IDs covered (6)

CVE-2025-25724 →CVE-2024-53920 →CVE-2025-3576 →CVE-2025-4802 →CVE-2025-5702 →CVE-2025-6020 →

📋 Description

CVE-2024-53920 — emacs: arbitrary code execution via Lisp macro expansion CVE-2025-3576 — krb5: Kerberos RC4-HMAC-MD5 Checksum Vulnerability Enabling Message Spoofing via MD5 Collisions CVE-2025-4802 — glibc: static setuid binary dlopen may incorrectly search LD_LIBRARY_PATH CVE-2025-5702 — glibc: Vector register overwrite bug in glibc CVE-2025-6020 — linux-pam: Linux-pam directory Traversal CVE-2025-25724 — libarchive: Buffer Overflow vulnerability in libarchive

🎯 Affected products5

  • Red Hat Discovery 2
  • registry.redhat.io/discovery/discovery-server-rhel9@sha256:bd9cb502def3153c193713b56372694cb555a71b38d4fc0fd9d021bccc5602de_arm64 as a component of Red Hat Discovery 2
  • registry.redhat.io/discovery/discovery-server-rhel9@sha256:c499a099e03c7488ffe50529a34723ade191a89fcfc59d1f0edd01db2b579ca3_amd64 as a component of Red Hat Discovery 2
  • registry.redhat.io/discovery/discovery-ui-rhel9@sha256:728ad644c83c3828f8bdc3b6aad9b1d30110f9911f0febcea5f0cfedc6b29dc7_arm64 as a component of Red Hat Discovery 2
  • registry.redhat.io/discovery/discovery-ui-rhel9@sha256:cb27ba3c1340e59001ddf83d311d952a4c11f9d4fa18bdab9f4a914370957948_amd64 as a component of Red Hat Discovery 2

✅ Remediation

The containers required to run Discovery can be installed through discovery-installer RPM. See the official documentation for more details. Workaround: Do not open or view untrusted Emacs Lisp source code files. Disabling auto-completion features and automatic error checking such as Flymake or Flycheck in untrusted Emacs Lisp source code files will mitigate this vulnerability. Workaround: Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base or stability. Workaround: Disable the `pam_namespace` module if it is not essential for your environment, or carefully review and configure it to avoid operating on any directories or paths that can be influenced or controlled by unprivileged users, such as user home directories or world-writable locations like `/tmp`.

🔗 References (10)