# CVE-2026-56097: Rubygem-katello: sql injection in registry proxy via labels

> An attacker with limited permissions can execute arbitrary SQL commands via unsanitized labels in the Katello Registry Proxy, potentially accessing or modifying database contents.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 1 Oct 2026
- **Updated:** 7 Oct 2026
- **Also known as:** GHSA-mmq3-mv36-wfm7

## What is CVE-2026-56097?

CVE-2026-56097 is a medium-severity SQL injection vulnerability in Red Hat Satellite 6, published on 1 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in rubygem-katello. An SQL injection vulnerability exists in the Red Hat Satellite Katello Registry Proxy. The application fails to sanitize input parameters used in database queries within the RegistryProxiesController. The methods check_blob_push_org_label and get_matching_products_from_org take user-supplied labels directly from the request path and interpolate them into raw SQL fragments. This flaw is accessible to a user with only the create_personal_access_tokens permission, even if the user access is restricted, with no Organization or Location assigned.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-56097?


## How do I fix CVE-2026-56097?

Apply the vendor's patch.

## Is CVE-2026-56097 being exploited?

There is no known exploitation of CVE-2026-56097 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-56097 and fix it if it is affected.

What it is: CVE-2026-56097 is a medium-severity SQL injection vulnerability in Red Hat Satellite 6, published on 1 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-56097 in the wild and no public exploit code.

Affected product: Red Hat Satellite 6. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-56097/ (Markdown: https://insights.sbomify.com/CVE-2026-56097/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-56097
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-56097
- OSV: https://osv.dev/vulnerability/CVE-2026-56097

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-56097/
Summaries are generated and may contain mistakes; the official description above is the record.