<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Chatgpt on CuraSec</title><link>https://curasec.metacog.co.kr/tags/chatgpt/</link><description>Recent content in Chatgpt on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Sat, 25 Jul 2026 12:08:50 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/chatgpt/index.xml" rel="self" type="application/rss+xml"/><item><title>ChatGPT AgentForger Flaw Enabled Rogue AI Agent Deployment via Phishing</title><link>https://curasec.metacog.co.kr/insights/2026-07-25-chatgpt-agentforger-flaw-could-deploy-rogue-workspace-agents/</link><pubDate>Sat, 25 Jul 2026 12:08:50 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-25-chatgpt-agentforger-flaw-could-deploy-rogue-workspace-agents/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Vulnerability is already patched server-side by OpenAI (June 8), but organizations using ChatGPT Workspace should audit deployed agents for any unauthorized instances created before the patch date.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Plan:&lt;/strong> Novel attack chain — phishing link silently builds and authorizes an autonomous AI agent inside the target org — is worth mapping to detection coverage; build or tune detections for unauthorized workspace agent creation and authorization events.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> This flaw illustrates AI workspace agents as a persistent-access attack surface; use it to prioritize an AI agent governance policy — defining who can authorize agents and what audit logging is required — before enterprise rollout expands.&lt;/li>
&lt;/ul></description></item></channel></rss>