Quick answers
- Is CVE-2026-64618 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-64618 being exploited in the wild.
- How severe is CVE-2026-64618?
- Informational severity, published 30 October 2026.
- Which products and versions are affected?
- Apache Fineract through 1.15.0.
- Is there a fix for CVE-2026-64618?
- Yes: fixed in 1.16.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-64618 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-64618?
- Check whether you run Apache Fineract 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: 1.16.1
Technical details
SQL injection vulnerability exists in the outStandingAmountPercentageCondition parameter of the /fineract-provider/api/v1/search/advance endpoint due to insufficient input neutralization. The vulnerability allows unauthenticated network-based SQL command injection via a malicious parameter value. Fineract 1.16.1 and later fix this issue.
Affected products
- Apache Fineract through 1.15.0
Timeline
- 2026-10-30: disclosed
- 2026-07-23: patched