Unexpected WebSearch call in Codex session (possible cross-session leakage)

What version of Codex is running?

0.38.0

Which model were you using?

gpt-5-codex medium

What platform is your computer?

NixOS - Linux 6.12.46 x86_64

What steps can reproduce the bug?

There's no clear reproduction step as this appeared seemingly out of thin air. I've been a regular user of Codex CLI for a couple of weeks and have never seen anything like this. I can't find anywhere else to report this.

What is the expected behavior?

I only get search results addressed to me - i'm worried this is a data security issue on the search provider side (i don't know how the search tool is implemented).

What do you see instead?

A random result for a completely unrelated search popped up in the middle of a codex session.

Additional information

When asked about the odd search, codex responded with the following:

<img width="1130" height="653" alt="Image" src="https://github.com/user-attachments/assets/2f460b11-c0b8-40ac-bf0b-9adf4d9f85b7" />

I had codex help me draft the report:

While working in our Codex CLI session today, the TUI reported a tool response that we never
initiated. The suspicious entry is:

  2025-09-22T01:45:49.150524Z  WARN  Unexpected response item: WebSearchCall { id:
  Some("ws_0b65e0d0bd5320220168d0aa344c98819d8adb5cadaa0e725b"), status: Some("completed"),
  action: Search { query: "Texas Longhorns football score today" } } with response: None

Context:

• Toolchain: Codex CLI, no web searches were triggered by anyone on our team during this
session.
• We have zero history of football-related work or queries, so this appears to be a misrouted
web search result from another user/tenant. The TUI logged it as “Unexpected response item”, however all searches (including intended ones) appear to this way in the log.

Actions taken:

• Captured the log segment to logs/unexpected-websearch.log.
• No user-initiated web calls were running at the time; the CLI was idle when the callback
arrived (i'm not sure Codex is right about this - it could be).

Request:

• Please investigate the originating request(s) for the above WebSearchCall IDs.
• Confirm whether isolation was breached (i.e., another tenant’s call surfaced in our stream)
and whether any further action is needed on our side.

Thank you for looking into this.