AI Risk Wire

Cases › produced harmful content › LR-2026-0407

Google Translate Gemini mode vulnerable to prompt injection

Preliminary Why: Publisher not yet named · subject to change

Developing: a major or severe case captured in the last 72 hours. Later changes are logged on the corrections page.

Status: no action reported

Severity major
Reported 10 Feb 2026

No source states: loss or records, developer and model, agent tool, could do, deployer, industry.

Google Translate’s Gemini-based translation feature appears to be affected by prompt injection, in what is reported to be its Advanced mode. A user who entered a question in a foreign language followed by an English meta-instruction caused the service to answer the question instead of translating it. Security researchers reported that the technique could produce dangerous content, including instructions for making drugs and malware. A Tumblr user first discovered the behaviour, and it was publicised by a jailbreaker and reported in the press. As of February 10, 2026, the vulnerability remained active in production, and Google had not issued a public statement or a timeline for a fix.

What happened

1 · What it was doingA user enters a question in a foreign language and adds an English meta-instruction below it, asking the system to answer the question.
2 · What went wrongThe service answered the question instead of translating the text.
3 · What it reached or didAccording to security researchers, the exploit could produce dangerous content, including instructions for making drugs and malware.
4 · How it was caughtA Tumblr user discovered the behaviour and it was reported publicly.

What was done

No source states an action or fix.

Risks

Read from the sources; not yet reviewed by a person.

Controls

Not yet read for controls. Controls that mitigate the primary risk:

Harness

Outside content treated as data, not instructions · Prompt-injection detection · Confirmation after untrusted input · Validation of tool inputs and outputs · Tool allow-list

Application

Human approval for high-impact actions · Least-privilege access for the agent · Segmentation of agent components · Alerts on unusual tool use

Evidence

No source states: when it happened, when it was found, how many records were exposed, the direct loss, a count of the other parties affected, any court case, the cause, what was done.

Show the full account: 4 items from the primary sources

What happened, in order

  1. late 2025 Advanced mode, which the vulnerability appears to affect, rolled out.
  2. 2025-12 Google’s Gemini integration with Google Translate was part of a broader upgrade.
  3. 2025-10 Similar Gemini security flaws were documented, and Google refused to fix them.
  4. 2026-02-10 The vulnerability remained active in the production system.
Show every field, with its source and grade

The AI system

Stage of use
in live use
C one secondary source states it

What happened

Earliest source we hold
2026-02-10
D inferred by us from the described behaviour, reason shown
What set it off
hidden instructions in its input
C one secondary source states it
Who caught it
an independent researcher or journalist
C one secondary source states it
What went wrong
produced harmful content
D inferred by us from the described behaviour, reason shown
primary risk
RK01
D inferred by us from the described behaviour, reason shown
secondary risks
RK12
D inferred by us from the described behaviour, reason shown

Impact

Severity
major
D inferred by us from the described behaviour, reason shown

Notes on gaps

Not stated: the exact Gemini model (the system's self-claim of Gemini 1.5 Pro was judged unreliable by the source and is not recorded), the date the flaw occurred or was detected, the disclosure date, the number of affected users or any count of affected parties, any financial loss, and any remediation. Pliny the Liberator's claims are reported as the source reports them, not verified. The article's architectural claims are opinion-like and are attributed to the source, not stated as fact.

LR-2026-0407 · version 1 · published 2026-11-01 after automatic checks; not yet checked field by field by a person · JSON