What is CVE-2026-76904?

CVE-2026-76904 is a critical-severity SQL injection vulnerability in org.geotools.jdbc:gt-jdbc-postgis (maven), affecting versions = 35.0. It is fixed in 35.1, 34.5, 33.6. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.

How severe is CVE-2026-76904?

CVE-2026-76904 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.geotools.jdbc:gt-jdbc-postgis are affected by CVE-2026-76904?

org.geotools.jdbc:gt-jdbc-postgis (maven) versions = 35.0 is affected.

Is there a fix for CVE-2026-76904?

Yes. CVE-2026-76904 is fixed in 35.1, 34.5, 33.6. Upgrade to this version or later.

Is CVE-2026-76904 exploitable, and should I be worried?

Whether CVE-2026-76904 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-76904 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-76904?

Upgrade: org.geotools.jdbc:gt-jdbc-postgis to 35.1 or later, org.geotools.jdbc:gt-jdbc-postgis to 34.5 or later, org.geotools.jdbc:gt-jdbc-postgis to 33.6 or later.

CVE-2026-76904 in org.geotools.jdbc:gt-jdbc-postgis

Summary

GeoTools has unauthenticated SQL injection in the jsonArrayContains filter function against PostGIS layers

An SQL Injection Vulnerability has been found when executing OGC Filters with PostGIS DataStore implementation:

jsonArrayContains function
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.

Mitigation

No mitigation is available:

To limit scope of SQL Injection the PostGIS connection pool should be configured with limited rights.

References

Impact

This vulnerability can lead to execution of arbitrary SQL expressions in the database.

Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.

CVE-2026-76904 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (35.1, 34.5, 33.6); upgrading removes the vulnerable code path.

Affected versions

org.geotools.jdbc:gt-jdbc-postgis (= 35.0) org.geotools.jdbc:gt-jdbc-postgis (>= 34.0, < 34.5) org.geotools.jdbc:gt-jdbc-postgis (>= 30.5, < 33.6)

Security releases

org.geotools.jdbc:gt-jdbc-postgis → 35.1 (maven) org.geotools.jdbc:gt-jdbc-postgis → 34.5 (maven) org.geotools.jdbc:gt-jdbc-postgis → 33.6 (maven)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

GeoTools 35.1
GeoTools 33.5
GeoTools 34.4

Frequently Asked Questions

What is CVE-2026-76904? CVE-2026-76904 is a critical-severity SQL injection vulnerability in org.geotools.jdbc:gt-jdbc-postgis (maven), affecting versions = 35.0. It is fixed in 35.1, 34.5, 33.6. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
How severe is CVE-2026-76904? CVE-2026-76904 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of org.geotools.jdbc:gt-jdbc-postgis are affected by CVE-2026-76904? org.geotools.jdbc:gt-jdbc-postgis (maven) versions = 35.0 is affected.
Is there a fix for CVE-2026-76904? Yes. CVE-2026-76904 is fixed in 35.1, 34.5, 33.6. Upgrade to this version or later.
Is CVE-2026-76904 exploitable, and should I be worried? Whether CVE-2026-76904 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-76904 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-76904?
- Upgrade org.geotools.jdbc:gt-jdbc-postgis to 35.1 or later
- Upgrade org.geotools.jdbc:gt-jdbc-postgis to 34.5 or later
- Upgrade org.geotools.jdbc:gt-jdbc-postgis to 33.6 or later