# CVE-2018-11786: Improper Privilege Management in Apache Karaf

> Users with Karaf console access can read and write arbitrary files on the host filesystem if the SSH service is enabled without strict chroot or security manager policies.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Sep 2018
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-9448-c9wq-jg9v

## What is CVE-2018-11786?

CVE-2018-11786 is a high-severity vulnerability in Apache Karaf, published on 18 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

In Apache Karaf prior to 4.2.0 release, if the sshd service in Karaf is left on so an administrator can manage the running instance, any user with rights to the Karaf console can pivot and read/write any file on the file system to which the Karaf process user has access. This can be locked down a bit by using chroot to change the root directory to protect files outside of the Karaf install directory; it can be further locked down by defining a security manager policy that limits file system access to those directories beneath the Karaf home that are necessary for the system to run. However, this still allows anyone with ssh access to the Karaf process to read and write a large number of files as the Karaf process user.

Weakness: CWE-269 (Improper Privilege Management)

## Which versions are affected by CVE-2018-11786?

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


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

Products: Apache Karaf.

## How do I fix CVE-2018-11786?

Upgrade org.apache.karaf:apache-karaf to 4.2.0 or later.

## Is CVE-2018-11786 being exploited?

There is no known exploitation of CVE-2018-11786 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-2018-11786 and fix it if it is affected.

What it is: CVE-2018-11786 is a high-severity vulnerability in Apache Karaf, published on 18 Sep 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-11786 in the wild and no public exploit code.

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

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-2018-11786/ (Markdown: https://insights.sbomify.com/CVE-2018-11786/index.md)
```

## Sources

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

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