Quick answers
- Is CVE-2026-91085 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-91085 being exploited in the wild.
- How severe is CVE-2026-91085?
- Informational severity, published 29 September 2026.
- Which products and versions are affected?
- Apache Karaf all versions with the default ACL configuration.
- Is there a fix for CVE-2026-91085?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-91085 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-91085?
- Check whether you run Apache Karaf at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The config:install shell command lacks an ACL rule and fails open when no matching rule is found, allowing any authenticated user to execute it. The command accepts a URL and fetches content into the Karaf etc directory with optional file override, and while path traversal is blocked, the etc directory contains all security-relevant configuration files including ACL definitions. An attacker can craft a malicious CFG file and upload it via config:install to override the ACL rules governing command authorization.
Affected products
- Apache Karaf all versions with the default ACL configuration
Timeline
- 2026-09-29: disclosed