CVE-2026-4324: Rubygem-katello: katello: denial of service and potential information disclosure via sql injection
A flaw was found in the Katello plugin for Red Hat Satellite. The vulnerability occurs due to improper sanitization of user-provided input in the sortby parameter of the /api/hosts/bootcimages API endpoint. An attacker could exploit this flaw by injecting arbitrary SQL commands into the order clause of the database query. While certain complex queries are blocked by the underlying framework's protections, an attacker can still manipulate the query structure to trigger database errors, cause a Denial of Service (DoS), or potentially perform Boolean-based Blind SQL injection.
Other sources
A flaw was found in the Katello plugin for Red Hat Satellite. This vulnerability, caused by improper sanitization of user-provided input, allows a remote attacker to inject arbitrary SQL commands into the sortby parameter of the /api/hosts/bootcimages API endpoint. This can lead to a Denial of Service (DoS) by triggering database errors, and potentially enable Boolean-based Blind SQL injection, which could allow an attacker to extract sensitive information from the database.
— MITRE
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
rubygems/katelloto a version that resolves this vulnerability.Fixed in 4.19.1
Event History
Frequently Asked Questions
What is the severity of CVE-2026-4324?
CVE-2026-4324 has been classified as a denial of service vulnerability with potential information disclosure risks.
How do I fix CVE-2026-4324?
To mitigate CVE-2026-4324, users should update the Katello plugin for Red Hat Satellite to the latest version that addresses this vulnerability.
What software is affected by CVE-2026-4324?
CVE-2026-4324 affects the Katello plugin for Red Hat Satellite.
What impact can CVE-2026-4324 have on my system?
If exploited, CVE-2026-4324 can lead to a denial of service and may expose sensitive information.
Is there a workaround for CVE-2026-4324?
Currently, the recommended action for CVE-2026-4324 is to apply the latest updates, as no specific workaround is provided.