Notifications
Clear all
Topic starter
02/08/2026 12:19 pm
TL;DR: Mobile AI apps inherit prompt injection, sensitive data disclosure, supply-chain weakness, poisoning, excessive agency, and unbounded consumption risks, according to NowSecure’s analysis of the OWASP Top 10 for LLM applications. For IAM and security teams, the key issue is not just model safety but how identity, data access, and downstream authorisation controls fail around the model boundary.
NHIMG editorial — based on content published by NowSecure: the OWASP Top 10 LLM security risks for mobile applications
Questions worth separating out
Q: How should security teams govern mobile apps that use LLMs?
A: Treat the model as one component in a broader access chain, not as the control point.
Q: Why do mobile AI apps create more privacy risk than traditional apps?
A: They often pass personal data, messages, and workflow context into systems that can infer, reproduce, or redirect that information in ways the app did not anticipate.
Q: What do teams get wrong about prompt injection in mobile apps?
A: They treat it as a content filtering problem only.
Practitioner guidance
- Separate instructions from data in every mobile AI flow Keep system prompts, user input, and retrieved content in distinct trust zones, and block the model from directly influencing security-sensitive app logic without policy checks.
- Strip secrets and personal data before model submission Minimise what the mobile app sends to the model, remove PII and credentials where possible, and treat embeddings, caches, and conversation history as sensitive stores.
- Enforce downstream authorisation for every model action Do not let the model decide whether a message is sent, a calendar item is read, or a record is accessed.
What's in the full article
NowSecure's full analysis covers the operational detail this post intentionally leaves for the source:
- Line-by-line treatment of each OWASP LLM Top 10 risk in the mobile context, including app-specific examples and failure patterns.
- Practical mobile AppSec controls for model input filtering, output handling, and retrieval scoping that go beyond the strategic framing here.
- Discussion of real-world incident examples such as EmailGPT, Air Canada, and supply-chain weaknesses in mobile AI components.
- Guidance on continuous mobile testing for AI integrations, SDKs, and APIs across the application lifecycle.
👉 Read NowSecure's analysis of OWASP LLM risks in mobile apps →
Mobile LLM risks in apps: are your controls keeping up?
Explore further
02/08/2026 1:20 pm
Mobile LLM security is becoming an identity governance problem, not just an application security problem. Once a mobile assistant can read messages, calendars, health records, or financial data, the control question becomes who or what is authorised to see, infer, and act on that data. That shifts the boundary from model safety to access governance, where IAM, secrets management, and API authorisation must hold the line. Practitioners should treat mobile AI features as identity-bearing workflows rather than isolated UX enhancements.
A few things that frame the scale:
- The average estimated time to remediate a leaked secret is 27 days, despite 75% of organisations expressing strong confidence in their secrets management capabilities, according to The State of Secrets in AppSec.
- 43% of security professionals are concerned about AI systems learning and reproducing sensitive information patterns from codebases.
A question worth separating out:
Q: How can organisations reduce the blast radius of AI features in mobile apps?
A: Limit the model’s permissions, keep secrets out of prompts, and require explicit approval or policy checks before any sensitive action executes. The less authority the model has, the less damage a successful manipulation can cause. That approach is especially important for apps handling private or regulated data.
👉 Read our full editorial: Mobile LLM security risks expose gaps in AI app governance
