<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Data-Exposure on CuraSec</title><link>https://curasec.metacog.co.kr/tags/data-exposure/</link><description>Recent content in Data-Exposure on CuraSec</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 21 Aug 2026 11:38:25 +0000</lastBuildDate><atom:link href="https://curasec.metacog.co.kr/tags/data-exposure/index.xml" rel="self" type="application/rss+xml"/><item><title>"Shady AI" governance risk: unauthorized AI agent data exposure</title><link>https://curasec.metacog.co.kr/insights/2026-08-21-why-shady-ai-is-security-s-next-big-governance-problem/</link><pubDate>Fri, 21 Aug 2026 11:38:25 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-08-21-why-shady-ai-is-security-s-next-big-governance-problem/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Learn:&lt;/strong> The Meta incident illustrates how approved AI agents can inadvertently exfiltrate data to unintended audiences; worth reviewing how AI tooling in your CI/CD or dev workflows handles authorization boundaries before posting or sharing outputs.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> The case demonstrates a new category of data-loss event driven by AI agent behavior rather than malicious actors; consider whether current DLP and logging coverage would detect unauthorized AI-driven data postings in internal tools.&lt;/li>
&lt;li>&lt;strong>Leader — Plan:&lt;/strong> This is an emerging governance gap requiring policy before controls; establish an AI agent usage policy this quarter that defines approval workflows, data-scope restrictions, and incident classification criteria for AI-driven exposure events.&lt;/li>
&lt;/ul></description></item><item><title>Adobe Acrobat Chrome Extension Exposed WhatsApp Web Chat Data</title><link>https://curasec.metacog.co.kr/insights/2026-07-23-adobe-chrome-extension-flaw-let-sites-access-private-whatsap/</link><pubDate>Thu, 23 Jul 2026 12:47:45 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-23-adobe-chrome-extension-flaw-let-sites-access-private-whatsap/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> Audit enterprise Chrome extension policies to confirm the Adobe Acrobat extension is at current patched version; consider restricting extension permissions via managed browser policy if update cadence is slow.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No active exploitation or IOCs reported; file as a reference for understanding cross-origin data leakage via browser extension privilege abuse if hunting similar patterns later.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;/ul></description></item><item><title>Adobe Acrobat Chrome Extension Flaw Exposed WhatsApp Web Data</title><link>https://curasec.metacog.co.kr/insights/2026-07-23-adobe-acrobat-extension-flaw-let-malicious-sites-read-whatsa/</link><pubDate>Thu, 23 Jul 2026 12:47:45 +0000</pubDate><guid>https://curasec.metacog.co.kr/insights/2026-07-23-adobe-acrobat-extension-flaw-let-malicious-sites-read-whatsa/</guid><description>&lt;ul>
&lt;li>&lt;strong>Engineer — Plan:&lt;/strong> The patched Adobe Acrobat Chrome extension (CVE-2026-48294) could allow malicious sites to silently read WhatsApp Web session data; public PoC exists but EPSS is 0.01 and KEV-unlisted. Audit enterprise browser policies and confirm the extension has been updated to the patched version across managed endpoints.&lt;/li>
&lt;li>&lt;strong>SOC/IR — Learn:&lt;/strong> No active exploitation campaign or IOCs published; the HermeticReader attack chain demonstrates how a privileged browser extension can be abused to silently cross-read web app data — useful context for evaluating browser extension detection coverage but no immediate hunt or rule-write warranted.&lt;/li>
&lt;li>&lt;strong>Leader — Skip&lt;/strong>&lt;/li>
&lt;li>&lt;strong>Signals:&lt;/strong> CVE-2026-48294 — CISA KEV: not listed, EPSS 0.01, public PoC on GitHub&lt;/li>
&lt;/ul></description></item></channel></rss>