dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-4324

MEDIUM · 5.4 CVSS v3.1 Published 2026-03-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 sort_by parameter of the /api/hosts/bootc_images 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Katello plugin for Red Hat Satellite contains a SQL injection vulnerability in the /api/hosts/bootc_images API endpoint. The sort_by parameter is not properly sanitized, allowing an attacker to inject arbitrary SQL commands. This can cause database errors leading to DoS and potentially enable boolean-based blind SQL injection for extracting sensitive data.

MitigationImplement proper input validation and parameterized queries for the sort_by parameter in the bootc_images API endpoint. Apply the vendor patch when available and conduct thorough testing to verify the sanitization is effective.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Katello plugin is installed
    Check for the presence of the Katello plugin in Red Hat Satellite by running: rpm -qa | grep -i katello or checking the Satellite web UI for Katello components under Hosts > Bootc Images
    Affected if The Katello plugin is present and the bootc_images feature is enabled
  2. Determine the Katello/Satellite version
    Run: rpm -q katello or satellite --version to obtain the installed version number
    Affected if The installed version falls within the vulnerable version range (if known) or is unpatched for this CVE
  3. Verify bootc_images API endpoint exposure
    Check if the /api/hosts/bootc_images endpoint is accessible: curl -k -u admin:password https://satellite-server/api/hosts/bootc_images 2>/dev/null | head -20
    Affected if The API endpoint returns a response (even if empty) indicating it is exposed
  4. Test sort_by parameter for SQL injection susceptibility
    Send a request with a malicious sort_by value: curl -k -u admin:password 'https://satellite-server/api/hosts/bootc_images?sort_by=test\' OR 1=1--' -X GET and observe for database errors or unexpected behavior
    Affected if The endpoint returns database errors, behaves unexpectedly, or appears to process the injected SQL syntax
  5. Review API access logs for SQL injection attempts
    Check Satellite logs under /var/log/foreman/production.log or /var/log/katello/katello.log for entries containing bootc_images and suspicious sort_by patterns containing quotes or SQL keywords
    Affected if Logs show malformed queries or SQL syntax errors related to the sort_by parameter

A user is affected if they have Katello with bootc_images enabled, the vulnerable sort_by parameter is accessible via the API, and the installed version is unpatched for CVE-2026-4324.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and parameterized queries for the sort_by parameter in the bootc_images API endpoint. Apply the vendor patch when available and conduct thorough testing to verify the sanitization is effective.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4324 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4324 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data