The Wire · Showcase
CODEX FIXES IMAGE TRANSPARENCY AND PATH RESOLUTION VULNERABILITIES
By RepoJournal · Filed · About OpenAI
Codex shipped native transparency support for image generation and patched a directory traversal risk in project path resolution.
The image generation skill now uses built-in transparency requests instead of chroma-key workarounds, with explicit CLI fallback confirmation between model versions [1]. Two separate patches tightened line-ending handling: a feature flag preserves CRLF and mixed endings in apply_patch operations [2], while a new PreserveLineEndings mode offers opt-in protection without breaking existing APIs [3]. Plugin installation tracking improved with the addition of installAttemptId forwarding to remote systems, letting clients correlate requests with specific attempts [5]. The most critical fix bounds Cursor project path resolution to 128 probes instead of recursive directory scanning, closing a potential DoS vector on large filesystem trees [4].
One email a day. Unsubscribe in one click.
Keep up with OpenAI in about 3 minutes a day: what actually shipped — the commits, pull requests, releases, and security advisories that matter.
One email a day. Unsubscribe in one click. Read a past issue →
Action items
- → Deploy image generation transparency changes to production openai/codex [plan]
- → Enable apply_patch line-ending preservation for Windows-heavy codebases openai/codex [plan]
- → Verify Cursor project path resolution bounds in high-volume environments openai/codex [monitor]
References
- [1] Use native transparency in the imagegen skill ↗ openai/codex
- [2] Add a feature flag to preserve apply_patch line endings ↗ openai/codex
- [3] Add a line-ending preservation mode to `apply_patch` ↗ openai/codex
- [4] Bound Cursor project path resolution ↗ openai/codex
- [5] Forward install attempt IDs for remote plugins ↗ openai/codex