Threat reportVulnerabilityTL-2026-2037
Unpatched GeoServer Zero-Day SQL Injection (jsonArrayContains, GHSA-mqjf-5f49-2fjh) Under Active Exploitation
An uncoordinated public disclosure on August 12, 2026 by researcher @q1uf3ng exposed a critical unauthenticated SQL injection in GeoTools' jsonArrayContains OGC Filter function against PostGIS DataStores, which can escalate to remote code execution under database-administrator configurations. watchTowr recorded hundreds of scanning/probing exploitation attempts from a small pool of source IPs within hours of disclosure, before a patch (GeoServer 3.0.1/2.28.5/2.27.6, GeoTools gt-jdbc-postgis 35.1/34.5/33.6) shipped on August 14-15, 2026 as GHSA-mqjf-5f49-2fjh.
Key facts
| Identifiers | TL-2026-2037, CVE-2023-25157, CVE-2023-25158 |
|---|---|
| Also known as | GeoServer jsonArrayContains SQL Injection, GHSA-mqjf-5f49-2fjh |
| Severity | CRITICAL |
| CVSS | 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) |
| EPSS | CVE-2023-25157: 85.2% (99.7th percentile); CVE-2023-25158: 1.0% (64.5th percentile) |
| Affected products | OSGeo / GeoSolutions / GeoCat GeoServer; GeoTools org.geotools:gt-jdbc-postgis |
| Weaknesses (CWE) | CWE-89 |
| Malware | Condi, Mirai (JenX variant), SideWalk (ELF), xmrig |
| Tools | China Chopper, RingQ, Stowaway |
| MITRE ATT&CK techniques | T1053.003 Scheduled Task/Job: Cron, T1059 Command and Scripting Interpreter, T1059.001 Command and Scripting Interpreter: PowerShell, T1090.001 Proxy: Internal Proxy, T1136.001 Create Account: Local Account, T1190 Exploit Public-Facing Application, T1197 BITS Jobs, T1213 Data from Information Repositories, T1496 Resource Hijacking, T1505.003 Server Software Component: Web Shell, T1565.001 Data Manipulation: Stored Data Manipulation, T1584.005 Compromise Infrastructure: Botnet and 3 more in the attack flow |
| Motivation | UNKNOWN |
| Target sectors | government administration, defense, science, education, engineering, technology |
| Target regions | Global |
| Detection rules | 9 (1 shown free) |
| Sources | 15 cited sources |
Detection coverage
As of 2026-08-13, Threadlinqs Intelligence publishes 9 detection rule(s) for TL-2026-2037 across Splunk SPL, Microsoft KQL and Sigma, covering 16 indicator(s) of compromise. The whole corpus is readable without an account. Every threat comes with one complete detection in Splunk SPL, Microsoft KQL and Sigma, free for everyone; a free account adds daily TL Creds to unlock the rest. Paid plans add a larger daily allowance, correlation and the MCP server. Threadlinqs MCP server · View plans.
Free detection: GeoServer jsonArrayContains OGC Filter SQL Injection Probing (GHSA-mqjf-5f49-2fjh)
Detects WFS/WMS OGC Filter requests invoking the vulnerable jsonArrayContains(<column>, <pointer>, <value>) function with the <value> argument containing SQL-injection metacharacters or keywords, matching the root-cause exploitation mechanic (unescaped concatenation into generated SQL against a PostGIS DataStore) and watchTowr's post-disclosure scanning wave.
- Languages: Splunk SPL, Microsoft KQL, Sigma
- ATT&CK: T1190, T1595.002
- Data sources: geoserver_access_log, web_proxy, waf, nginx_access_log, apache_access_log
- Severity: high
- Confidence: high
Splunk SPL
index=web sourcetype IN ("access_combined", "geoserver:access", "nginx:access", "apache:access")
| regex uri_query="(?i)jsonArrayContains\s*\("
| eval sqli_pattern=if(match(uri_query, "(?i)(union\s+select|;\s*--|xp_cmdshell|'\s*or\s*'1'\s*=\s*'1|sleep\(|pg_sleep|information_schema|pg_read_file|copy\s+.*\s+to\s+program)"), "high_confidence_sqli", "recon_probe")
| stats count as request_count, min(_time) as first_seen, max(_time) as last_seen, values(uri_query) as sample_queries, values(http_status) as statuses by src_ip, dest_ip, sqli_pattern
| where request_count > 0
| sort -sqli_pattern -request_countMicrosoft KQL
let ProxyLogs = union isfuzzy=true
(AzureDiagnostics | where Category == "ApplicationGatewayAccessLog"),
(W3CIISLog);
ProxyLogs
| where TimeGenerated > ago(24h)
| extend RequestUri = coalesce(column_ifexists("requestUri_s", ""), column_ifexists("csUriQuery", ""))
| where RequestUri has "jsonArrayContains"
| extend SqliPattern = iff(RequestUri matches regex @"(?i)(union\s+select|;\s*--|xp_cmdshell|'\s*or\s*'1'\s*=\s*'1|sleep\(|pg_sleep|information_schema)", "high_confidence_sqli", "recon_probe")
| summarize RequestCount = count(), SampleURIs = make_set(RequestUri, 5) by ClientIP = coalesce(column_ifexists("clientIP_s", ""), column_ifexists("cIP", "")), SqliPattern
| order by SqliPattern desc, RequestCount descSigma
title: GeoServer jsonArrayContains OGC Filter SQL Injection Attempt
id: b1e4a1c2-6f3d-4a9e-9c2f-1a2b3c4d5e6f
status: experimental
description: Detects HTTP requests to a GeoServer WFS/WMS endpoint invoking the vulnerable jsonArrayContains OGC Filter function with SQL-injection metacharacters, per GHSA-mqjf-5f49-2fjh.
references:
- https://github.com/geotools/geotools/security/advisories/GHSA-mqjf-5f49-2fjh
- https://thehackernews.com/2026/08/unpatched-geoserver-zero-day-targeted.html
author: Threadlinqs Team
date: 2026-08-17
tags:
- attack.reconnaissance
- attack.t1595.002
- attack.initial-access
- attack.t1190
- cwe.89
logsource:
category: webserver
detection:
selection_func:
cs-uri-query|contains: 'jsonArrayContains'
selection_sqli:
cs-uri-query|contains:
- 'UNION SELECT'
- ';--'
- 'xp_cmdshell'
- "' OR '1'='1"
- 'sleep('
- 'pg_sleep'
- 'information_schema'
- 'pg_read_file'
condition: selection_func and selection_sqli
falsepositives:
- Legitimate GeoServer clients using jsonArrayContains for valid JSON-array attribute filtering against PostGIS layers
level: highKnown false positives:
- Legitimate GeoServer WFS/WMS clients using jsonArrayContains for valid JSON-array attribute filtering against PostGIS layers — cross-check src_ip against known application service accounts before escalating
Tuning notes: Baseline legitimate jsonArrayContains usage from known internal GIS clients/integrations and suppress those source IPs; tighten sqli_pattern regex to organization-specific PostGIS error-message strings if false positives from automated vulnerability scanners are high.
- GeoServer OGC Filter Fingerprinting via Malformed jsonArrayContains Triggering SQL Errors · unlock with TL Creds
- Web Shell File Write Under GeoServer/Tomcat webapps Directory · unlock with TL Creds
- BITS Job Abuse for C2 Delivery/Data Staging from GeoServer Host · unlock with TL Creds
- GeoServer jsonArrayContains OGC Filter SQL Injection Attempt · unlock with TL Creds
- Local Account Creation or Cron Persistence Following GeoServer Process Activity · unlock with TL Creds
- XMRig Cryptomining Process Launched from GeoServer/Tomcat (Resource Hijacking / Data Manipulation Follow-On) · unlock with TL Creds
- PowerShell/Command-Interpreter Execution Spawned from GeoServer/Tomcat (Post-SQLi RCE Escalation) · unlock with TL Creds
- Stowaway Reverse-Proxy C2 Beacon over TCP/4441 from GeoServer Host · unlock with TL Creds
Indicators of compromise
As of 2026-08-13, Threadlinqs Intelligence tracks 16 indicators of compromise for TL-2026-2037.
Sample indicators (2 of 16)
- File hash:
dff3e75f2f72f8123be76f010d7bd71f5f7508dfac84b2b52a721e779abc50c9 - File hash:
42202a67748c6a5eb735e8241ef144462d9323894579a2f063fa2f82c91eca08
Defanged, TLP:CLEAR. Full set of 16 indicators: unlock with TL Creds.
Technical analysis
On August 12, 2026 at 10:46 UTC, researcher @q1uf3ng publicly disclosed on X — without following coordinated vulnerability disclosure procedures — a critical SQL injection vulnerability in GeoTools' `jsonArrayContains(<column>, <pointer>, <value>)` OGC Filter function. The function writes the caller-supplied `<value>` argument directly into generated SQL without escaping when queried against a PostGIS DataStore (PostGIS 12+) with a String or JSON field, allowing an unauthenticated attacker to inject arbitrary SQL. Under configurations where the backing database account holds administrator privileges, the injection can be leveraged to execute operating-system commands, escalating a data-layer SQL injection into full remote code execution. The GeoTools advisory states "no mitigation is available at this time" and that the previously recommended workaround (prepared statements + disabled PostGIS encode functions) does not stop this instance. Some reporting additionally flags certain H2 DataStore configurations as a further RCE path, though the exact conditions required have not been publicly documented as of August 13, 2026.
The flaw is a regression of the jsonArrayContains SQL-injection class first disclosed on February 20, 2023 as CVE-2023-25157 (GeoServer) / CVE-2023-25158 (GeoTools, GHSA-99c3-qc2q-p94m).
watchTowr began observing exploitation activity within hours of the public disclosure, documenting hundreds of attempts originating from a small pool of source IP addresses. Principal researcher Jake Knott characterized the observed activity as reconnaissance — attackers triggering SQL errors to fingerprint vulnerable, internet-facing GeoServer instances rather than delivering follow-on payloads — but cautioned this is unlikely to remain the case for long given GeoServer's "track record of being targeted and exploited at scale, with multiple vulnerabilities listed in CISA's Known Exploited Vulnerabilities catalog."
That track record includes CVE-2024-36401 (CVSS 9.8, an unrelated GeoTools property-name/XPath eval-injection RCE via Apache Commons JXPath), which CISA added to its KEV catalog on July 15, 2024. Per CISA advisory AA25-266A (published September 23, 2025), threat actors exploited CVE-2024-36401 to gain unauthenticated RCE on a U.S. federal civilian agency's internet-facing GeoServer on July 11, 2024; the intrusion went undetected for roughly three weeks because the web server lacked EDR coverage. During that window the actors used PowerShell and `xp_cmdshell` for execution, pivoted from the web server to an internal SQL server, breached a second internet-facing GeoServer via the same CVE on July 24, 2024, and moved laterally to two additional servers. Persistence was established via China Chopper/PHP web shells, Windows local-account creation (`net user`), and Linux cron jobs; the RingQ evasion loader was used to hinder AV/EDR detection; and Stowaway, a multi-level reverse-proxy utility, tunneled command-and-control traffic over HTTP on TCP/4441. Separately, FortiGuard Labs and other researchers documented mass, opportunistic exploitation of CVE-2024-36401 since mid-2024 — reportedly affecting roughly 7,100 internet-facing GeoServer instances worldwide — to deploy XMRig cryptocurrency miners, the Mirai-variant "JenX" and Condi DDoS botnet malware, the SideWalk backdoor, and residential-proxy monetization tooling.
GeoServer/GeoTools maintainers (Andrea Aime of GeoSolutions and Jody Garnett of GeoCat) shipped fixed releases — GeoServer 3.0.1, 2.28.5, and 2.27.6, and GeoTools gt-jdbc-postgis 35.1, 34.5, and 33.6 — on August 14-15, 2026, publishing the fix as GitHub Security Advisory GHSA-mqjf-5f49-2fjh (CWE-89, CVSS 3.1 9.8: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), tracked via GeoTools JIRA ticket GEOT-7958 / PR #5829. No CVE identifier had been assigned as of the advisory's publication. GeoServer's user base spans government, defense, science, education, engineering, and technology sectors, consistent with its documented history of being a high-value target for opportunistic internet-wide scanning campaigns.
MITRE ATT&CK techniques by tactic:
Persistence
T1053.003 Scheduled Task/Job: Cron; T1136.001 Create Account: Local Account; T1505.003 Server Software Component: Web Shell
Execution
T1059 Command and Scripting Interpreter; T1059.001 Command and Scripting Interpreter: PowerShell
Command and Control
T1090.001 Proxy: Internal Proxy
Initial Access
T1190 Exploit Public-Facing Application
stealth
Collection
T1213 Data from Information Repositories
Impact
T1496 Resource Hijacking; T1565.001 Data Manipulation: Stored Data Manipulation
Resource Development
T1584.005 Compromise Infrastructure: Botnet; T1588.005 Obtain Capabilities: Exploits
Reconnaissance
T1592.002 Gather Victim Host Information: Software; T1595.002 Active Scanning: Vulnerability Scanning
Remediation
Patches
- GeoServer 3.0.1 / 2.28.5 / 2.27.6 (August 14-15, 2026)
- GeoTools org.geotools:gt-jdbc-postgis 35.1 / 34.5 / 33.6
Immediate actions
- Upgrade to GeoServer 3.0.1, 2.28.5, or 2.27.6 (bundles patched GeoTools gt-jdbc-postgis)
- Upgrade standalone GeoTools deployments to gt-jdbc-postgis 35.1, 34.5, or 33.6
- If patching is not immediately possible, remove public internet exposure of GeoServer via VPN, reverse proxy, or IP allowlisting
- Restrict the GeoServer backing database account to least-privilege (non-administrator) permissions to eliminate the RCE escalation path even if the SQLi is triggered
- Deploy EDR on internet-facing GeoServer hosts and centralize/aggregate logs out-of-band — CISA AA25-266A found the compromised federal GeoServer host had neither
Workarounds
- Restrict or disable PostGIS DataStore access to jsonArrayContains-capable String/JSON fields where the function is not required
- Limit the GeoServer database service account to non-administrator privileges to remove the documented RCE escalation path
Longer-term hardening
- Audit all internet-facing GeoServer/GeoTools deployments and inventory PostGIS-backed DataStores using String or JSON fields
- Establish a coordinated-disclosure and rapid-patch SLA for GeoServer given its repeated history of SQLi/RCE zero-days (CVE-2023-25157/25158, CVE-2024-36401, GHSA-mqjf-5f49-2fjh)
- Deploy WAF/reverse-proxy rules to inspect OGC Filter (WFS/WMS) request parameters for jsonArrayContains and other filter-function injection patterns
- Test incident-response plans against a GeoServer-exploitation scenario and validate EDR alerting coverage on all GIS/geospatial hosts, per CISA AA25-266A lessons learned
Affected and fixed versions
- OSGeo / GeoSolutions / GeoCat — GeoServer
Vulnerable versions: < 2.27.6; < 2.28.5; < 3.0.1
Fixed in: 3.0.1; 2.28.5; 2.27.6 - GeoTools — org.geotools:gt-jdbc-postgis
Vulnerable versions: 33.1-33.5; 34.0-34.4; 35.0
Fixed in: 33.6; 34.5; 35.1
Timeline
- CVE-2023-25157 (GeoServer) / CVE-2023-25158 (GeoTools, GHSA-99c3-qc2q-p94m) disclosed: the original OGC Filter/jsonArrayContains SQL injection class, of which this 2026 flaw is a regression.
- CVE-2024-36401, an unrelated GeoTools property-name/XPath eval-injection RCE, disclosed — later exploited in the wild and added to CISA KEV.
- Threat actors exploit CVE-2024-36401 for initial access against a U.S. federal agency's public-facing GeoServer instance, per CISA AA25-266a.
- CISA adds CVE-2024-36401 to the Known Exploited Vulnerabilities catalog, requiring federal remediation by August 5, 2024.
- The same actors breach a second internet-facing GeoServer at the federal agency via CVE-2024-36401 and move laterally to two additional internal servers, per CISA AA25-266A.
- CISA publishes advisory AA25-266A detailing the federal-agency GeoServer breach TTPs (PowerShell, Stowaway proxy C2, China Chopper web shells) and lessons learned (delayed patching, untested IR plans, missing EDR).
- watchTowr begins observing exploitation attempts within hours of disclosure, recording hundreds of scanning/probing attempts from a small pool of source IP addresses.
- Researcher @q1uf3ng publicly discloses the jsonArrayContains SQL injection on X at 10:46 UTC without coordinated vulnerability disclosure.
- The Hacker News, SecurityWeek, CSO Online, Security Affairs, and Field Effect publish coverage of the unpatched zero-day and active exploitation attempts.
- GeoServer 3.0.1, 2.28.5, and 2.27.6 (bundling patched GeoTools gt-jdbc-postgis) are released.
- GitHub Security Advisory GHSA-mqjf-5f49-2fjh formally published for GeoTools gt-jdbc-postgis; no CVE identifier assigned as of publication.
Sources cited
- Unauthenticated SQL injection in the jsonArrayContains filter function against PostGIS layers (GHSA-mqjf-5f49-2fjh) GitHub · Advisory · 2026-08-15
- CISA Shares Lessons Learned from an Incident Response Engagement (CVE-2024-36401 federal agency breach) CISA · Government advisory · 2025-09-23
- OGC Filter Injection Vulnerability Statement (CVE-2023-25157 / CVE-2023-25158) geoserver.org · Vendor report · 2023-02-20
- GeoServer 3.0.1 / GeoServer 2.28.5 / GeoServer 2.27.6 Released discourse.osgeo.org · Vendor report · 2026-08-15
- CVE-2024-36401: Remote Code Execution (RCE) vulnerability in evaluating property name expressions geoserver.org · Vendor report · 2024-09-12
- Threat Actors Exploit GeoServer Vulnerability CVE-2024-36401 Fortinet · Vendor report · 2024-09-17
- Early exploitation attempts observed of GeoServer zero day fieldeffect.com · Blog · 2026-08-13
- CISA Alert AA25-266A: Detecting Malicious Activity Linked to the U.S. Federal Agency Breach via Unpatched GeoServer (CVE-2024-36401) socprime.com · Blog · 2025-09-24
- Response to CISA Advisory (AA25-266A) attackiq.com · Blog · 2025-09-24
- Unpatched GeoServer Zero-Day Targeted in Active Exploitation Attempts, Can Lead to RCE The Hacker News · News · 2026-08-13
- GeoServer Zero-Day Is Already Being Probed. That's the Problem securityaffairs.com · News · 2026-08-13
- Hackers Exploiting Unpatched GeoServer Zero-Day SecurityWeek · News · 2026-08-13
- Attackers target zero-day vulnerability in geospatial data platform GeoServer csoonline.com · News · 2026-08-13
- Multiple malware families delivered exploiting GeoServer GeoTools flaw CVE-2024-36401 securityaffairs.com · News · 2024-09-18
- GeoServer Exploits, PolarEdge, and Gayfemboy Push Cybercrime Beyond Traditional Botnets The Hacker News · News · 2025-08-01
Previous and next in vulnerability
Drafted by the Threadlinqs research pipeline from 15 sources; published ; last updated —.