Quick answers
- Is CVE-2025-61027 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-61027 being exploited in the wild.
- How severe is CVE-2025-61027?
- Informational severity, with a CVSS score of 0, published 23 June 2026.
- Which products and versions are affected?
- OpenLink Software Virtuoso OpenSource 7.2.11.
- Is there a fix for CVE-2025-61027?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2025-61027 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2025-61027?
- Check whether you run OpenLink Software Virtuoso OpenSource at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability exists in the t_set_push component of OpenLink Virtuoso OpenSource v7.2.11. The issue is triggered during the compilation or execution phase of complex SQL statements involving specific subqueries, CROSS JOINs, and date arithmetic (as demonstrated in the provided PoC). When the engine processes these crafted statements, it triggers a null pointer dereference or similar memory corruption leading to a process crash (SIGSEGV). An attacker with the ability to execute SQL queries against the database can exploit this to cause a persistent Denial of Service. The issue was identified via fuzzing and reported on the project's GitHub repository.
Affected products
- OpenLink Virtuoso OpenSource 7.2.11
Timeline
- 2024-01-07: disclosed: Issue reported on GitHub with PoC
- 2026-06-23: advisory: CVE published to NVD