# CVE-2019-0226: Apache Karaf vulnerable to relative path traversal

> An attacker can traverse directories and overwrite files via the Karaf Config service install method, requiring an upgrade to mitigate.

- **Severity:** Medium 4.9 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-fjw4-39pg-vf4f

## What is CVE-2019-0226?

CVE-2019-0226 is a medium-severity path traversal vulnerability in Apache Karaf, published on 9 May 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Apache Karaf Config service provides a install method (via service or MBean) that could be used to travel in any directory and overwrite existing file. The vulnerability is low if the Karaf process user has limited permission on the filesystem. Any Apache Karaf version before 4.2.5 is impacted. User should upgrade to Apache Karaf 4.2.5 or later.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2019-0226?

2 open source packages ship an affected version, including org.apache.karaf.config:org.apache.karaf.config.core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `org.apache.karaf.config:org.apache.karaf.config.core` | Maven | All versions | 4.2.5 |
| `org.apache.karaf.config:org.apache.karaf.config.core` | Maven | All versions | 4.2.5 |

Products: Apache Karaf.

## How do I fix CVE-2019-0226?

Upgrade org.apache.karaf.config:org.apache.karaf.config.core to 4.2.5 or later.

## Is CVE-2019-0226 being exploited?

There is no known exploitation of CVE-2019-0226 in the wild and no public exploit code.

## Other vulnerabilities in Apache Karaf

- [CVE-2026-91012](https://insights.sbomify.com/CVE-2026-91012/): Apache Karaf: Path Traversal in Config Service Allows Manager-to-Admin Privilege Escalation (critical 9.8)
- [CVE-2026-91048](https://insights.sbomify.com/CVE-2026-91048/): Missing authorization in Apache Karaf (critical 9.8)
- [CVE-2022-40145](https://insights.sbomify.com/CVE-2022-40145/): Apache Karaf: JDBC JAAS LDAP injection (critical 9.8)
- [CVE-2018-11788](https://insights.sbomify.com/CVE-2018-11788/): XML External Entity Reference in Apache Karaf (critical 9.8)
- [CVE-2026-92142](https://insights.sbomify.com/CVE-2026-92142/): Apache Karaf: Authorization bypass in JMX MBean lifecycle operations (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-0226 and fix it if it is affected.

What it is: CVE-2019-0226 is a medium-severity path traversal vulnerability in Apache Karaf, published on 9 May 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-0226 in the wild and no public exploit code.

Affected packages and fixed versions:
- org.apache.karaf.config:org.apache.karaf.config.core (Maven): affected all versions; fixed in 4.2.5
- org.apache.karaf.config:org.apache.karaf.config.core (Maven): affected all versions; fixed in 4.2.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-0226/ (Markdown: https://insights.sbomify.com/CVE-2019-0226/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-0226
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-0226
- OSV: https://osv.dev/vulnerability/CVE-2019-0226

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-0226/
Summaries are generated and may contain mistakes; the official description above is the record.