Quick answers
- Is CVE-2025-61020 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-61020 being exploited in the wild.
- How severe is CVE-2025-61020?
- Informational severity, with a CVSS score of 7.5, published 23 June 2026.
- Which products and versions are affected?
- OpenLink Software Virtuoso OpenSource 7.2.11.
- Is there a fix for CVE-2025-61020?
- 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-61020 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2025-61020?
- 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 sqlo_strip_in_join component of OpenLink Virtuoso OpenSource v7.2.11. The issue is triggered during the optimization or execution phase of specific SQL statements involving nested IN clauses and aggregate functions (e.g., xmlagg). An attacker with the ability to execute SQL queries against the database can cause a NULL pointer dereference or similar memory corruption leading to a daemon crash. The vulnerability was identified via fuzzing and can be reproduced using a crafted UPDATE statement with a complex subquery. No patch is explicitly confirmed in the advisory, though it was reported via the project's GitHub issue tracker.
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 by NVD