Skip to content
VulniPulse
Advisory severityCritical9.8Apache Software Foundation

Critical [CVE-2026-91048] The jdbc shell command scope shipped no org.apache.karaf.command.acl.jdbc.cfg

This critical-severity Apache Software Foundation advisory covers CVE-2026-91048; related products: Apache Karaf.

Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.

CVE-2026-91048 Source published Source updated

VulniPulse record published Record updated

Related products & platforms
Apache Software FoundationUnclassified
Open source advisory

Android app · Google Play

Monitor future Apache Software Foundation CVEs from your phone.

Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 32 official vendor sources and 160+ reviewed platform categories.

Matching phone alertsOptional email delivery

Summary

The jdbc shell command scope shipped no org.apache.karaf.command.acl.jdbc.cfg.

Karaf's command guard (SecuredSessionFactoryImpl) treats a command with no matching ACL rule as allowed, so any authenticated shell session (including one holding only the viewer role) could run every jdbc:* command. jdbc:ds-create stores a fully attacker-controlled JDBC URL into a pax-jdbc-config factory Configuration with no validation. pax-jdbc-config reactively turns that into a live DataSource.

Several JDBC drivers run code or SQL at connection time based on URL parameters (e.g. H2 INIT=RUNSCRIPT), so a viewer-level shell user could reach arbitrary code execution, bypassing the admin-role gate that already protects shell:exec.

This is a privilege-escalation-to-RCE chain, not merely an "admin misconfiguration".

The same applies to jms:* shell commands.

Affected versions
  • Apache Karaf before 4.4.12

Official advisory · high-confidence parse· fetched 7 days ago·verify at source

Fixed versions
  • 4.4.12

Official advisory · high-confidence parse· fetched 7 days ago·verify at source

Mitigation

Upgrade to a fixed release: 4.4.12. That is the remediation for this advisory.

The vendor advisory may list additional interim mitigations or workarounds not captured here — review it before change work.

Official advisory · high-confidence parse· fetched 7 days ago·verify at source

Discussion(0)

No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.

Sign in to join the discussion.