Quick answers
- Is CVE-2026-81815 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81815 being exploited in the wild.
- How severe is CVE-2026-81815?
- Informational severity, published 5 November 2026.
- Which products and versions are affected?
- Apache OFBiz 24.09 before 24.09.08.
- Is there a fix for CVE-2026-81815?
- Yes: fixed in 24.09.08. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-81815 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-81815?
- Check whether you run Apache OFBiz 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.
How to fix
- Fixed in: 24.09.08
Technical details
The vulnerability exists in SqlJdbcUtil.addValueSingle, which handles ignore-case find requests (via _ic=Y parameter) by inlining EntityFunction-wrapped values into SQL using ANSI single-quote doubling rather than parameterized binding. MySQL and MariaDB interpret backslash as an escape character, allowing attackers to break out of string literals with a backslash-terminated payload and turn WHERE clauses into tautologies. Derby and PostgreSQL are unaffected as they do not interpret backslash escapes in this context.
Affected products
- Apache OFBiz 24.09 before 24.09.08
Timeline
- 2026-11-05: disclosed