# 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.

- **Published:** 2026-08-13T00:00:00Z
- **Last reviewed:** 2026-08-13T00:00:00Z
- **Canonical:** https://intel.threadlinqs.com/threat/TL-2026-2037
- **Card image:** https://intel.threadlinqs.com/og/threat/threat-intel-geoserver-jsonarraycontains-injection-tl-2026-2037.webp?v=31a723d3 (Threadlinqs threat intel: GHSA-mqjf-5f49-2fjh GeoServer Injection: Detection & IOCs (TL-2026-2037) — Critical severity, 16 IOCs, 9 detection rules.)
- **ID:** TL-2026-2037
- **Severity:** CRITICAL (CVSS 9.8)
- **Category:** VULNERABILITY
- **Status:** ACTIVE
- **Detections:** 9 (1 shown free below) · **IOCs:** 16 (2 shown free below)
- **CVEs:** CVE-2023-25157, CVE-2023-25158

## Description

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

- T1595.002 Active Scanning: Vulnerability Scanning
- T1592.002 Gather Victim Host Information: Software
- T1588.005 Obtain Capabilities: Exploits
- T1584.005 Compromise Infrastructure: Botnet
- T1190 Exploit Public-Facing Application
- T1059 Command and Scripting Interpreter
- T1059.001 Command and Scripting Interpreter: PowerShell
- T1505.003 Server Software Component: Web Shell
- T1136.001 Create Account: Local Account
- T1053.003 Scheduled Task/Job: Cron
- T1213 Data from Information Repositories
- T1090.001 Proxy: Internal Proxy
- T1197 BITS Jobs
- T1496 Resource Hijacking
- T1565.001 Data Manipulation: Stored Data Manipulation

## Free detection (Splunk SPL, Microsoft KQL, Sigma)

**GeoServer jsonArrayContains OGC Filter SQL Injection Probing (GHSA-mqjf-5f49-2fjh)** (`TL-2026-2037-SPL-001`)

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

```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_count
```

### Microsoft KQL

```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 desc
```

### Sigma

```yaml
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: high
```

**Known 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.

### 8 more detection rules (Splunk SPL, Microsoft KQL, Sigma), unlock with TL Creds

- GeoServer OGC Filter Fingerprinting via Malformed jsonArrayContains Triggering SQL Errors (locked: unlock with TL Creds)
- Web Shell File Write Under GeoServer/Tomcat webapps Directory (locked: unlock with TL Creds)
- BITS Job Abuse for C2 Delivery/Data Staging from GeoServer Host (locked: unlock with TL Creds)
- GeoServer jsonArrayContains OGC Filter SQL Injection Attempt (locked: unlock with TL Creds)
- Local Account Creation or Cron Persistence Following GeoServer Process Activity (locked: unlock with TL Creds)
- XMRig Cryptomining Process Launched from GeoServer/Tomcat (Resource Hijacking / Data Manipulation Follow-On) (locked: unlock with TL Creds)
- PowerShell/Command-Interpreter Execution Spawned from GeoServer/Tomcat (Post-SQLi RCE Escalation) (locked: unlock with TL Creds)
- Stowaway Reverse-Proxy C2 Beacon over TCP/4441 from GeoServer Host (locked: unlock with TL Creds)

Sign up free to unlock the detection rules: https://threadlinqs.com/?modal=signup

## Sample indicators (2 of 16)

Defanged, TLP:CLEAR.

- File hash: `dff3e75f2f72f8123be76f010d7bd71f5f7508dfac84b2b52a721e779abc50c9`
- File hash: `42202a67748c6a5eb735e8241ef144462d9323894579a2f063fa2f82c91eca08`

Full set of 16 indicators unlocks with TL Creds: https://threadlinqs.com/tl-creds

## Sources

- [Unpatched GeoServer Zero-Day Targeted in Active Exploitation Attempts, Can Lead to RCE](https://thehackernews.com/2026/08/unpatched-geoserver-zero-day-targeted.html)
- [Unauthenticated SQL injection in the jsonArrayContains filter function against PostGIS layers (GHSA-mqjf-5f49-2fjh)](https://github.com/geotools/geotools/security/advisories/GHSA-mqjf-5f49-2fjh)
- [GeoServer Zero-Day Is Already Being Probed. That's the Problem](https://securityaffairs.com/197216/hacking/geoserver-zero-day-is-already-being-probed-thats-the-problem.html)
- [Hackers Exploiting Unpatched GeoServer Zero-Day](https://www.securityweek.com/hackers-exploiting-unpatched-geoserver-zero-day/)
- [Attackers target zero-day vulnerability in geospatial data platform GeoServer](https://www.csoonline.com/article/4209388/attackers-target-zero-day-vulnerability-in-geospatial-data-platform-geoserver.html)
- [Early exploitation attempts observed of GeoServer zero day](https://fieldeffect.com/blog/early-exploitation-attempts-observed-geoserver-zero-day)
- [OGC Filter Injection Vulnerability Statement (CVE-2023-25157 / CVE-2023-25158)](https://geoserver.org/vulnerability/2023/02/20/ogc-filter-injection.html)
- [GeoServer 3.0.1 / GeoServer 2.28.5 / GeoServer 2.27.6 Released](https://discourse.osgeo.org/t/geoserver-3-0-1-geoserver-2-28-5-geoserver-2-27-6-released/154874)
- [CISA Shares Lessons Learned from an Incident Response Engagement (CVE-2024-36401 federal agency breach)](https://www.cisa.gov/news-events/cybersecurity-advisories/aa25-266a)
- [CVE-2024-36401: Remote Code Execution (RCE) vulnerability in evaluating property name expressions](https://geoserver.org/vulnerability/2024/09/12/cve-2024-36401.html)
- [CISA Alert AA25-266A: Detecting Malicious Activity Linked to the U.S. Federal Agency Breach via Unpatched GeoServer (CVE-2024-36401)](https://socprime.com/blog/latest-threats/detect-attack-using-cve-2024-36401-aa25-266a-cisa-alert/)
- [Response to CISA Advisory (AA25-266A)](https://www.attackiq.com/2025/09/24/response-to-cisa-advisory-aa25-266a/)
- [Threat Actors Exploit GeoServer Vulnerability CVE-2024-36401](https://www.fortinet.com/blog/threat-research/threat-actors-exploit-geoserver-vulnerability-cve-2024-36401)
- [Multiple malware families delivered exploiting GeoServer GeoTools flaw CVE-2024-36401](https://securityaffairs.com/168197/malware/geoserver-geotools-flaw-cve-2024-36401-malware.html)
- [GeoServer Exploits, PolarEdge, and Gayfemboy Push Cybercrime Beyond Traditional Botnets](https://thehackernews.com/2025/08/geoserver-exploits-polaredge-and.html)

## Full data

The other 8 detection rules (Splunk SPL / Microsoft KQL / Sigma) unlock with TL Creds; a free account includes daily creds: https://threadlinqs.com/?modal=signup
Indicator values unlock with TL Creds, at a lower price on Red and Purple; AI agents can query rules and IOCs through the Threadlinqs MCP server (Purple): https://intel.threadlinqs.com/mcp

Canonical: https://intel.threadlinqs.com/threat/TL-2026-2037
