Mistral Vibe: OIDC Sign-in Fixes Stop Credential and Tenant Data Leaking Across Accounts

Mistral VibeNov 3, 2026View original changelog

Mistral Vibe 3.1.0 fixed three OIDC isolation problems. Model requests no longer forward tenant headers through redirects, a refresh no longer restores cleared or replaced credentials, and account or tenant switches no longer reuse another account's cached settings or connector catalog. Rejected model tokens now require renewed authentication.

Key Takeaways

OIDC model requests no longer forward tenant headers through redirects.
A refresh no longer restores credentials that were cleared or replaced.
Rejected model tokens now require renewed authentication instead of continuing to be used.
Switching accounts or tenants no longer reuses another account's cached settings.
The same switch also no longer reuses another account's connector catalog.
The three fixes together tighten identity isolation for OIDC users; the changelog lists them as fixes and does not describe an exploit.

The pattern

Three fixes in Mistral Vibe 3.1.0 share one theme: with OIDC sign-in, credentials and account data could cross a boundary they should not cross. Each fix keeps one identity's data from reaching another party or another account.

Tenant headers and redirects

OIDC-authenticated model requests no longer forward tenant headers through redirects. Before the fix, a redirect could carry tenant identifying headers to a different destination.

Credentials stay cleared

An OIDC refresh no longer restores cleared or replaced credentials. Previously a refresh could bring back credentials that had been removed or swapped. Also, rejected model tokens now require renewed authentication, so a token the service rejected cannot linger.

Account and tenant switches

Switching OIDC accounts or tenants no longer reuses another account's cached settings or connector catalog. The cache is no longer shared between identities.

Who is affected

These fixes matter mainly to people who sign in through OIDC, typically in organizations. The changelog does not describe any exploit. It lists them as fixes.