MEDIUM 6.5

CVE-2026-14898: OpenAI Codex macOS Image Fetching Information Disclosure

The OpenAI Codex desktop app for macOS has a vulnerability that allows attackers to steal sensitive information from users' sessions. An attacker can craft malicious prompts that trick the Codex model into generating URLs pointing to attacker-controlled servers. When the app displays the response, it automatically loads these remote images without requiring the user to click anything, causing the embedded sensitive data—like API keys or source code—to be sent to the attacker. This happens because the app renders Markdown-formatted responses and fetches remote images automatically.

Source data · NVD / CISA · public domain

CVSS
3.1 · 6.5 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Weaknesses (CWE)
CWE-200
Affected products
0 configuration(s)
Published / Modified
2026-07-06 / 2026-07-07

NVD description (verbatim)

The OpenAI Codex desktop app for macOS rendered remote images from Markdown in model responses. An attacker who could place an indirect prompt injection in content processed by Codex, such as a connected-tool result or another untrusted source, could induce the model to construct a remote image URL containing sensitive data. The app automatically fetched that URL when rendering the response, sending the embedded data to an attacker-controlled server without a separate user click. Successful exploitation could exfiltrate secrets and other information accessible in the Codex session, including API keys, source code, and data returned by connected tools. No direct integrity or availability impact was demonstrated, and there is no known exploitation in the wild.

1 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-14898 is an indirect prompt injection vulnerability in the OpenAI Codex macOS desktop application that leads to unintended information exfiltration. The vulnerability exists in the response-rendering layer, which automatically fetches remote images embedded in Markdown when processing model outputs. An attacker positioned to influence prompt content—through compromised tools, poisoned external data sources, or other indirect injection vectors—can cause the model to construct URLs that encode sensitive session data. The desktop app's automatic image-fetching behavior (no user interaction required) means the embedded credentials or secrets reach the attacker's server during the fetch operation. The attack surface includes any untrusted data fed into Codex prompts, including results from connected integrations.

Business impact

Organizations using Codex for code generation, documentation, or data analysis face credential exposure risk. Compromised API keys can lead to unauthorized access to OpenAI services and downstream systems. Exfiltrated source code creates intellectual property and security posture disclosure. If Codex is integrated with other tools (databases, version control, deployment systems), connected-tool results become an attack vector that could leak data from those systems as well. The lack of UI friction (no click required) increases the likelihood that users remain unaware of the exfiltration, delaying detection and response.

Affected systems

The OpenAI Codex desktop application for macOS is directly affected. The vendor_products list in the advisory is empty, which suggests either the vendor has not formally listed affected versions or the vulnerability details are still under coordination. Users should verify with OpenAI's official advisory for specific version ranges affected by this issue.

Exploitability

Exploitation requires an attacker to place an indirect prompt injection in content that will be processed by Codex—such as output from a connected tool, a code repository, or another untrusted source integrated into the workflow. The CVSS vector (AV:N/AC:L/PR:N/UI:R) reflects network-accessible attack, low complexity, and user interaction (the user must cause the Codex app to render the malicious response). The user interaction requirement is met once the user sends a prompt; the automatic image fetch requires no additional clicks. No direct integrity or availability impact and no known wild exploitation lower the severity to MEDIUM, but the potential for high confidentiality impact warrants attention.

Remediation

Users should immediately update Codex to a patched version provided by OpenAI. Check OpenAI's official security advisories and release notes for the specific version that remedies this vulnerability. The primary mitigation is preventing automatic fetching of remote images in Markdown responses—users should verify that their installed version includes this fix. Until patched, organizations should audit which external data sources and tool integrations feed prompts into Codex and reduce reliance on untrusted inputs in production workflows.

Patch guidance

Apply the latest OpenAI Codex desktop app update for macOS as released by OpenAI in response to CVE-2026-14898. Verify the patched version against OpenAI's official security bulletin to confirm the image-fetching behavior has been hardened or disabled. Organizations should test the update in a non-production environment before rolling out to ensure compatibility with dependent workflows. Enable automatic updates if available to reduce the window of exposure.

Detection guidance

Monitor Codex sessions for unexpected outbound HTTPS requests to unfamiliar domains, particularly during or immediately after response rendering. Check application logs and network traffic for evidence of image-fetch requests containing encoded data or unusual URL patterns. Review Codex interaction history for prompts containing injected markdown image syntax, especially from integrated external tools. Inspect any API key or secret rotation logs to identify whether credentials accessed during Codex sessions have been misused. Organizations with endpoint detection and response (EDR) tools should look for the Codex app making network requests to non-OpenAI infrastructure during normal operation.

Why prioritize this

Although the CVSS score is MEDIUM (6.5), the practical confidentiality impact is high: API keys, source code, and tool-returned data represent critical assets. The low barrier to exploitation (network-accessible, no special privileges required) combined with the silent nature of the exfiltration (automatic image fetch, no user visibility) justifies urgent patching. The absence of known wild exploitation provides a narrow window to patch before adversaries weaponize the technique. Organizations where Codex is connected to production systems or processes sensitive source code should prioritize this patch above routine updates.

Risk score, explained

The CVSS 3.1 score of 6.5 (MEDIUM) reflects high confidentiality impact and low attack complexity, balanced against the user-interaction requirement and lack of direct integrity or availability damage. The network-accessible attack vector and the simplicity of crafting indirect prompt injections keep the attack complexity low. The score appropriately captures the risk for users but may underweight the business risk in organizations where Codex handles proprietary code or integrates with sensitive tool chains. Security teams should consider their own environment's exposure when deciding on patch priority independent of the base CVSS score.

Frequently asked questions

Can this vulnerability be exploited if I use Codex in an isolated environment with no external tool integrations?

The attack requires the attacker to inject malicious content into a prompt or Codex input. If Codex only processes prompts you manually type and does not ingest data from external sources, repositories, or connected tools, your attack surface is limited. However, you remain vulnerable if you copy-paste code or data from untrusted sources into Codex prompts. Patching is still strongly recommended.

Does this vulnerability affect the OpenAI API or only the desktop app?

This CVE specifically affects the Codex desktop application for macOS. The vulnerability is in how the desktop app renders Markdown responses and automatically fetches remote images. The API itself does not have this auto-fetch behavior, though API users should still be aware of prompt injection risks in general.

What should I do if I think my API keys were exposed through this vulnerability?

Immediately rotate any API keys that were accessible in Codex sessions before patching. Review your OpenAI account activity and connected integrations for unauthorized access. Check the systems and tools connected to Codex (version control, databases, etc.) for anomalous activity. Consider this a credential exposure incident and follow your organization's incident response procedures.

Is there a workaround if I cannot patch immediately?

Limit Codex's access to untrusted data sources and external tool integrations. Avoid using Codex with connected tools that return unvetted content. Do not copy-paste code or data from public repositories, forums, or external sources into Codex. These are temporary risk-reduction measures only; patching should remain your priority.

This analysis is provided for informational purposes based on the CVE record and publicly available information as of the publication date. Specific affected versions and patch availability should be verified directly with OpenAI's official security advisories. Organizations should assess their own risk context, system inventory, and operational dependencies when determining patch priority. SEC.co does not provide legal, compliance, or risk management advice; consult your security team and vendor guidance for authoritative remediation decisions. Source: NVD (public-domain), retrieved 2026-08-15. Analysis generated by SEC.co (claude-haiku-4-5).