CVE-2026-76904 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in org.geotools.jdbc:gt-jdbc-postgis. O3 Security confirms whether CVE-2026-76904 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
GeoTools has unauthenticated SQL injection in the jsonArrayContains filter function against PostGIS layers
Real-World Exposure
org.geotools.jdbc:gt-jdbc-postgis☕org.geotools.jdbc:gt-jdbc-postgis☕org.geotools.jdbc:gt-jdbc-postgisReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Summary
An SQL Injection Vulnerability has been found when executing OGC Filters with PostGIS DataStore implementation:
jsonArrayContainsfunction
Requires PostGIS 12 or greater with a String or JSON field
For PostGIS 12 and greater jsonArrayContains(<column>, <pointer>, <value>) function writes <value> into generated SQL without escaping.
Patches
- GeoTools 35.1
- GeoTools 33.5
- GeoTools 34.4
Mitigation
No mitigation is available:
- To limit scope of SQL Injection the PostGIS connection pool should be configured with limited rights.
Impact
This vulnerability can lead to execution of arbitrary SQL expressions in the database.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.geotools.jdbc:gt-jdbc-postgis | ≥ 35.0&&< 35.1 | 35.1 |
| ☕Maven | org.geotools.jdbc:gt-jdbc-postgis | ≥ 34.0&&< 34.5 | 34.5 |
| ☕Maven | org.geotools.jdbc:gt-jdbc-postgis | ≥ 30.5&&< 33.6 | 33.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.geotools.jdbc:gt-jdbc-postgis. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.geotools.jdbc:gt-jdbc-postgis to 35.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-76904 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2026-76904 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2026-76904. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2026-76904 in your dependencies?
O3 detects CVE-2026-76904 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.