Apache Sling Servlets Resolver executes malicious code via path traversal

Exploitation

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

CVSS

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

EPSS

• CVE-2024-23673: 1.32% estimated exploitation activity in the next 30 days; percentile 70.91 (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.

Malicious code execution via path traversal in Apache Software Foundation Apache Sling Servlets Resolver.This issue affects all version of Apache Sling Servlets Resolver before 2.11.0. However, whether a system is vulnerable to this attack depends on the exact configuration of the system. If the system is vulnerable, a user with write access to the repository might be able to trick the Sling Servlet Resolver to load a previously uploaded script. Users are recommended to upgrade to version 2.11.0, which fixes this issue. It is recommended to upgrade, regardless of whether your system configuration currently allows this attack or not.

Published by the source

6 Feb 2024, 12:30 UTC

Last modified by the source

13 Feb 2025, 19:31 UTC

Source last checked

26 Oct 2026, 16:35 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-h2rq-qhr7-53gm

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

# Patch Next advisory brief: CVE-2024-23673

Advisory: Apache Sling Servlets Resolver executes malicious code via path traversal
IDs: CVE-2024-23673, GHSA-h2rq-qhr7-53gm
Record: https://patchnext.com/advisories/cve-2024-23673 (revision 1, source checked 26 Oct 2026, 16:35 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.sling:org.apache.sling.servlets.resolver 2.11.0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.sling:org.apache.sling.servlets.resolver: affected < 2.11.0; fixed in 2.11.0

## Suggested inspection (read-only)
- Maven org.apache.sling:org.apache.sling.servlets.resolver: 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.apache.sling:org.apache.sling.servlets.resolver.
- 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-h2rq-qhr7-53gm (GitHub-reviewed advisory GHSA-h2rq-qhr7-53gm lists affected ranges: Maven org.apache.sling:org.apache.sling.servlets.resolver >=0 <2.11.0)

Commands are suggestions: review each one before running it.