High [CVE-2026-105941] kroxylicious-kms-provider-azure-key-vault-kms: Streams for Apache Kafka Kroxylicious: Azure Key Vault SSRF exfiltrates bearer token via untrusted EDEK vaultName
This high-severity Red Hat Linux advisory covers CVE-2026-105941; related products: streams for Apache Kafka 3.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Red Hat Linux 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 34 official vendor sources and 160+ reviewed platform categories.
Summary
kroxylicious-kms-provider-azure-key-vault-kms: Streams for Apache Kafka Kroxylicious: Azure Key Vault SSRF exfiltrates bearer token via untrusted EDEK vaultName. Red Hat rates this important (CVSS 8.1).
Weakness: CWE-918.
Affected product named by the advisory: streams for Apache Kafka 3.
Affected versions
No affected-version range was extracted from the source record. The vendor advisory is authoritative — check it before change work.
Official advisory · high-confidence parse· fetched 12 hours ago·verify at source
Fixed versions
No fixed release is recorded yet. That does not prove no patch exists — confirm against the vendor advisory.
Official advisory · high-confidence parse· fetched 12 hours ago·verify at source
Mitigation checklist
- 1. Restrict outbound network access — use Kubernetes NetworkPolicy to limit proxy pod egress to only legitimate Azure Key Vault endpoints on port 443. 2. Monitor KMS call patterns — alert on unwrap requests targeting unexpected vault hostnames. --- CME Mitigation Guidance (2026-10-20) --- Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure. The highest-value action is to enforce strict allowlist regex validation on wire-deserialized vaultName in the Azure Key Vault KMS provider before constructing outbound HTTP endpoints: upgrade to kroxylicious-kms-provider-azure-key-vault-kms 0.25.1+ (or the fixed Kroxylicious Kms Provider Azure Key Vault Kms builds), which validate Key Vault name using validateKeyVaultName to reject names containing dots, URL fragments, invalid lengths, or malformed hyphens before constructing the Key Vault URL, closing all 2 injection vectors (crafted EDEK containing an arbitrary hostname in vaultName, vaultName URL fragment injection). Until patched, this is a concern on Kafka clusters using the Kroxylicious Record Encryption filter with Azure Key Vault KMS, so restrict proxy pod outbound network egress using Kubernetes NetworkPolicy strictly to legitimate Azure Key Vault endpoints on port 443 and alert on unwrap requests targeting unexpected vault hostnames. As a compensating measure, Deploy Falco or eBPF runtime security to detect anomalous outbound network connections initiated by the Kroxylicious proxy process to unexpected destinations. These controls limit blast radius and contain exploitation, but they do not fix the underlying unvalidated input SSRF defect — apply the upstream patch to fully remediate. Highest-impact CME: CME-1315 Allowlist-Preferred Input Validation (Deny-by-Default Filtering) (high)
Official advisory · high-confidence parse· fetched 12 hours 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.