How severe is CVE-2023-25158?

CVE-2023-25158 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2023-25158?

CVE-2023-25158 affects the following packages: org.geotools:gt-jdbc (Maven), org.geotools:gt-jdbc (Maven), org.geotools:gt-jdbc (Maven), org.geotools:gt-jdbc (Maven), org.geotools:gt-jdbc (Maven). Ecosystems affected: Maven.

How do I fix CVE-2023-25158?

Update org.geotools:gt-jdbc to 28.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-25158 is resolved across your whole dependency graph.

How do I detect CVE-2023-25158 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.geotools:gt-jdbc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2023-25158 if there is no patch (or I can't update yet)?

Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Is CVE-2023-25158 actively exploited in the wild?

No public exploit code has been indexed for CVE-2023-25158 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2023-25158?

CVE-2023-25158 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 66th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2023-25158?

CVE-2023-25158 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2023-25158 published, and has it been updated?

CVE-2023-25158 was published on February 21, 2023 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

CVE-2023-25158 — gt-jdbc

CRITICALFix: geotools/geotools@64fb4c4

CVE-2023-25158 is a critical-severity (CVSS 9.8) SQL Injection vulnerability in org.geotools:gt-jdbc. A fix is available for org.geotools:gt-jdbc — see the affected versions and patch details below.

Unfiltered SQL Injection in Geotools

Also known asGHSA-99c3-qc2q-p94m

Published

Feb 21, 2023

Updated

Oct 28, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs66th percentile — riskier than 66% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

5 pkgs affected

☕org.geotools:gt-jdbc☕org.geotools:gt-jdbc☕org.geotools:gt-jdbc☕org.geotools:gt-jdbc☕org.geotools:gt-jdbc

Real-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

Impact

GeoTools includes support for OGC Filter expression language parsing, encoding and execution against a range of datastore.

SQL Injection Vulnerabilities have been found when executing OGC Filters with JDBCDataStore implementations:

PropertyIsLike filter
- Requires PostGIS DataStore with "encode functions" enabled
- Or any JDBCDataStore (all relational databases) with String field (no mitigation)
strEndsWith function
- Requires PostGIS DataStore with "encode functions" enabled
strStartsWith function
- Requires PostGIS DataStore with "encode functions" enabled
FeatureId filter
- Requires JDBCDataStore (all relational databases) with prepared statements disabled and table with String primary key (Oracle not affected, SQL Server and MySQL have no settings to enabled prepared statements, PostGIS does)
jsonArrayContains function
- Requires PostGIS and Oracle DataStore with String or JSON field
DWithin filter
- Happens only in Oracle DataStore, no mitigation

Patches

GeoTools 28.2
GeoTools 27.4
GeoTools 26.7
GeoTools 25.7
GeoTools 24.7

Workarounds

Partial mitigation:

In PostGIS DataStore disable "encode functions"
In any PostGIS enable "prepared statements" (only database with such settings)

        Map<String, Object> params = new HashMap<>();
        params.put("dbtype", "postgis");
        params.put("host", "localhost");
        params.put("port", 5432);
        params.put("schema", "public");
        params.put("database", "database");
        params.put("user", "postgres");
        params.put("passwd", "postgres");
        params.put("preparedStatements", true ); // mitigation
        params.put("encode functions", false ); // mitigation

        DataStore dataStore = DataStoreFinder.getDataStore(params);

References

OGC Filter SQL Injection Vulnerabilities (GeoServer)

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.geotools:gt-jdbc`	≥ 28.0&&< 28.2	28.2`org.geotools:gt-jdbc:28.2`
☕Maven	`org.geotools:gt-jdbc`	≥ 27.0&&< 27.4	27.4`org.geotools:gt-jdbc:27.4`
☕Maven	`org.geotools:gt-jdbc`	≥ 26.0&&< 26.7	26.7`org.geotools:gt-jdbc:26.7`
☕Maven	`org.geotools:gt-jdbc`	≥ 25.0&&< 25.7	25.7`org.geotools:gt-jdbc:25.7`
☕Maven	`org.geotools:gt-jdbc`	all versions	24.7`org.geotools:gt-jdbc:24.7`

Affected Products

1 product · 5 configurations

Application

geotoolsgeotools

≥ 28.0 && < 28.2

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.geotools:gt-jdbc, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.geotools:gt-jdbc to 28.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-25158 is resolved across your whole dependency graph.
Workarounds
Until you can upgrade, make sure every query built from user input uses parameterised statements or a prepared-statement API rather than string concatenation, and reduce the database account's privileges so an injected query cannot read or alter data beyond what the feature needs.

Frequently Asked Questions

### Impact GeoTools includes support for OGC Filter expression language parsing, encoding and execution against a range of datastore. SQL Injection Vulnerabilities have been found when executing OGC Filters with JDBCDataStore implementations: 1. ``PropertyIsLike`` filter * Requires PostGIS DataStore with "encode functions" enabled * Or any JDBCDataStore (all relational databases) with String field (no mitigation) 3. ``strEndsWith`` function * Requires PostGIS DataStore with "encode functions" enabled 5. ``strStartsWith`` function * Requires PostGIS DataStore with "encode functio