cve.bz

CVE-2026-105941 SSRF

8.1 highEPSS 0.2%

High (8.1). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
EPSS
0.2% (unchanged from 0.2% a week ago) estimated probability of exploitation activity in the next 30 days; 16th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-20. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-105941 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105941?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105941?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105941 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as an Important severity flaw because an authenticated Kafka client can induce the proxy to transmit sensitive cloud credentials to an arbitrary destination, compromising the confidentiality and integrity of encrypted topic data. The flaw specifically affects Red Hat Streams for Apache Kafka environments where the Kroxylicious proxy is deployed with the Azure Key Vault KMS provider filter enabled. Deployments utilizing alternative Key Management Service (KMS) providers or those not utilizing record-level encryption filters are not susceptible to this attack.

Red Hat's mitigation

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)

ProductPackageStateAdvisory
streams for Apache Kafka 3kroxylicious-kms-provider-azure-key-vault-kmsAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-105941.

Attack patterns (CAPEC)

  • CAPEC-664 Server Side Request Forgery Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON