‘Bleeding Llama’ Vulnerability in Ollama Expose Entire Process Memory
Ollama Deployments under attack
Continue ReadingOllama Deployments under attack
Continue ReadingMicrosoft 365 Copilot Vulnerability Bypasses DLP Policies, Summarizes Confidential Emails; Bug Tracked CW1226324
Summary :
A recently disclosed issue in Microsoft 365 Copilot caused the AI assistant to summarize confidential emails despite sensitivity labels and Data Loss Prevention (DLP) policies being configured.
The bug, tracked under CW1226324, allowed Copilot’s “Work Tab” chat feature to process and summarize emails from Sent Items and Draft folders, even when those emails carried confidentiality labels designed to restrict automated access.
Microsoft findings
Microsoft’s investigation revealed a code-level defect as the root cause. The flaw allows Copilot to inadvertently pick up items stored in users’ Sent Items and Draft folders, bypassing the confidentiality labels applied to those messages.
Although Microsoft categorized the issue as an advisory with potentially limited scope, the incident raises significant concerns regarding AI governance, trust boundaries, and enterprise data protection controls.
As per CSN the flaw allows Copilot to inadvertently pick up items stored in users’ Sent Items and Draft folders, ignoring the confidentiality labels applied to those messages.
Vulnerability Details
The issue happened because of an internal coding mistake in Microsoft 365 Copilot’s Work Tab chat feature. Due to this error, Copilot was able to access emails stored in Sent and Draft folders, even if they were marked as confidential.
In normal conditions, sensitivity labels and DLP policies should block automated tools from processing such emails.
However, because of this flaw, Copilot treated those protected emails as regular content and created summaries from them until Microsoft began deploying a fix in February 2026.

Attack Flow
| Step | Description |
| Configuration | Organization applies confidentiality labels and DLP policies to sensitive emails. |
| Storage | Emails are stored in Sent Items or Draft folders. |
| Trigger | User interacts with Copilot “Work Tab” Chat. |
| Processing | Due to the code bug, Copilot accesses labeled emails. |
| Exposure | Copilot generates summaries of confidential content, bypassing expected DLP enforcement. |

Source:0din
Why It’s Effective
Broader Implications
This issue shows that AI tools inside business software can sometimes ignore security rules, even when protection like DLP and sensitivity labels are properly set. It proves that AI systems can create new risk areas that traditional security controls may not fully cover.
As more companies use AI assistants in daily work, security teams must regularly test and monitor how AI handles sensitive data. AI should be treated like a powerful internal system that needs strict oversight, not just a simple productivity feature.
Remediation:
Microsoft has initiated a fixed rollout and is monitoring deployment progress. However, organizations should take proactive measures:
Conclusion:
This incident highlights that AI integrations can introduce unexpected security gaps, even in well-configured enterprise environments. Organizations cannot assume that existing security controls will automatically work the same way with AI-powered features.
As AI adoption increases, companies must strengthen AI governance, continuously validate security policies, and monitor AI behavior just like any other critical system. Proactive testing and oversight are essential to prevent future data exposure risks.
Bypassing DLP policies by AI aided assistants signals huge security gap which needs to be addressed at enterprise level as AI tool taking over enterprise security posture cannot be undermined.
References:
Summary
Be careful when you open that file in whatapp, it might have that spoofing flaw allowing Arbitrary Code Execution (CVE-2025-30401) and affects all versions of WhatsApp Desktop for Windows prior to 2.2450.6, and stems from a bug .
Overview
The vulnerability has been fixed in version 2.2450.6. WhatsApp has and will always be an attractive field for attackers and this particular bug does require user interaction – the victim has to manually open the malicious attachment for the payload to run.
| Vulnerability Name | CVE ID | Product Affected | Severity | Fixed Version |
| Spoofing Vulnerability | CVE-2025-30401 | WhatsApp Desktop for Windows | Medium | 2.2450.6 |
Technical Summary
The vulnerability results from WhatsApp for Windows’s different handling of attachments. It opens files depending on their filename extension while displaying files based on their MIME type. This mismatch allows attackers to spoof file types and trick users into launching malicious executables.
Example Scenario:
An attacker sends a file named cat.jpg.exe with a MIME type of image/jpeg. WhatsApp displays the file as an image (because of the MIME type), misleading the user. If the user manually opens the attachment from within WhatsApp, Windows uses the .exe extension to execute the file — potentially launching malicious code.
This form of UI spoofing can be especially effective in group chats, where malicious attachments may be distributed widely and appear harmless.
| CVE ID | System Affected | Vulnerability Details | Impact |
| CVE-2025-30401 | WhatsApp Desktop for Windows (<2.2450.6) | MIME type used for display, but file extension used for execution. A mismatch between the two could allow a file to appear harmless (e.g., image), while actually being executable (e.g., .exe). | Remote Arbitrary code execution |
Remediation:
Conclusion:
CVE-2025-30401 is a key example of how inconsistent file processing in the user interface can result in serious security threats. Attackers can create misleading payloads that can run arbitrary code by taking advantage of users’ faith in how apps display attachments.
Due to the possibility of remote exploitation, users should update to the latest WhatsApp version 2.2450.6 or later. Patching should be done right away to avoid any compromise.
Be careful when you click attachments.
References:
Recent Comments