Risks
What prompt injection puts at risk
A successful injection can expose data, trigger actions the owner never intended or skew decisions. How much harm follows depends on what the tool can reach.
Last reviewed against NCSC, OWASP GenAI Security Project and Microsoft Security Response Center. Sources
The outcomes
Four things that go wrong
OWASP lists the consequences of a successful attack: disclosure of sensitive information, harmful content, unauthorised access and manipulated decisions [2]. Each needs a different control.
Data leaves the building
Tools act on the attacker's behalf
The NCSC warns that an attacker who can inject prompts effectively gains the capabilities of the tools the LLM can reach [1]. A mail assistant with send rights can send.
Decisions drift
OWASP describes a tampered document in a retrieval repository steering a model towards misleading output [2]. The harm is a wrong answer people trust.
Hidden instructions in ordinary files
OWASP's examples include a job description with a concealed instruction, which a candidate's optimised CV then triggered by accident [2]. Injection need not be hostile to cause trouble.
Agents
Why autonomy raises the stakes
OpenAI concedes that the agent feature in its ChatGPT Atlas browser enlarges the area open to attack [5]. In its demonstration, a hostile email led an agent to send a resignation message in place of an out-of-office reply [5]. Wiz's Rami McCarthy argues that agentic browsers combine moderate autonomy with very high access to sensitive data [5].
A measure to ask for
OpenAI would not say whether its latest update measurably reduced successful injections [5]. Ask any supplier for evidence, not assurances.
Key facts
Prompt injection in brief
- OWASP ranking
- LLM01 in the 2025 Top 10 for LLM applications[2]
- NCSC view
- May never be totally mitigated; reduce likelihood and impact[1]
- Two main forms
- Direct (user input) and indirect (hidden in external content)[2]
- Worked case
- EchoLeak, CVE-2025-32711, CVSS 9.3, fixed by Microsoft[4]
- Risky combination
- Private data, untrusted content and outward communication[6]
- OpenAI's position
- Unlikely ever to be fully solved[5]
Keep reading
Read next
Plan
A practical prompt injection plan for UK organisations: map untrusted content, limit tool access, add approvals, keep logs and test, in order.
Read the guide
Examples
Prompt injection examples from OWASP's catalogue, from a support chatbot to hidden image instructions, with what each means for UK teams.
Read the guide
Direct vs indirect
How direct and indirect prompt injection differ, why indirect injection is the harder problem for business tools, and what each means for defence.
Read the guideHow CyPro can help
Need a hand planning for this?
Understanding the change is one job. Working out what it means for your systems, your suppliers and your roadmap is several more. CyPro's consultants can take any of them on.
Fractional CISO for the board
A senior security lead who advises the board on what to fix first, what to accept and what to tell customers, and owns the decision record.
More on cypro.co.uk
Hardening and segmentation
Our consultants put the controls in place that limit the damage when something is missed: firewall rules, network isolation and tighter admin access.
More on cypro.co.uk
Penetration testing
A focused test of your systems and the controls around them, so you know they hold before an attacker finds out for you.
More on cypro.co.uk
Vulnerability scanning
Find every internet-facing system you run, including the forgotten ones, and see which are still on a vulnerable build.
See the scanning service
24/7 security monitoring
Our SOC analysts watch your systems day and night for the signs of an attack in progress: unexpected processes, new outbound connections, logins that do not fit.
More on cypro.co.uk
Incident response
If you may already be compromised, our responders contain it, preserve the evidence, find out what was touched and get you running again safely.
More on cypro.co.uk
Plan ahead
Want a plan for your organisation?
Prompt injection only shows up when someone tries it against your own tools. Penetration testing can probe the AI features you run or build, to see what a hostile instruction could reach.