xmlrpc-c: XML-RPC is a remote procedure call (RPC) protocol that uses XML to encode its calls and HTTP as a transport mechanism
CVE-2026-15928 is fixed in 5 products on 1 platform, first by SUSE-SU-2026:3572-1, released August 11, 2026. It is not reported as exploited. Patch Radar priority: High.
XML-RPC is a remote procedure call (RPC) protocol that uses XML to encode its calls and HTTP as a transport mechanism. The xmlrpc-c packages provide a network protocol to allow a client program to make a simple RPC (remote procedure call) over the Internet. It converts an RPC into an XML document, sends it to a remote server using HTTP, and gets back the response in XML. Security Fix(es): * xmlrpc-c: XMLRPC-C Library: Cross-Site Scripting in error page component (CVE-2026-15928) For more details about the security issue(s), including the impact, a CVSS score, acknowledgments, and other related information, refer to the CVE page(s) listed in the References section.
Where it's fixed
| Product | Fixed in | Fix | Released |
|---|---|---|---|
| Linux | |||
| xmlrpc-c · RHEL 8 | 0:1.51.0-11.el8_10.1 | RHSA-2026:64772 | Sep 13, 2026 |
| xmlrpc-c · RHEL 9 | 0:1.51.0-17.el9_8 | RHSA-2026:61316 | Sep 13, 2026 |
| xmlrpc-c · almalinux 8 | 1.51.0-11.el8_10.1 | ALSA-2026:64772 | Sep 8, 2026 |
| xmlrpc-c · almalinux 9 | 1.51.0-17.el9_8 | ALSA-2026:61316 | Aug 31, 2026 |
| xmlrpc-c · ol 8 | 0:1.51.0-11.el8_10.1 | ELSA-2026-64772-0 | Sep 8, 2026 |
| xmlrpc-c · ol 9 | 0:1.51.0-17.el9_8 | ELSA-2026-61316-0 | Sep 1, 2026 |
| xmlrpc-c · opensuse-leap 16.0 | 1.54.06-160000.3.1 | OPENSUSE-SU-2026:21633-1 | Aug 24, 2026 |
| xmlrpc-c · rocky 8 | 0:1.51.0-11.el8_10.1 | RLSA-2026:64772 | Sep 9, 2026 |
| xmlrpc-c · rocky 9 | 0:1.51.0-17.el9_8 | RLSA-2026:61316 | Sep 1, 2026 |
| xmlrpc-c · sles 15.7 | 1.51.07-150400.3.3.1 | SUSE-SU-2026:3572-1 | Aug 11, 2026 |
| xmlrpc-c · sles 16.0 | 1.54.06-160000.3.1 | SUSE-SU-2026:23311-1 | Aug 24, 2026 |
| xmlrpc-c-c++ · RHEL 8 | 0:1.51.0-11.el8_10.1 | RHSA-2026:64772 | Sep 13, 2026 |
| xmlrpc-c-c++ · RHEL 9 | 0:1.51.0-17.el9_8 | RHSA-2026:61316 | Sep 13, 2026 |
| xmlrpc-c-c++ · almalinux 8 | 1.51.0-11.el8_10.1 | ALSA-2026:64772 | Sep 8, 2026 |
| xmlrpc-c-c++ · almalinux 9 | 1.51.0-17.el9_8 | ALSA-2026:61316 | Aug 31, 2026 |
| xmlrpc-c-c++ · ol 8 | 0:1.51.0-11.el8_10.1 | ELSA-2026-64772-0 | Sep 8, 2026 |
| xmlrpc-c-c++ · ol 9 | 0:1.51.0-17.el9_8 | ELSA-2026-61316-0 | Sep 1, 2026 |
| xmlrpc-c-client · RHEL 8 | 0:1.51.0-11.el8_10.1 | RHSA-2026:64772 | Sep 13, 2026 |
| xmlrpc-c-client · RHEL 9 | 0:1.51.0-17.el9_8 | RHSA-2026:61316 | Sep 13, 2026 |
| xmlrpc-c-client · almalinux 8 | 1.51.0-11.el8_10.1 | ALSA-2026:64772 | Sep 8, 2026 |
| xmlrpc-c-client · almalinux 9 | 1.51.0-17.el9_8 | ALSA-2026:61316 | Aug 31, 2026 |
| xmlrpc-c-client · ol 8 | 0:1.51.0-11.el8_10.1 | ELSA-2026-64772-0 | Sep 8, 2026 |
| xmlrpc-c-client · ol 9 | 0:1.51.0-17.el9_8 | ELSA-2026-61316-0 | Sep 1, 2026 |
| xmlrpc-c-client++ · RHEL 8 | 0:1.51.0-11.el8_10.1 | RHSA-2026:64772 | Sep 13, 2026 |
| xmlrpc-c-client++ · RHEL 9 | 0:1.51.0-17.el9_8 | RHSA-2026:61316 | Sep 13, 2026 |
| xmlrpc-c-client++ · almalinux 8 | 1.51.0-11.el8_10.1 | ALSA-2026:64772 | Sep 8, 2026 |
| xmlrpc-c-client++ · almalinux 9 | 1.51.0-17.el9_8 | ALSA-2026:61316 | Aug 31, 2026 |
| xmlrpc-c-client++ · ol 8 | 0:1.51.0-11.el8_10.1 | ELSA-2026-64772-0 | Sep 8, 2026 |
| xmlrpc-c-client++ · ol 9 | 0:1.51.0-17.el9_8 | ELSA-2026-61316-0 | Sep 1, 2026 |
| xmlrpc-c-devel · RHEL 8 | 0:1.51.0-11.el8_10.1 | RHSA-2026:64772 | Sep 13, 2026 |
| xmlrpc-c-devel · RHEL 9 | 0:1.51.0-17.el9_8 | RHSA-2026:61316 | Sep 13, 2026 |
| xmlrpc-c-devel · almalinux 8 | 1.51.0-11.el8_10.1 | ALSA-2026:64772 | Sep 8, 2026 |
| xmlrpc-c-devel · almalinux 9 | 1.51.0-17.el9_8 | ALSA-2026:61316 | Aug 31, 2026 |
| xmlrpc-c-devel · ol 8 | 0:1.51.0-11.el8_10.1 | ELSA-2026-64772-0 | Sep 8, 2026 |
| xmlrpc-c-devel · ol 9 | 0:1.51.0-17.el9_8 | ELSA-2026-61316-0 | Sep 1, 2026 |
Patch Radar data is free to use with attribution. Terms and how to credit it.
Product names, logos and trademarks shown on Patch Radar belong to their respective owners. They are used only to identify the software each security fix applies to and to help readers find their platform. Their use does not imply any affiliation with, or endorsement by, those owners, and Patchblox is not affiliated with any of them.