CVE-2026-105941 PUBLISHED

Kroxylicious-kms-provider-azure-key-vault-kms: streams for apache kafka kroxylicious: azure key vault ssrf exfiltrates bearer token via untrusted edek vaultname

Assigner: redhat
Reserved: 06.10.2026 Published: 20.10.2026 Updated: 20.10.2026

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.

Metrics

CVSS 3.1

CVSS Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
CVSS Score: 8.1

Attack Vector	Network	Scope	Unchanged
Attack Complexity	Low	Confidentiality Impact	High
Privileges Required	Low	Integrity Impact	High
User Interaction	None	Availability Impact	None

CVSS 3.1

Product Status

Vendor	Red Hat
Product	streams for Apache Kafka 3
Versions	Default: affected

Workarounds

Bind all topics to KEKs — remove PASSTHROUGH_UNENCRYPTED as unresolvedKeyPolicy. Explicitly configure kekSelector to match every topic.
Restrict outbound network access — use Kubernetes NetworkPolicy to limit proxy pod egress to only legitimate Azure Key Vault endpoints on port 443.
Monitor KMS call patterns — alert on unwrap requests targeting unexpected vault hostnames.

References

Problem Types

Server-Side Request Forgery (SSRF) CWE