Disclosed weakness · no CVE recorded

Codex could restore MCP credentials after logout or overwrite a newer login

OpenAI · Codex · MCP OAuth credential persistence

First documented disclosure · Review checkpoint

Summary

A pending token refresh could recreate credentials after logout or replace credentials from a newer sign-in.

Severity and exploitation evidence

No CVSS score recorded in this review.

Exploitation not established: The reviewed sources describe a correction or controlled reproduction; malicious exploitation against users is not established.

Exploitation evidence source

Technical severity is not a measure of observed attacks or of risk to your deployment. Attempts, demonstrations, and successful compromise retain the qualifications in the source.

How the weakness works

Persistence did not revalidate that the stored credential state still matched the refresh operation’s expected state.

Conditions required

An MCP OAuth refresh overlaps logout or a new login in an affected Codex session.

Potential impact

Revoked local sign-in state could return or a different intended login could be overwritten. Provider-side revocation behavior is outside the report.

Affected versions and configurations

The reviewed upstream report does not establish a complete affected-release range.

Fix and mitigation status

0.170.0 contains the correction.

Practical next steps

Upgrade to Codex 0.170.0 and repeat logout or reauthorization if an earlier refresh may have overlapped an account change.

Operating lesson

Revalidate authorization state immediately before committing refreshed credentials.

Evidence and limits

Tagged verification: credential persistence acquires a store guard, reloads stored state and requires authorization again if it differs from the expected credentials. The adjacent cancellation-safety change addresses rotated-token availability and is not a separate theft claim.

Sources