CVE-2026-8827
SQL Injection in AddressRepository::getSqlQuery() via untrusted input (extension).
Is CVE-2026-8827 being exploited?
Not confirmed. CVE-2026-8827 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.33% probability of exploitation in the next 30 days.
How severe is CVE-2026-8827?
CVE-2026-8827 is rated High with a CVSS score of 8.2. 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-8827?
Yes. A fix has been recorded for CVE-2026-8827. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-8827 affect?
CVE-2026-8827 affects Extensions calling AddressRepository::getSqlQuery(), Deployments using this extension with untrusted input. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-8827?
Sanitize inputs and use parameterized queries
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
SQL injection via untrusted input when custom extensions call the method; could lead to data theft, modification.
Patch when possible
- affected>= 10.0.0 and < 10.0.1
- affected>= 9.0.0 and < 9.1.1
- affected< 8.1.2
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.