# CVE-2026-64618: Apache Fineract SQL injection in search API

Source: https://junglewise.ai/threats/cve-2026-64618-improper-neutralization-of-special-elements-used-in-an-sql  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-10-30. Updated: 2026-10-30  
License: CC BY 4.0 with a link back

CVE-2026-64618 · Severity: info · Published 2026-10-30

Apache Fineract is a financial services platform used by microfinance institutions to manage loans and customer accounts. A SQL injection vulnerability in the search API allows an attacker to execute arbitrary database commands, potentially exposing or modifying sensitive financial data. Exploitation requires network access to the vulnerable API endpoint.

Technologies: [Apache Fineract](https://junglewise.ai/threats/technologies/apache-fineract). Vendors: [Apache](https://junglewise.ai/threats/vendors/apache).

## 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

## References

- [https://github.com/apache/fineract/pull/6153](https://github.com/apache/fineract/pull/6153)
- [https://lists.apache.org/thread/s8orckszcd9x4d1qsloc046ppf5q9oc7](https://lists.apache.org/thread/s8orckszcd9x4d1qsloc046ppf5q9oc7)

## Related threats

- [Apache Fineract SQL injection in centers and datatables endpoints](https://junglewise.ai/threats/cve-2026-65874-this-issue-affects-apache-fineract-versions-up-to-and-including-1)
- [Authorization Bypass Through User-Controlled Key vulnerability in Apache Fineract. This issue affects Apache Fineract…](https://junglewise.ai/threats/cve-2025-58137-authorization-bypass-through-user-controlled-key-vulnerability-in)
- [Insufficiently Protected Credentials vulnerability in Apache Fineract. This issue affects Apache Fineract: through…](https://junglewise.ai/threats/cve-2025-58130-insufficiently-protected-credentials-vulnerability-in-apache)
- [Weak Password Requirements vulnerability in Apache Fineract. This issue affects Apache Fineract: through 1.10.1. The…](https://junglewise.ai/threats/cve-2025-23408-weak-password-requirements-vulnerability-in-apache-fineract-this)