Quick answers
- Is CVE-2026-92142 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-92142 being exploited in the wild.
- How severe is CVE-2026-92142?
- Informational severity, published 29 September 2026.
- Which products and versions are affected?
- Apache Karaf before 4.4.12 and before 4.5.0.
- Is there a fix for CVE-2026-92142?
- 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-92142 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-92142?
- 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 KarafMBeanServerGuard proxy enforces role-based access control (RBAC) only on a hardcoded list of MBean operation names (invoke, getAttribute, setAttribute, etc.) but omits lifecycle methods createMBean, registerMBean, and unregisterMBean. An authenticated user can abuse this gap to instantiate javax.management.loading.MLet, a standard JDK MBean with remote classloading capability; the getMBeansFromURL() method is accessible via the default ACL rule "get*=viewer" despite being a code execution vector. An attacker with any valid JMX credential can chain these to achieve RCE.
Affected products
- Apache Karaf before 4.4.12 and before 4.5.0
Timeline
- 2026-09-29: disclosed