CVE-2026-27478: Unity Catalog Auth Bypass Vulnerability

CVE-2026-27478 Overview

CVE-2026-27478 is a critical authentication bypass vulnerability affecting Unity Catalog, an open, multi-modal catalog for data and AI. The vulnerability exists in the token exchange endpoint (/api/1.0/unity-control/auth/tokens) where the system extracts the issuer (iss) claim from incoming JWTs and uses it to dynamically fetch the JWKS endpoint for signature validation without validating that the issuer is a trusted identity provider.

Critical Impact

Attackers can forge arbitrary JWT tokens by specifying a malicious issuer URL pointing to an attacker-controlled JWKS endpoint, bypassing authentication entirely and gaining unauthorized access to the Unity Catalog system.

Affected Products

• Unity Catalog version 0.4.0 and earlier

Discovery Timeline

• 2026-03-11 - CVE-2026-27478 published to NVD
• 2026-03-12 - Last updated in NVD database

Technical Details for CVE-2026-27478

Vulnerability Analysis

This authentication bypass vulnerability (CWE-290: Authentication Bypass by Spoofing) stems from an insecure JWT validation implementation. The affected token exchange endpoint blindly trusts the iss (issuer) claim embedded within incoming JWT tokens without first verifying that the issuer is an authorized and trusted identity provider.

When a JWT is submitted to the /api/1.0/unity-control/auth/tokens endpoint, the application extracts the issuer claim and dynamically constructs the JWKS (JSON Web Key Set) URL based on this untrusted input. The application then fetches the public keys from this URL to validate the JWT signature. This design flaw allows an attacker to craft a JWT with a malicious iss value pointing to an attacker-controlled server hosting a JWKS endpoint with keys the attacker possesses.

Root Cause

The root cause is the absence of issuer validation in the JWT authentication flow. The endpoint fails to maintain a whitelist or perform verification of trusted identity providers before accepting the issuer claim. Instead of validating the iss claim against known, trusted issuers, the application treats the issuer value as authoritative and uses it to determine where to fetch validation keys.

Attack Vector

The attack is network-based and requires no authentication or user interaction. An attacker can exploit this vulnerability through the following sequence:

1. The attacker generates a cryptographic key pair and hosts a JWKS endpoint on an attacker-controlled server
2. The attacker crafts a JWT with arbitrary claims (including elevated privileges or impersonated identities) and sets the iss claim to point to their malicious JWKS endpoint
3. The attacker signs the JWT with their private key
4. The attacker submits the forged JWT to the vulnerable token exchange endpoint
5. Unity Catalog extracts the iss claim, fetches keys from the attacker's JWKS endpoint, and successfully validates the signature using the attacker's public key
6. The attacker gains unauthorized access with the privileges specified in the forged token

For technical details and proof-of-concept information, refer to the GitHub Security Advisory.

Detection Methods for CVE-2026-27478

Indicators of Compromise

• JWT tokens with iss claims pointing to external or unknown domains
• Network traffic showing JWKS requests to unexpected or suspicious external endpoints
• Authentication logs showing token exchanges from unrecognized issuer URLs
• Unusual access patterns from accounts that were authenticated via the token exchange endpoint

Detection Strategies

• Monitor the /api/1.0/unity-control/auth/tokens endpoint for incoming JWTs with non-whitelisted issuer values
• Implement network monitoring to detect outbound JWKS fetch requests to external domains
• Review authentication logs for patterns indicating issuer spoofing attempts
• Deploy web application firewalls (WAF) with rules to detect and block JWTs containing suspicious issuer claims

Monitoring Recommendations

• Enable verbose logging on the Unity Catalog authentication subsystem
• Set up alerts for JWKS fetch requests to domains outside of your trusted identity provider list
• Monitor for privilege escalation attempts following token exchange operations
• Implement anomaly detection for authentication patterns on the affected endpoint

How to Mitigate CVE-2026-27478

Immediate Actions Required

• Upgrade Unity Catalog to a patched version that includes issuer validation
• Implement network-level restrictions to block outbound JWKS requests to untrusted domains
• Review authentication logs for evidence of exploitation
• Rotate all credentials and tokens that may have been compromised

Patch Information

Security updates addressing this vulnerability are tracked in the GitHub Security Advisory (GHSA-qqcj-rghw-829x). Organizations should upgrade from version 0.4.0 or earlier to the latest patched release as soon as it becomes available.

Workarounds

• Deploy a reverse proxy or API gateway in front of Unity Catalog that validates JWT issuer claims against a whitelist before forwarding requests
• Implement network segmentation to restrict outbound connections from the Unity Catalog server to only trusted identity provider domains
• Use firewall rules to block the Unity Catalog server from making arbitrary outbound HTTPS connections
• Consider disabling the token exchange endpoint if not required for operations until a patch is applied

# Example: Network restriction to limit JWKS fetch destinations
# Configure firewall to only allow outbound HTTPS to trusted IdP domains
iptables -A OUTPUT -p tcp --dport 443 -d trusted-idp.example.com -j ACCEPT
iptables -A OUTPUT -p tcp --dport 443 -m owner --uid-owner unity-catalog -j DROP