Answer: Send a prompt like "Use $codex-security:vulnerability-writeup to create one self-contained report for each distinct vulnerability in [input paths]." Codex then groups reports with the same root cause and vulnerable path into one directory per vulnerability, each containing a Markdown report and, when available, supporting files in `poc/`. Status: Confirmed Entry: tool/codex/permissions-and-security/write-vulnerability-reports-workflow Revision: 2 Digest: sha256:efe11eeb4a457568 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:53:43Z Last changed: 2026-11-17T14:07:33Z (directory contents: a Markdown report and a `poc/` directory → a Markdown report and, when available, supporting files in `poc/`) Last verified: 2026-11-20T13:42:16Z Next check: 2026-11-21T13:42:16Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of prompt command | $codex-security:vulnerability-writeup | [1] | 2026-11-20 report grouping | one directory per vulnerability | [1] | 2026-11-20 directory contents | a Markdown report and, when available, supporting files in `poc/` | [1] | 2026-11-20 Sources: [1] OpenAI. "Write vulnerability reports". https://learn.chatgpt.com/docs/security/plugin/vulnerability-reports.md Role: primary. Accessed: 2026-11-20T13:42:16Z Quote: "Use $codex-security:vulnerability-writeup to create one self-contained report for each distinct vulnerability in [input paths]." (Supports: prompt command) Quote: "Codex groups reports with the same root cause and vulnerable path into one directory per vulnerability." (Supports: report grouping) Quote: "Each directory contains a Markdown report and, when available, supporting files in `poc/`." (Supports: directory contents) Snapshot SHA-256: 732354a45baa9b8ed926533e9c8c3b66df62438df8c83215ef6d739cd973d3e0 (captured 2026-11-17T14:07:34Z) Verification: Method: Automated extraction from [1] with deepseek-flash (JSON output, thinking disabled). Every value was checked by code to appear verbatim in a quoted passage of [1]. On this check the text of [1] was unchanged since 2026-11-17T14:07:33Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:42:16Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:42:16Z Last attempt: 2026-11-20T13:42:16Z Notes and limitations: Extracted automatically from a single official source (section "Run the workflow"). Related: https://latestn.com/tool/codex/pricing-and-limits/auto-review-limits What are the limits of Codex Auto-review and when does it trigger? https://latestn.com/tool/codex/pricing-and-limits/cloud-scan-billing How are Daybreak Defense Factory cloud scans billed? https://latestn.com/tool/codex/pricing-and-limits/fast-mode-billing How is Fast mode billed in Codex? https://latestn.com/tool/codex/permissions-and-security/use-chatgpt-auth-instead-of-api-key How do I make Codex Security CLI use my ChatGPT sign-in instead of an API key for scans? https://latestn.com/tool/codex/permissions-and-security/use-hardening-guidance-from-scan How do I use hardening guidance from a Codex Security scan? https://latestn.com/tool/codex/permissions-and-security/vulnerability-report-without-scan Can Codex write vulnerability reports without a Codex Security scan? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-17T14:07:33Z | changed | directory contents: a Markdown report and a `poc/` directory → a Markdown report and, when available, supporting files in `poc/` | [1] 2026-11-17T14:07:33Z | changed | output per vulnerability: creates one report directory per distinct vulnerability → — | [1] 2026-11-17T14:07:33Z | changed | report grouping: groups reports that describe the same root cause and vulnerable path → one directory per vulnerability | [1] 2026-11-17T14:07:33Z | changed | reproduction environment: Use a local test environment for reproductions. → — | [1] 2026-11-17T14:07:33Z | changed | verification instruction: Verify the claims against [source path and revision] → — | [1] 2026-11-13T03:53:43Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/permissions-and-security/write-vulnerability-reports-workflow/latest Challenge this entry: Open challenges: None How: If a value here is wrong or out of date, send what is wrong and a link to evidence. Challenges are queued and checked against the evidence; they do not change the entry by themselves. If the entry changes as a result, the change log says so. Form: https://latestn.com/dispute/tool/codex/permissions-and-security/write-vulnerability-reports-workflow POST: https://latestn.com/dispute/tool/codex/permissions-and-security/write-vulnerability-reports-workflow with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/permissions-and-security/write-vulnerability-reports-workflow?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I use Codex to write vulnerability reports from findings and PoCs? Revision 2, last verified 2026-11-20T13:42:16Z. https://latestn.com/tool/codex/permissions-and-security/write-vulnerability-reports-workflow (accessed 2026-11-21T10:00:39Z). @misc{LatestN_tool_codex_permissions_and_security_write_vulnerability_reports_workflow_r2, title = {How do I use Codex to write vulnerability reports from findings and PoCs?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/permissions-and-security/write-vulnerability-reports-workflow}}, note = {Revision 2; digest sha256:efe11eeb4a457568; last verified 2026-11-20T13:42:16Z; accessed 2026-11-21T10:00:39Z} } Reuse: License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/) Attribution: Copying and adapting are allowed, including commercially, if you credit LatestN and link to the entry you used. Each entry ends with a ready-made citation. URL: https://latestn.com/tool/codex/permissions-and-security/write-vulnerability-reports-workflow