Disclosed weakness · no CVE recorded

Codex child-thread creation could lose sandbox restrictions during conversion

OpenAI · Codex · child-thread sandbox inheritance

First documented disclosure · Review checkpoint

Summary

Converting a parent’s sandbox configuration for a child thread could lose restrictions or change the meaning of writable roots.

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

Legacy template conversions could collapse fixed roots to current-directory access or otherwise discard constraints that did not survive the round trip.

Conditions required

A child thread is created from an affected legacy sandbox configuration.

Potential impact

The child’s effective filesystem or network authority could differ from the intended inherited policy.

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 child-thread permissions for customized sandbox profiles.

Operating lesson

Permission inheritance must be lossless or reject an unrepresentable policy.

Evidence and limits

The original PR lists writable roots, network access and temporary-directory exclusions in its regression coverage. Tagged verification: child creation uses the explicit legacy sandbox-template conversion and rejects profiles whose restrictions cannot survive conversion.

Sources