Disclosed weakness · no CVE recorded

Codex permission updates could lose existing filesystem read restrictions

OpenAI · Codex · session permission updates

First documented disclosure · Review checkpoint

Summary

Updating session permissions could lose deny-read restrictions already applied to the session.

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

Permission normalization and legacy-policy conversion did not consistently retain the current filesystem restrictions at settings admission.

Conditions required

An affected session receives a permission-profile or legacy sandbox-policy update.

Potential impact

The resulting session could have broader filesystem read authority than its prior restrictions intended.

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 verify the active filesystem policy after permission changes.

Operating lesson

Apply permission changes while preserving restrictions that remain in force.

Evidence and limits

Tagged verification: permission updates preserve existing deny-read entries before installing the normalized profile; legacy conversions also use the restriction-preserving path.

Sources