# CVE-2025-61021: SQL injection in n/a

> Attackers can cause a Denial of Service in Virtuoso database via crafted SQL statements exploiting a SQL injection flaw.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 23 Jun 2026
- **Updated:** 25 Jun 2026
- **Also known as:** DEBIAN-CVE-2025-61021, GHSA-7q5w-m9wx-x74m, RHSA-2026:66026, UBUNTU-CVE-2025-61021

## What is CVE-2025-61021?

CVE-2025-61021 is a high-severity SQL injection vulnerability in n/a, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue in the sqlo_natural_join_cond component of openlink virtuoso-opensource v7.2.11 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements.

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

## Which versions are affected by CVE-2025-61021?


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `virtuoso-opensource` | Red Hat:rhel_els:7 | All versions | 1:6.1.6-9.el7_9 |
| `virtuoso-opensource-debuginfo` | Red Hat:rhel_els:7 | All versions | 1:6.1.6-9.el7_9 |
| `virtuoso-opensource-utils` | Red Hat:rhel_els:7 | All versions | 1:6.1.6-9.el7_9 |

## How do I fix CVE-2025-61021?

Apply the vendor's patch.

## Is CVE-2025-61021 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61021 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-61021 and fix it if it is affected.

What it is: CVE-2025-61021 is a high-severity SQL injection vulnerability in n/a, published on 23 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61021 exists.

Affected product: n/a. 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-2025-61021/ (Markdown: https://insights.sbomify.com/CVE-2025-61021/index.md)
```

## Sources

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

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