Path traversal in Apache Karaf

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-2022-22932: 2.75% estimated exploitation activity in the next 30 days; percentile 86.25 (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.

Apache Karaf obr: commands and run goal on the karaf-maven-plugin have partial path traversal which allows to break out of expected folder. The risk is low as obr: commands are not very used and the entry is set by user. This has been fixed in revision: https://gitbox.apache.org/repos/asf?p=karaf.git;h=36a2bc4 https://gitbox.apache.org/repos/asf?p=karaf.git;h=52b70cf Mitigation: Apache Karaf users should upgrade to 4.2.15 or 4.3.6 or later as soon as possible, or use correct path. JIRA Tickets: https://issues.apache.org/jira/browse/KARAF-7326

Published by the source

28 Jan 2022, 22:25 UTC

Last modified by the source

3 Feb 2023, 05:05 UTC

Source last checked

26 Oct 2026, 16:10 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-544x-2jx9-4pfg

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

# Patch Next advisory brief: CVE-2022-22932

Advisory: Path traversal in Apache Karaf
IDs: CVE-2022-22932, GHSA-544x-2jx9-4pfg
Record: https://patchnext.com/advisories/cve-2022-22932 (revision 1, source checked 26 Oct 2026, 16:10 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.apache.karaf:apache-karaf 4.3.6, 4.2.15. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.karaf:apache-karaf: affected >= 4.3.0, < 4.3.6; < 4.2.15; fixed in 4.3.6, 4.2.15

## Suggested inspection (read-only)
- Maven org.apache.karaf:apache-karaf: 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.karaf:apache-karaf.
- 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-544x-2jx9-4pfg (GitHub-reviewed advisory GHSA-544x-2jx9-4pfg lists affected ranges: Maven org.apache.karaf:apache-karaf >=4.3.0 =0 <4.2.15)

Commands are suggestions: review each one before running it.