CVE-2026-32698
SQL injection in OpenProject Cost Reports via custom field name.
Is CVE-2026-32698 being exploited?
Not confirmed. CVE-2026-32698 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.27% probability of exploitation in the next 30 days.
How severe is CVE-2026-32698?
CVE-2026-32698 is rated Critical with a CVSS score of 9.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-32698?
Yes. A fix has been recorded for CVE-2026-32698. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-32698 affect?
CVE-2026-32698 affects OpenProject (<16.6.9, <17.0.6, <17.1.3, <17.2.1). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-32698?
Upgrade to fixed versions: 16.6.9+, 17.0.6+, 17.1.3+, or 17.2.1
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
SQL injection allows arbitrary SQL in Cost Reports; may read/modify data; path bug could trigger Ruby code on restart.
Patch when possible
- affected< 16.6.9
- affected>= 17.0.0 and < 17.0.6
- affected>= 17.1.0 and < 17.1.3
- affected>= 17.2.0 and < 17.2.1
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.