Skip to content
VulniPulse
Sign in
Advisory severityHigh7.4Red Hat Linux

High [CVE-2026-15928] Cross-Site Scripting in error page component

This high-severity Red Hat Linux advisory covers CVE-2026-15928 affecting Red Hat Enterprise Linux 7 Extended Lifecycle Support, Red Hat Enterprise Linux 8.4 Advanced Mission Critical Update Support, Red Hat Enterprise Linux 8.4 Extended Update Support Long-Life Add-On.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-15928 Source published Source updated

VulniPulse record published Record updated

CVE-2026-15928
Affected products & platforms
Red Hat LinuxRed Hat Enterprise Linux
Open source advisory

Android app · Google Play

Monitor future Red Hat Linux CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery
Get CVE alertsSee app features

Summary

XMLRPC-C Library versions 1.07 through 1.67.01 are vulnerable to a reflected cross-site scripting (XSS) vulnerability in the error page component. A remote attacker could exploit this by tricking a user into clicking a specially crafted link.

Successful exploitation could lead to the execution of malicious scripts in the user's browser, potentially resulting in information disclosure or session hijacking. This reflected cross-site scripting (XSS) vulnerability relies entirely on client-side interaction through a web browser.

If executed, the script runs within the context of the user's browser session, making sensitive session tokens or client-side data accessible to the attacker. While external CVSSv4 scoring rates this flaw to an 8.2 High, Red Hat bounds the severity to CVSS 7.4 based on explicit CIA triad mechanics.

The impact is strictly confined to Confidentiality (C:H) via potential browser-side data disclosure. The flaw carries zero impact on system Integrity (I:N) or Availability (A:N), as it cannot alter server-side application logic, modify stored data, or disrupt underlying XML-RPC services.

Affected versions
  • 1.07
  • 1.67.01

Official advisory · high-confidence parse· fetched 26 days ago·verify at source

Fixed versions
  • xmlrpc-c-0:1.32.5-1905.svn2451.el7_9.1
  • xmlrpc-c-0:1.51.0-11.el8_10.1
  • xmlrpc-c-0:1.51.0-5.el8_4.3
  • xmlrpc-c-0:1.51.0-6.el8_6.2
  • xmlrpc-c-0:1.51.0-8.el8_8.2
  • xmlrpc-c-0:1.51.0-17.el9_8
  • xmlrpc-c-0:1.51.0-16.el9_2.1
  • xmlrpc-c-0:1.51.0-16.el9_4.1
  • xmlrpc-c-0:1.51.0-16.el9_6.1
  • RHSA-2026:61234
  • RHSA-2026:64772
  • RHSA-2026:61236
  • RHSA-2026:61233
  • RHSA-2026:61235
  • RHSA-2026:61316
  • RHSA-2026:61231
  • RHSA-2026:61232
  • RHSA-2026:61315

Official advisory · high-confidence parse· fetched 26 days ago·verify at source

Mitigation checklist

Recommended fix / mitigation
  • To mitigate this issue, ensure that applications utilizing the XMLRPC-C library do not directly expose its error pages to end-users via a web browser. Configure web servers or application frontends to intercept and sanitize or replace error responses originating from XMLRPC-C before they are rendered client-side. Alternatively, restrict XMLRPC-C deployments to backend services that do not present error output in a user-facing web interface.

Official advisory · high-confidence parse· fetched 26 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.