Apache Karaf: Missing authorization on the jdbc:* shell command scope allows privilege escalation to remote code execution via jdbc:ds-create
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.
- Products
- Not specified
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-91048
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 3 Nov 2026, 14:13 UTC · Revision 1
Source evidence
Apache Karaf: Missing authorization on the jdbc:* shell command scope allows privilege escalation to remote code execution via jdbc:ds-create
core-osv · Original sourcePublished 29 Sept 2026, 08:34 UTC
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.
osv:CVE-2026-91048
Complete source record
{
"id": "9b93aad052e8a508423046a3ca5fa5e4168b71f46da95ad8ee37693eb2a647dc",
"url": "https://osv.dev/vulnerability/CVE-2026-91048",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Apache Karaf: Missing authorization on the jdbc:* shell command scope allows privilege escalation to remote code execution via jdbc:ds-create",
"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.",
"evidence": "osv:CVE-2026-91048",
"products": [],
"severity": "critical",
"structured": {
"id": "CVE-2026-91048",
"aliases": [
"CVE-2026-91048"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"repo": "https://github.com/apache/karaf",
"type": "GIT",
"events": [
{
"introduced": "0"
},
{
"fixed": "189048fff3422afaadcbbb57d95b257cb35248ad"
}
],
"database_specific": {
"extracted_events": [
{
"cpe": "cpe:2.3:a:apache:karaf:*:*:*:*:*:*:*:*",
"range": [
{
"introduced": "0"
},
{
"fixed": "4.4.12"
}
],
"source": "CPE_RANGE"
}
]
}
}
],
"versions": [
"karaf-4.4.8",
"karaf-4.4.7",
"karaf-4.4.6",
"karaf-4.4.5",
"karaf-4.4.4",
"karaf-4.4.3",
"karaf-4.4.2",
"karaf-4.4.1",
"karaf-4.4.0",
"karaf-4.3.3",
"karaf-4.3.2",
"karaf-4.3.1",
"karaf-4.3.0",
"karaf-4.3.0.RC1",
"karaf-4.2.3",
"karaf-4.2.2",
"karaf-4.2.1",
"karaf-4.2.0",
"karaf-4.2.0.M2",
"karaf-4.2.0.M1",
"karaf-4.1.1",
"karaf-4.1.0",
"karaf-4.0.4",
"karaf-4.0.3",
"karaf-4.0.2",
"karaf-4.0.1",
"karaf-4.0.0.M2",
"karaf-4.0.0.M1",
"karaf-3.0.0"
],
"database_specific": {
"source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-91048.json"
}
}
],
"modified": "2026-10-28T02:30:29.198826428Z",
"provider": "osv",
"references": [
"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/91xxx/CVE-2026-91048.json",
"https://lists.apache.org/thread/ph3867mxh2tft75w0o1hpn10f5mbmw32",
"https://nvd.nist.gov/vuln/detail/CVE-2026-91048"
],
"provider_metadata": {
"cwe_ids": [
"CWE-862"
],
"cna_assigner": "apache",
"unresolved_ranges": [
{
"extracted_events": [
{
"range": [
{
"fixed": "4.4.12"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
}
]
}
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/91xxx/CVE-2026-91048.json"
}
},
"related_cves": [
{
"value": "CVE-2026-91048",
"evidence": "/id"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 496273,
"published_at": "2026-09-29T08:34:47.193+00:00"
}