{"id":66491,"date":"2026-04-09T16:02:35","date_gmt":"2026-04-09T14:02:35","guid":{"rendered":"https:\/\/www.apfelpatient.de\/?p=66491"},"modified":"2026-04-09T16:04:02","modified_gmt":"2026-04-09T14:04:02","slug":"apple-intelligence-vulnerable-to-prompt-injection","status":"publish","type":"post","link":"https:\/\/www.apfelpatient.de\/en\/news\/apple-intelligence-anfaellig-fuer-prompt-injection","title":{"rendered":"Apple Intelligence vulnerable to prompt injection attacks"},"content":{"rendered":"

Security researchers have demonstrated that Apple's on-device AI can be manipulated through targeted input. The success rate was 76 percent \u2013 potentially affecting hundreds of thousands of users.<\/strong><\/p>\n\n\n\n

Apple has positioned Apple Intelligence as a privacy-friendly alternative to cloud-based AI systems: A local language model runs directly on the device, while more complex tasks are processed via private cloud computing. However, this deep integration into the operating system poses risks. Researchers at RSAC Research have demonstrated<\/a> that the on-device model can be manipulated using prompt injection techniques \u2013 with a success rate of 76 percent in 100 tests.<\/p>\n\n\n\n

The results were communicated to Apple on October 15, 2025. The study focused on the local Large Language Model, which is embedded in Apple's operating systems and also available to third-party apps via system APIs. The researchers demonstrate that the deeper system integration, which Apple deliberately chose, simultaneously increases the attack surface.<\/p>\n\n\n\n

How the attack works<\/h2>\n\n\n\n

The researchers combined two techniques to circumvent Apple's security measures. The first method, called "Neural Exec," uses specially constructed inputs that appear meaningless to humans but are interpreted by the language model as concrete instructions.<\/p>\n\n\n\n

The second technique utilizes a Unicode function: the so-called right-to-left override. This allows text sections to be visually reversed, making embedded instructions invisible to human reviewers \u2013 the language model, however, reads them correctly. Combined, both methods bypass both the model's internal protection mechanisms and external filters.<\/p>\n\n\n\n

The result: The model can be made to generate outputs that are controlled by the attacker.<\/p>\n\n\n\n

Why this is problematic<\/h2>\n\n\n\n

The risk extends far beyond unwanted text output. Because Apple Intelligence connects directly to apps via system APIs, manipulated responses can influence app behavior or expose sensitive user data. A successful prompt injection attack could affect multiple apps and system-wide functions simultaneously.<\/p>\n\n\n\n

RSAC estimates that between 100,000 and one million users are already using apps that are potentially vulnerable. As more and more apps integrate Apple intelligence features, the number of potential attack targets is constantly growing.<\/p>\n\n\n\n

Attackers do not need direct access to the model itself \u2013 it is sufficient to send manipulated input via legitimate APIs. This makes the attack particularly difficult to detect and prevent.<\/p>\n\n\n\n

Apple's reaction<\/h2>\n\n\n\n

According to the researchers, Apple already strengthened security measures with iOS 26.4 and macOS 26.4, without publicly disclosing the specific changes. The recent collaboration with Anthropic within the framework of Project Glasswing<\/a> demonstrates that Apple increasingly intends to enhance the security of its systems using AI-powered methods.<\/p>\n\n\n\n

At the time of publication, there is no evidence that the vulnerability is being actively exploited \u2013 the attack is currently purely theoretical. However, the techniques used, such as prompt injection and Unicode manipulation, are well-documented in security research and relatively easy to implement.<\/p>\n\n\n\n

What this means for Apple Intelligence<\/h2>\n\n\n\n

The results reveal a fundamental tension in Apple's AI strategy. While the decision to run models locally limits data exposure to the cloud, it simultaneously makes the operating system the gatekeeper and execution layer. If the safeguards fail, the consequences are correspondingly far-reaching.<\/p>\n\n\n\n

Apple's approach remains the right one from a data privacy perspective. However, RSAC research shows that local models are not automatically more secure than cloud-based systems. Actual security depends on how well a model can defend against adversarial input \u2013 regardless of where it runs. (Image: Shutterstock \/ Primakov)<\/p>\n\n\n\n