Skip to content
Applications

CVE-2026-76904

9.8
Critical
EPSS 2%Patch availableAug 22, 2026

SQL injection in GeoTools PostGIS DataStore jsonArrayContains enabling arbitrary SQL execution.

common questions

Is CVE-2026-76904 being exploited?

Not confirmed. CVE-2026-76904 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 1.8% probability of exploitation in the next 30 days.

How severe is CVE-2026-76904?

CVE-2026-76904 is rated Critical with a CVSS score of 9.8. 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-76904?

Yes. A fix has been recorded for CVE-2026-76904. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-76904 affect?

CVE-2026-76904 affects GeoTools (>=30.5 and prior to patched 33.6/34.5), PostGIS 12+, Applications using GeoTools PostGIS DataStore. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-76904?

Upgrade GeoTools to 33.6/34.5, restrict DB privileges, and patch immediately.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
GeoTools (>=30.5 and prior to patched 33.6/34.5)PostGIS 12+Applications using GeoTools PostGIS DataStore
impact

SQL injection allows attackers to execute arbitrary SQL on Postgres/PostGIS (v12+), enabling data theft, DB compromise, or escalation.

action required

Immediate action required

affected versions
geotools geotools
  • affected= 35.0
  • affected>= 34.0 and < 34.5
  • affected>= 30.5 and < 33.6

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.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free