CVE-2026-105941 Red Hat CVE debrief

Who should care

Defenders responsible for Kroxylicious-kms-provider-azure-key-vault-kms deployments should assess exposure and prioritize patching or workarounds. This includes operators, platform administrators, vulnerability management teams, and security teams. They should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Why it matters

Defenders should prioritize verifying affected versions and applying patches or workarounds to prevent exploitation of the Kroxylicious-kms-provider-azure-key-vault-kms vulnerability.

• Potential exfiltration of Azure bearer tokens
• Possible SSRF attacks against Azure Key Vault
• Required verification of affected versions and patches
• Potential impact on record-encryption trust model

Technical summary

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. This vulnerability affects Kroxylicious deployments using the Azure Key Vault KMS provider and has a CVSS score of 8.1. Defenders should prioritize verifying affected versions and applying patches or workarounds to prevent exploitation. The vulnerability allows for potential exfiltration of Azure bearer tokens and possible SSRF attacks against Azure Key Vault.

Defensive priority

Defenders should prioritize verifying affected versions and applying patches or workarounds to prevent exploitation.

Recommended defensive actions

• Verify affected versions of Kroxylicious-kms-provider-azure-key-vault-kms
• Apply patches or workarounds to prevent exploitation
• Monitor for suspicious activity related to Azure bearer token exfiltration
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, including its description, CVSS score, and affected products. The vulnerability has a CVSS score of 8.1 and is classified as HIGH severity. There are no known exploits in the wild, but defenders should verify affected versions and apply patches or workarounds to prevent exploitation. The source item provides additional context on the vulnerability, including its impact on the record-encryption trust model.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.