GeoServer log file path traversal vulnerability

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2023-41877: 0.84% estimated exploitation activity in the next 30 days; percentile 57.93 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Impact This vulnerability requires GeoServer Administrator with access to the admin console to misconfigured the Global Settings for log file location to an arbitrary location. This can be used to read files via the admin console GeoServer Logs page. It is also possible to leverage RCE or cause denial of service by overwriting key GeoServer files. Patches This issue has been addressed in GeoServer 3.0.0: The Global Settings page can no longer be used to specify log file location The application parameter GEOSERVERLOGLOCATION mechanism (outlined below) is now the only approach available to customize the log file location. Workarounds A system administrator responsible for running GeoServer can define the GEOSERVERLOGFILE parameter, preventing the global setting provided from being used. The GEOSERVERLOGLOCATION parameter can be set as system property, environment variable, or servlet context parameter. Environmental variable: System property: Web application WEB-INF/web.xml: Tomcat…

Published by the source

20 Mar 2024, 14:45 UTC

Last modified by the source

20 Jul 2026, 13:39 UTC

Source last checked

26 Oct 2026, 16:54 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-8g7v-vjrc-x4g5

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2023-41877

Advisory: GeoServer log file path traversal vulnerability
IDs: CVE-2023-41877, GHSA-8g7v-vjrc-x4g5
Record: https://patchnext.com/advisories/cve-2023-41877 (revision 1, source checked 26 Oct 2026, 16:54 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.geoserver:gs-main: affected <= 2.23.4

## Suggested inspection (read-only)
- Maven org.geoserver:gs-main: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.geoserver:gs-main.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8g7v-vjrc-x4g5 (GitHub-reviewed advisory GHSA-8g7v-vjrc-x4g5 lists affected ranges: Maven org.geoserver:gs-main >=0 <=2.23.4)

Commands are suggestions: review each one before running it.