CVE-2025-61024
Deferred Deferred - Pending Action
Denial of Service in Virtuoso Open-Source Database

Publication date: 2026-06-23

Last updated on: 2026-06-23

Assigner: MITRE

Description
An issue in the sqlo_try_in_loop component of openlink virtuoso-opensource v7.2.11 allows attackers to cause a Denial of Service (DoS) via crafted SQL statements.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-06-23
Last Modified
2026-06-23
Generated
2026-06-24
AI Q&A
2026-06-23
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
openlink virtuoso-opensource 7.2.11
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-89 The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Compliance Impact

The vulnerability described causes a Denial of Service (DoS) condition in the openlink virtuoso-opensource software by crashing the system when processing crafted SQL statements.

There is no information provided about any impact on data confidentiality, integrity, or availability beyond service disruption, nor any direct mention of effects on compliance with standards such as GDPR or HIPAA.

Therefore, based on the available information, it is not possible to determine how this vulnerability affects compliance with common standards and regulations.

Executive Summary

The vulnerability CVE-2025-61024 exists in the sqlo_try_in_loop component of openlink virtuoso-opensource version 7.2.11. It is triggered by a specially crafted SQL statement that causes the software to crash. Specifically, the crash happens due to improper handling of complex SQL constructs such as nested conditions, arithmetic operations, CASE statements, and subqueries, leading to a segmentation fault.

This crash results in a Denial of Service (DoS) condition, meaning that an attacker can cause the database service to become unavailable by sending malicious SQL queries.

Impact Analysis

This vulnerability can impact you by allowing an attacker to cause a Denial of Service (DoS) on your Virtuoso Open Source database server. By exploiting this issue, an attacker can crash the database service, making it unavailable to legitimate users and potentially disrupting business operations that rely on the database.

Detection Guidance

This vulnerability can be detected by executing a crafted SQL statement that triggers the crash in the sqlo_try_in_loop function of Virtuoso Open Source version 7.2.11. The Proof of Concept (PoC) involves a complex SQL query with nested conditions, arithmetic operations, CASE statements, and subqueries that cause a segmentation fault.

Detection can be performed by setting up a Docker container environment with Virtuoso 7.2.11 and running the PoC SQL query to observe if the system crashes or segfaults, indicating the presence of the vulnerability.

While exact commands are not fully detailed here, the referenced resource provides a set of Docker commands to set up the environment and execute the PoC to reproduce the crash.

Mitigation Strategies

To mitigate the CVE-2025-61024 vulnerability, immediate steps include avoiding the execution of untrusted or complex SQL statements that could trigger the crash in the sqlo_try_in_loop function.

Additionally, setting up the environment to monitor and restrict potentially malicious SQL queries can help prevent exploitation.

Since the issue causes a denial-of-service via crafted SQL, applying any available patches or updates from the vendor once released is recommended.

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-61024. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart