Analysis and contextual insights are available on OpenCVE Cloud.
Vendor Workaround
1. Bind all topics to KEKs — remove PASSTHROUGH_UNENCRYPTED as unresolvedKeyPolicy. Explicitly configure kekSelector to match every topic. 2. Restrict outbound network access — use Kubernetes NetworkPolicy to limit proxy pod egress to only legitimate Azure Key Vault endpoints on port 443. 3. Monitor KMS call patterns — alert on unwrap requests targeting unexpected vault hostnames.
Tracking
Sign in to view the affected projects.
No advisories yet.
Tue, 20 Oct 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 20 Oct 2026 13:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | The Azure Key Vault KMS provider in Kroxylicious accepts an untrusted vaultName from wire-deserialized EDEK bytes without format validation, enabling SSRF that exfiltrates the proxy's Azure bearer token to an attacker-controlled host. Token replay against the real Key Vault defeats the entire record-encryption trust model. | |
| Title | Kroxylicious-kms-provider-azure-key-vault-kms: streams for apache kafka kroxylicious: azure key vault ssrf exfiltrates bearer token via untrusted edek vaultname | |
| First Time appeared |
Redhat
Redhat amq Streams |
|
| Weaknesses | CWE-918 | |
| CPEs | cpe:/a:redhat:amq_streams:3 | |
| Vendors & Products |
Redhat
Redhat amq Streams |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: redhat
Published:
Updated: 2026-10-20T13:40:36.464Z
Reserved: 2026-10-06T07:03:52.238Z
Link: CVE-2026-105941
Updated: 2026-10-20T13:40:31.659Z
Status : Awaiting Analysis
Published: 2026-10-20T13:16:39.457
Modified: 2026-10-20T15:03:59.857
Link: CVE-2026-105941
No data.
OpenCVE Enrichment
Updated: 2026-10-20T14:15:14Z