Answer: Use `$codex-security:track-findings` with one or more validated findings from the same completed scan, choosing one destination per run: for a GitHub issue specify the owner and repository, and for a private draft GitHub Security Advisory specify one finding and its public source repository on GitHub.com. For a draft advisory, sign in to GitHub.com with GitHub CLI (`gh`) using an account with administrator access to the public, non-fork source repository, select one finding from a scan whose target is a Git revision (`git_revision`), and have the package name, ecosystem, and affected versions ready. Status: Confirmed Entry: tool/codex/permissions-and-security/track-findings-issue-advisory Revision: 2 Digest: sha256:ad69e1d9893f3323 (changes whenever the content changes) Timeline: Created: 2026-11-13T03:53:32Z Last changed: 2026-11-18T13:35:48Z (Draft advisory details: — → package name, ecosystem, and affected versions) Last verified: 2026-11-20T13:42:05Z Next check: 2026-11-21T13:42:05Z Check interval: Daily Expected change: No fixed schedule Data: Field | Value | Source | As of Command | $codex-security:track-findings | [1] | 2026-11-20 GitHub issue requirements | Owner and repository | [1] | 2026-11-20 Draft advisory requirements | One finding and its public source repository on GitHub.com | [1] | 2026-11-20 Draft advisory sign-in | GitHub CLI (`gh`) | [1] | 2026-11-20 Draft advisory access | administrator access to the public, non-fork source repository | [1] | 2026-11-20 Draft advisory scan target | git_revision | [1] | 2026-11-20 Draft advisory details | package name, ecosystem, and affected versions | [1] | 2026-11-20 Sources: [1] OpenAI. "Export and track security findings". https://learn.chatgpt.com/docs/security/plugin/export-findings.md Role: primary. Accessed: 2026-11-20T13:42:05Z Quote: "Use `$codex-security:track-findings` with one or more validated findings from" (Supports: Command) Quote: "| GitHub issue | Owner and repository |" (Supports: GitHub issue requirements) Quote: "| Private draft GitHub Security Advisory | One finding and its public source repository on GitHub.com |" (Supports: Draft advisory requirements) Quote: "For a draft advisory, sign in to GitHub.com with GitHub CLI (`gh`) using an" (Supports: Draft advisory sign-in) Quote: "account with administrator access to the public, non-fork source repository." (Supports: Draft advisory access) Quote: "(`git_revision`). Commit-diff scans don't qualify." (Supports: Draft advisory scan target) Quote: "Have the package name, ecosystem, and affected versions ready." (Supports: Draft advisory details) Snapshot SHA-256: d772e159976d73d119631b1efa315a3f0a91fd5c35e216069fcd9ecea9ba9855 (captured 2026-11-17T14:07:19Z) 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:19Z, so the values verified then were kept. Cross-check: not-available at 2026-11-20T13:42:05Z. No independent second source is configured for this entry Last successful check: 2026-11-20T13:42:05Z Last attempt: 2026-11-20T13:42:05Z Notes and limitations: Extracted automatically from a single official source (section "Track selected findings"). Related: https://latestn.com/tool/codex/permissions-and-security/triage-security-backlog How do I triage a backlog of security findings 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/start-security-scan How do I start a security scan in the Codex Security workbench? https://latestn.com/tool/codex/permissions-and-security/test-rule-file How do I test a Codex rule file to check it works? https://latestn.com/tool/codex/permissions-and-security/threat-model-contents What does a Codex threat model include for a repository? https://latestn.com/tool/ All entries in AI tools Change log: Time | Event | Change | Source 2026-11-18T13:35:48Z | changed | Draft advisory details: — → package name, ecosystem, and affected versions | [1] 2026-11-18T13:35:48Z | changed | Draft advisory access: — → administrator access to the public, non-fork source repository | [1] 2026-11-18T13:35:48Z | changed | Draft advisory sign-in: — → GitHub CLI (`gh`) | [1] 2026-11-18T13:35:48Z | changed | Draft advisory requirements: — → One finding and its public source repository on GitHub.com | [1] 2026-11-18T13:35:48Z | changed | GitHub issue requirements: — → Owner and repository | [1] 2026-11-18T13:35:48Z | changed | Command: — → $codex-security:track-findings | [1] 2026-11-18T13:35:48Z | changed | Draft advisory account access: administrator access to the public, non-fork source repository → — | [1] 2026-11-18T13:35:48Z | changed | Draft advisory sign-in tool: GitHub CLI (`gh`) → — | [1] 2026-11-18T13:35:48Z | changed | Draft advisory destination: One finding and its public source repository on GitHub.com → — | [1] 2026-11-18T13:35:48Z | changed | GitHub issue destination: Owner and repository → — | [1] 2026-11-18T13:35:48Z | changed | command: $codex-security:track-findings → — | [1] 2026-11-13T03:53:32Z | added | Entry created | — Changes for this entry as a feed: https://latestn.com/tool/codex/permissions-and-security/track-findings-issue-advisory/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/track-findings-issue-advisory POST: https://latestn.com/dispute/tool/codex/permissions-and-security/track-findings-issue-advisory with claim, evidence_url, and optionally field and contact (form-encoded or JSON) GET: https://latestn.com/dispute/tool/codex/permissions-and-security/track-findings-issue-advisory?claim={what is wrong}&evidence_url={link} How to cite: LatestN. (2026). How do I get Codex to create a GitHub issue or draft security advisory for findings? Revision 2, last verified 2026-11-20T13:42:05Z. https://latestn.com/tool/codex/permissions-and-security/track-findings-issue-advisory (accessed 2026-11-21T10:07:03Z). @misc{LatestN_tool_codex_permissions_and_security_track_findings_issue_advisory_r2, title = {How do I get Codex to create a GitHub issue or draft security advisory for findings?}, author = {{LatestN}}, year = {2026}, howpublished = {\url{https://latestn.com/tool/codex/permissions-and-security/track-findings-issue-advisory}}, note = {Revision 2; digest sha256:ad69e1d9893f3323; last verified 2026-11-20T13:42:05Z; accessed 2026-11-21T10:07:03Z} } 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/track-findings-issue-advisory