Quick answers
- Is CVE-2026-91012 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-91012 being exploited in the wild.
- How severe is CVE-2026-91012?
- Informational severity, published 29 September 2026.
- Which products and versions are affected?
- Apache Karaf all versions before fix.
- Is there a fix for CVE-2026-91012?
- 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-91012 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-91012?
- 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
ConfigRepositoryImpl.update() and createFactoryConfiguration() derive target file paths from caller-supplied input (either a felix.fileinstall.filename property or a PID containing ".." segments) without validating that the result remains within ${karaf.etc}. The vulnerability is reachable by any caller holding the "manager" role under Karaf's default ACL. An attacker can write attacker-controlled content to any file writable by the Karaf process, including ACL configuration files and user credential files normally restricted to administrators.
Affected products
- Apache Karaf all versions before fix
Timeline
- 2026-09-29: disclosed