Skip to content
Noroxi
NVD / CVE Program· CNA mitre

CVE-2023-35042: GeoServer 2, in some configurations, allows remote attackers to execute arbitrary code via java.lang.Runtime.getRuntime().exec in…

CriticalCVSS 9.8 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Plan (action score 52/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 44.8% (FIRST EPSS); higher than 98.7% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: org.geoserver:gs-wfs (Maven) 2.19.6, 2.20.4, 2.18.6; org.geoserver:gs-wms (Maven) 2.19.6, 2.20.4, 2.18.6; org.geoserver:gs-wps (Maven) 2.19.6, 2.20.4, 2.18.6.

Add it to your regular patch cycle. Upgrade to org.geoserver:gs-wfs (Maven) 2.19.6, 2.20.4, 2.18.6; org.geoserver:gs-wms (Maven) 2.19.6, 2.20.4, 2.18.6; org.geoserver:gs-wps (Maven) 2.19.6, 2.20.4, 2.18.6 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

GeoServer 2, in some configurations, allows remote attackers to execute arbitrary code via java.lang.Runtime.getRuntime().exec in wps:LiteralData within a wps:Execute request, as exploited in the wild in June 2023. NOTE: the vendor states that they are unable to reproduce this in any version.

Published
Jun 12, 2023
Updated
Jun 17, 2026
EPSS
44.8% · 98th percentile
CWE
—

Report tools

JSON

Action score

52

Plan

Add it to your regular patch cycle.

CVSS
39 / 40 · 9.8 / 10
CISA KEV
0 / 30 · Not listed
EPSS
13 / 30 · 44.8%

CISA SSVC decision

Exploitation
none
Automatable
yes
Technical impact
total

Vulnrichment: CISA's decision-tree inputs.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2023-35042

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools
Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
geoservergeoserver

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • geoserver geoserver2.0.0 and later

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Mavenorg.geoserver:gs-wfsfrom 2.19.0 · before 2.19.62.19.6
Mavenorg.geoserver:gs-wfsfrom 2.20.0 · before 2.20.42.20.4
Mavenorg.geoserver:gs-wfsbefore 2.18.62.18.6
Mavenorg.geoserver:gs-wmsfrom 2.19.0 · before 2.19.62.19.6
Mavenorg.geoserver:gs-wmsfrom 2.20.0 · before 2.20.42.20.4
Mavenorg.geoserver:gs-wmsbefore 2.18.62.18.6
Mavenorg.geoserver:gs-wpsfrom 2.19.0 · before 2.19.62.19.6
Mavenorg.geoserver:gs-wpsfrom 2.20.0 · before 2.20.42.20.4
Mavenorg.geoserver:gs-wpsbefore 2.18.62.18.6

Other highest-scoring records for the same primary product.

  • CVE-2024-36401Remote Code Execution (RCE) vulnerability in evaluating property name expressions in GeoserverKEV
    99Now
  • CVE-2025-58360GeoServer is vulnerable to an Unauthenticated XML External Entities (XXE) attack via WMS GetMap featureKEV
    87Now
  • CVE-2024-24749Classpath resource disclosure in GWC Web Resource API on Windows / Tomcat
    30Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2008-7227Sep 14, 2009 · PartialBufferOutputStream2 in GeoServer before 1.6.1 and 1.7.0-beta1 attempts to flush buffer contents even when it is handling an "in…
    20Monitor
  • Later →CVE-2023-41877Mar 20, 2024 · GeoServer log file path traversal vulnerability
    28Monitor
  • Later →CVE-2023-51444Mar 20, 2024 · GeoServer arbitrary file upload vulnerability in REST Coverage Store API
    29Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Maven:org.geoserver:gs-wfs2.18.6Package registry (OSV)
Maven:org.geoserver:gs-wfs2.19.6Package registry (OSV)
Maven:org.geoserver:gs-wfs2.20.4Package registry (OSV)
Maven:org.geoserver:gs-wms2.18.6Package registry (OSV)
Maven:org.geoserver:gs-wms2.19.6Package registry (OSV)
Maven:org.geoserver:gs-wms2.20.4Package registry (OSV)
Maven:org.geoserver:gs-wps2.18.6Package registry (OSV)
Maven:org.geoserver:gs-wps2.19.6Package registry (OSV)
Maven:org.geoserver:gs-wps2.20.4Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
high · data or configuration can be modified
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
High
Integrity impact
High
Availability impact
High

Weakness class (CWE)

—

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

Show all references (1 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records