HIGH 7.5

CVE-2025-61027: OpenLink Virtuoso 7.2.11 Remote Denial of Service Vulnerability

OpenLink Virtuoso Open Source version 7.2.11 contains a vulnerability in its t_set_push component that allows remote attackers to crash the database server by sending specially crafted SQL statements. No authentication is required to exploit this issue, making it accessible to any network-connected user. The attack results in denial of service, preventing legitimate users from accessing the database until the server is restarted.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.5 HIGH · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Weaknesses (CWE)
CWE-89
Affected products
0 configuration(s)
Published / Modified
2026-06-23 / 2026-06-25

NVD description (verbatim)

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

2 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2025-61027 is a denial of service vulnerability affecting the t_set_push component of OpenLink Virtuoso Open Source 7.2.11. The vulnerability stems from improper handling of SQL input (CWE-89: SQL Injection), allowing unauthenticated remote attackers to craft malicious SQL statements that trigger unhandled exceptions or resource exhaustion in the server process. The network-accessible nature of the vulnerability (CVSS vector AV:N) combined with low attack complexity (AC:L) and no privilege requirements (PR:N) creates a significant availability risk for exposed Virtuoso instances.

Business impact

Organizations running Virtuoso Open Source 7.2.11 face potential service disruptions affecting all database-dependent applications and business processes. A successful DoS attack could interrupt reporting, analytics, transaction processing, or any other functions relying on the affected Virtuoso instance. Recovery requires manual server restart, potentially causing hours of downtime and data access delays. The ease of exploitation—requiring only network access and no credentials—means this risk extends beyond internal networks if the service is exposed to untrusted networks.

Affected systems

OpenLink Virtuoso Open Source version 7.2.11 is specifically affected. Organizations should verify whether they operate this version in production or development environments. Users of other Virtuoso versions (both older and newer releases) should consult OpenLink's official advisory to determine if their deployments are in scope. The vulnerability does not appear to affect vendor-supplied products based on available information, though this should be confirmed against official vendor documentation.

Exploitability

This vulnerability is highly exploitable due to its network accessibility, lack of authentication requirements, and low attack complexity. An attacker with network access can trigger the denial of service without possessing valid database credentials or internal knowledge of the system. The attack merely requires crafting specific SQL statements and submitting them to the exposed Virtuoso instance. No user interaction or special conditions are needed, making this suitable for both targeted attacks and opportunistic exploitation by automated scanning tools.

Remediation

Organizations should immediately apply patches released by OpenLink for this vulnerability. Verify the patched version number against the official OpenLink Virtuoso advisory. As an interim measure, restrict network access to Virtuoso instances through firewall rules, allowing connections only from trusted application servers and administrative hosts. Implement SQL query logging and monitoring to detect suspicious statement patterns. If patching cannot be completed immediately, consider taking affected instances offline or operating them in isolated network segments until remediation is complete.

Patch guidance

Contact OpenLink directly or consult their official security advisory for the specific patched version addressing CVE-2025-61027. Apply patches first to non-production test environments to validate compatibility with dependent applications and existing database configurations. Establish a maintenance window for production patching to minimize business disruption. After patching, verify that the t_set_push component functions correctly and conduct regression testing of SQL workloads known to exercise that code path. Document the patch version deployed for future audit and compliance purposes.

Detection guidance

Monitor for unusual SQL error patterns or database server crashes that correlate with external connection attempts. Enable detailed SQL query logging to capture statements preceding server failures or performance degradation. Use intrusion detection systems to identify network-based SQL injection patterns targeting Virtuoso instances. Check for error messages or logs mentioning 't_set_push' component failures. Establish baseline metrics for normal CPU and memory usage; anomalous spikes followed by server crashes may indicate DoS exploitation. Regularly scan the network for exposed Virtuoso instances using port enumeration and service identification tools.

Why prioritize this

This vulnerability merits immediate attention due to its HIGH CVSS score (7.5) combined with critical exploitability factors: complete lack of authentication barriers, remote network accessibility, and ease of attack execution. While impact is limited to availability (not confidentiality or integrity), denial of service can cascade into severe business consequences depending on the criticality of database-dependent applications. The low effort required to exploit makes this an attractive target for both sophisticated threat actors and indiscriminate scanning campaigns.

Risk score, explained

The CVSS 3.1 score of 7.5 (HIGH) reflects the combination of maximum impact severity for the availability metric (A:H) with minimal barriers to exploitation. The network attack vector (AV:N), low complexity (AC:L), and no privilege requirements (PR:N) indicate this is weaponizable by any attacker with network connectivity. The lack of user interaction requirement (UI:N) and unscoped impact (S:U) further elevate the risk profile. However, the score stops short of CRITICAL because confidentiality and integrity are not affected—the attack is constrained to availability disruption.

Frequently asked questions

Should we assume OpenLink has released a patch, or do we need to wait for one?

The source data does not specify a patched version number or availability timeline. You must contact OpenLink directly or check their official security advisory to determine whether a patch is available, what version it addresses, and when general availability is expected. Do not assume patch availability; verify directly with the vendor before making deployment decisions.

Does this vulnerability require us to take systems offline immediately?

That depends on your risk tolerance and operational criticality. If the Virtuoso instance processes business-critical workloads and is exposed to untrusted networks, taking it offline until patched is prudent. If access is restricted to internal trusted networks only, implementing strict firewall rules and monitoring may provide adequate short-term protection while you plan patching. Document your risk decision and timeline for remediation.

How does this differ from a typical SQL injection vulnerability?

While rooted in SQL injection (CWE-89), this vulnerability is specifically a denial of service variant rather than one exploited for data theft or modification. Attackers cannot extract or alter data; they can only crash the server. This narrows the threat model but doesn't reduce urgency, since availability loss is equally damaging to business operations.

Is version 7.2.10 or 7.2.12 affected?

The source data specifies only version 7.2.11 as affected. Other versions may be vulnerable, but this cannot be assumed. Consult the OpenLink advisory for precise version scope and determine whether your deployments fall within that range.

This analysis is based on the vulnerability description and CVSS assessment as of the publication date. Patch availability, affected product scope, and vendor response timelines are subject to change and should be verified directly with OpenLink. This content does not constitute legal or compliance advice. Organizations should conduct their own risk assessments based on their specific environment, dependencies, and business criticality. SEC.co makes no warranty regarding the completeness or accuracy of third-party vendor information and recommends consulting official vendor advisories before making operational decisions. Source: NVD (public-domain), retrieved 2026-07-28. Analysis generated by SEC.co (claude-haiku-4-5).