Eclipse Jetty Server generates error message containing sensitive information

Exploitation

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

CVSS

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

EPSS

• CVE-2018-12536: 4.23% estimated exploitation activity in the next 30 days; percentile 91.04 (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.

In Eclipse Jetty Server, all 9.x versions, on webapps deployed using default Error Handling, when an intentionally bad query arrives that doesn't match a dynamic url-pattern, and is eventually handled by the DefaultServlet's static file serving, the bad characters can trigger a java.nio.file.InvalidPathException which includes the full path to the base resource directory that the DefaultServlet and/or webapp is using. If this InvalidPathException is then handled by the default Error Handler, the InvalidPathException message is included in the error response, revealing the full server path to the requesting system.

Published by the source

19 Oct 2018, 16:15 UTC

Last modified by the source

18 Aug 2023, 16:47 UTC

Source last checked

26 Oct 2026, 16:12 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-9rgv-h7x4-qw8g

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

# Patch Next advisory brief: CVE-2018-12536

Advisory: Eclipse Jetty Server generates error message containing sensitive information
IDs: CVE-2018-12536, GHSA-9rgv-h7x4-qw8g
Record: https://patchnext.com/advisories/cve-2018-12536 (revision 1, source checked 26 Oct 2026, 16:12 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.eclipse.jetty:jetty-server 9.4.11.v20180605, 9.3.24.v20180605. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.eclipse.jetty:jetty-server: affected >= 9.4.0, <= 9.4.10.v20180503; >= 9.0.0, <= 9.3.23.v20180228; fixed in 9.4.11.v20180605, 9.3.24.v20180605

## Suggested inspection (read-only)
- Maven org.eclipse.jetty:jetty-server: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.eclipse.jetty:jetty-server.
- 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-9rgv-h7x4-qw8g (GitHub-reviewed advisory GHSA-9rgv-h7x4-qw8g lists affected ranges: Maven org.eclipse.jetty:jetty-server >=9.4.0 =9.0.0 <=9.3.23.v20180228)

Commands are suggestions: review each one before running it.