CVE-2026-105941
8.1HighPublished 20 Oct 2026 · NVD status: Received · AI triage by gemini-3.8-flash
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- None
- Impact
- High impact on confidentiality, integrity
- Weakness
- CWE-918
Impact
Authenticated attackers can force Kroxylicious to leak its Azure bearer token to an arbitrary host via SSRF, allowing them to decrypt stored records against the real Azure Key Vault. They need network access to send crafted messages containing untrusted EDEK bytes to the proxy.
Root cause
The Azure Key Vault KMS provider fails to validate the format of the deserialized vaultName field from incoming EDEK bytes before issuing requests.
Affected systems
Versions not listed — check the vendor advisory.
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N
Fix & remediation
Upgrade to the patched Kroxylicious release once published by the vendor. In the interim, restrict proxy egress network traffic strictly to legitimate Azure Key Vault endpoints and deny untrusted clients access to the Kroxylicious proxy.
AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD 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.