ZeroHour
oss-securitypublished ()ingested

CVE-2026-92230: Apache Karaf: Improper release of ClassLoader references via static ThreadLocal caching

AI summary · glm-5.3-flash

Apache Karaf versions before 4.4.11 pin bundle ClassLoaders in memory via static ThreadLocal caching, causing leaks (CVE-2026-92230, moderate).

Apache Karaf's XmlUtils caches XML parser and transformer factories in static ThreadLocal fields on long-lived container threads. Because ThreadLocal values outlive the OSGi bundles that created them, repeated bundle or feature install, update, or refresh operations leave successive bundle ClassLoaders pinned in memory and unreachable for garbage collection. The flaw affects Apache Karaf before 4.4.11 and is rated moderate severity.

  • Fixed in Apache Karaf 4.4.11; earlier versions are affected.
  • XML parser/transformer factories cached in static ThreadLocal fields on container threads.
  • Repeated bundle install, update, or refresh operations accumulate unreachable ClassLoaders.

Vulnerabilities mentionedAll →

CVEVulnerabilityCVSSEPSSFlagsAffectedExposurePublished
CVE-2026-92230
Metaspace-Exhaustion DoS in Apache Karaf via ClassLoader Leak in XmlUtils

Apache Karaf's XmlUtils caches XML parser and transformer factories in static ThreadLocal fields on long-lived container threads. Because ThreadLocal values outlive the OSGi bundle that created them, each bundle or feature install, update, or refresh operation pins that bundle's ClassLoader in memory where it can never be garbage collected. Repeated dynamic lifecycle operations therefore drive unbounded Metaspace growth until the Karaf instance exhausts memory and is denied service. Exploitation requires the ability to trigger repeated bundle/feature operations, meaning an attacker would typically need management access (Karaf shell, JMX, or web console) or control of an automated deployment pipeline, though internal CI/CD-driven deployments can be affected without any attacker. The issue is not yet CVSS-scored, is not in CISA KEV, and no public proof-of-concept or in-the-wild exploitation is known.

Do: Upgrade Apache Karaf to the patched release referenced in the Apache security advisory once published, since no fixed version is stated in the available data. Until patched, restrict Karaf shell, JMX, and Hawtio/webpack console access to trusted administrators and avoid frequent automated bundle/feature install-update-refresh cycles in production. Monitor JVM Metaspace consumption and restart instances showing steady growth.

7.5
  • Apache Software Foundation Apache Karaf
moderate≈1,000–10,000 internet-exposed Karaf/Hawtio management instances (public scan estimates), with far more internal and embedded deployments
Full article

Posted by Jean-Baptiste Onofré on Sep 17 Severity: moderate Affected versions: - Apache Karaf before 4.4.11 Description: Apache Karaf's XmlUtils cached XML parser/transformer factories in static ThreadLocal fields on long-lived container threads. Because a ThreadLocal value outlives the OSGi bundle that created it, repeated bundle or feature install, update, or refresh operations can leave successive bundle ClassLoader's pinned in memory and unreachable for garbage...

This source does not provide full text. Read it at seclists.org.