Widely used SuiteCRM; high-risk data exposure and potential RCE via FILE privilege; affect many orgs.
CVE-2026-29096
Second-order SQLi in SuiteCRM reports allows data exfiltration.
Is CVE-2026-29096 being exploited?
Not confirmed. CVE-2026-29096 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.32% probability of exploitation in the next 30 days.
How severe is CVE-2026-29096?
CVE-2026-29096 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-29096?
Yes. A fix has been recorded for CVE-2026-29096. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-29096 affect?
CVE-2026-29096 affects SuiteCRM < 7.15.1, < 8.9.3. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-29096?
Patch to 7.15.1/8.9.3; limit Reports access; rotate secrets.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated users with Reports access can trigger second-order SQLi to read DB data; possible RCE if FILE privilege is abused.
Patch when possible
- affected< 7.15.1
- affected>= 8.0.0 and < 8.9.3
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.