Gemini 2.5 Pro Preview 06 05 profile
Gemini 2.5 Pro Preview 06 05 — security & risk dashboard
Known weaknesses, safety and security advisories, and documented real-world incidents for Gemini 2.5 Pro Preview 06 05 — collected automatically and re-checked every few hours, so teams building on it can see what to design around.
Last checked 26 Oct 2026
Known flaws
5
Security risks
3
Real-world incidents
0
Advisories logged
0
Security, safety & abuse risks
- Untrusted documents, webpages and tool responses can introduce prompt-injection risks in agentic applications.
- Safety filtering does not eliminate the possibility of harmful or misleading outputs.
- Generated code can introduce security vulnerabilities when deployed without review and testing.
Known flaws & limitations
- Reasoning, factual answers and generated code can contain errors and require independent validation.
- Thinking adds latency and consumes billable output tokens; thinking cannot be disabled for Gemini 2.5 Pro.
- A large context window does not guarantee reliable retrieval or reasoning across every detail.
- The listed prices are historical USD rates per million tokens for prompts up to 200,000 tokens. Longer prompts cost $2.50 per million input tokens and $15 per million output tokens; output billing includes thinking tokens.
- This dated preview was superseded by stable Gemini 2.5 Pro and should not be treated as the current production model.
Security advisories & risk updates
No risk advisories logged since this profile started being tracked. New ones appear here automatically.
What this means if you are building on it
- New production deployments requiring a current, supported model identifier.
- Safety-critical decisions without qualified human review.
- Latency-sensitive applications that require reasoning to be disabled.
- Autonomous execution of generated code or tool actions without permission boundaries.
Everything here comes from published documentation, advisories and reporting, with links to the original sources. It is not a complete vulnerability database — always check the provider's own security notices before shipping.