Codex Security scan cannot be loaded due to attackPath.impact schema mismatch

Resolved 💬 1 comment Opened Aug 13, 2026 by Makun0uchi Closed Aug 24, 2026

What version of the Codex App are you using (From “About Codex” dialog)?

Codex Desktop: 26.803.61601; Codex Security: 0.1.18

What subscription do you have?

Plus

What platform is your computer?

Darwin 24.6.0 arm64 arm

What issue are you seeing?

A completed Codex Security scan appears in the scan list, but opening it shows:

“Codex Security could not load this scan.”

The scan itself is complete and its data is available through the Codex Security tools:

  • scanId: 52f6ba87-2400-45b5-a8aa-8d89fac851e2
  • status: complete
  • findingCount: 18
  • reportAvailable: true

The sealed scan contract and artifact checksums are valid. The issue appears to be limited to deserialization in the Codex Desktop Security Workbench.

What steps can reproduce the bug?

  1. Open Codex Desktop.
  2. Open the Security section.
  3. Go to Scans.
  4. Select the completed scan for backend_fastapi:
  • scanId: 52f6ba87-2400-45b5-a8aa-8d89fac851e2
  • revision: 4e061cf02ae057e5e93517d0a304ab1f2f0fca5b
  1. The scan detail page fails to load and displays:

“Codex Security could not load this scan.”

  1. Clicking Refresh produces the same result.
  2. Fully restarting Codex does not resolve the issue.

What is the expected behavior?

Завершённое сканирование открывается в Security Workbench.

Additional information

_No response_

View original on GitHub ↗

1 Comment

Makun0uchi · 4 days ago

Problem solved