CVE-2026-56287
Boolean SQL injection in Apache Fineract client search allowing data exfiltration.
Is CVE-2026-56287 being exploited?
Not confirmed. CVE-2026-56287 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.65% probability of exploitation in the next 30 days.
How severe is CVE-2026-56287?
CVE-2026-56287 is rated High with a CVSS score of 8.1. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-56287?
Yes. A fix has been recorded for CVE-2026-56287. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-56287 affect?
CVE-2026-56287 affects Apache Fineract <= 1.14.0, Client Search API (GET /api/v1/clients). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-56287?
Upgrade Fineract to the fixed release; restrict client-view roles; apply WAF/SQL input filters.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated user with client-view perms can perform boolean SQLi via orderBy to extract data; on MySQL/MariaDB may read files via LOAD_FILE().
Immediate action required
- affected<= 1.14.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.