Answer: Before writing a vulnerability report, provide Codex with the findings, disclosure notes, or assessment documents to review; the target source tree and affected revision or release; existing PoCs, logs, traces, screenshots, or diagnostic output; and fix commits or diffs when available. Status: Confirmed Entry: tool/codex/permissions-and-security/prepare-evidence-vulnerability-report Revision: 2 Digest: sha256:16d2baa718600fe1 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:53:44Z Last changed: 2026-11-17T14:07:34Z (Fix commits or diffs: — → Fix commits or diffs when available.) 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 Findings and documents | The findings, disclosure notes, or assessment documents to review. | [1] | 2026-11-20 Source tree and revision | The target source tree and affected revision or release. | [1] | 2026-11-20 PoCs and diagnostics | Existing PoCs, logs, traces, screenshots, or diagnostic output. | [1] | 2026-11-20 Fix commits or diffs | Fix commits or diffs when available. | [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: "The findings, disclosure notes, or assessment documents to review." (Supports: Findings and documents) Quote: "The target source tree and affected revision or release." (Supports: Source tree and revision) Quote: "Existing PoCs, logs, traces, screenshots, or diagnostic output." (Supports: PoCs and diagnostics) Quote: "Fix commits or diffs when available." (Supports: Fix commits or diffs) 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:34Z, 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 "Prepare the evidence"). Related: https://latestn.com/tool/codex/permissions-and-security/preset-domain-lists What preset domain lists are available for Codex Cloud (Legacy) internet access? https://latestn.com/tool/codex/permissions-and-security/prisma-airs-enforcement-modes What enforcement modes and failure behaviors can I choose for Prisma AIRS in Codex? https://latestn.com/tool/codex/permissions-and-security/read-only-triage-requirements What are the requirements to run read-only triage in Codex? https://latestn.com/tool/codex/permissions-and-security/migrate-untrusted-approval-policy How do I migrate from the retired untrusted approval policy in Codex? https://latestn.com/tool/codex/permissions-and-security/permission-modes-overview What permission modes does ChatGPT and Codex offer for local actions? https://latestn.com/tool/codex/permissions-and-security/prepare-evidence-for-hardening What evidence should I provide to Codex Security when proposing security hardening? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-17T14:07:34Z | changed | Fix commits or diffs: — → Fix commits or diffs when available. | [1] 2026-11-17T14:07:34Z | changed | PoCs and diagnostics: — → Existing PoCs, logs, traces, screenshots, or diagnostic output. | [1] 2026-11-17T14:07:34Z | changed | Source tree and revision: — → The target source tree and affected revision or release. | [1] 2026-11-17T14:07:34Z | changed | Findings and documents: — → The findings, disclosure notes, or assessment documents to review. | [1] 2026-11-17T14:07:34Z | changed | fix commits or diffs: Fix commits or diffs when available. → — | [1] 2026-11-17T14:07:34Z | changed | PoCs and diagnostic output: Existing PoCs, logs, traces, screenshots, or diagnostic output. → — | [1] 2026-11-17T14:07:34Z | changed | source tree and revision: The target source tree and affected revision or release. → — | [1] 2026-11-17T14:07:34Z | changed | findings and documents: The findings, disclosure notes, or assessment documents to review. → — | [1] 2026-11-13T03:53:44Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/permissions-and-security/prepare-evidence-vulnerability-report/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/prepare-evidence-vulnerability-report POST: https://latestn.com/dispute/tool/codex/permissions-and-security/prepare-evidence-vulnerability-report with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/permissions-and-security/prepare-evidence-vulnerability-report?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). What evidence should I provide to Codex before writing a vulnerability report? Revision 2, last verified 2026-11-20T13:42:16Z. https://latestn.com/tool/codex/permissions-and-security/prepare-evidence-vulnerability-report (accessed 2026-11-21T10:03:54Z). @misc{LatestN_tool_codex_permissions_and_security_prepare_evidence_vulnerability_report_r2, title = {What evidence should I provide to Codex before writing a vulnerability report?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/permissions-and-security/prepare-evidence-vulnerability-report}}, note = {Revision 2; digest sha256:16d2baa718600fe1; last verified 2026-11-20T13:42:16Z; accessed 2026-11-21T10:03:54Z} } 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/prepare-evidence-vulnerability-report