GPT-5-Nano profile
GPT-5-Nano — security & risk dashboard
Known weaknesses, safety and security advisories, and documented real-world incidents for GPT-5-Nano — collected automatically and re-checked every few hours, so teams building on it can see what to design around.
Last checked 18 Oct 2026
Known flaws
5
Security risks
3
Real-world incidents
0
Advisories logged
0
Security, safety & abuse risks
- Prompt injection remains a GPT-5-family concern when applications process untrusted content or expose tools.
- Incorrect or fabricated answers can mislead users when generated claims are treated as verified facts.
- Model-level safety protections do not eliminate harmful-output risks or replace application-level access controls.
Known flaws & limitations
- The documented knowledge cutoff is May 31, 2024; newer facts require external information.
- Native audio and video inputs are not supported.
- Output is text-only; native image and audio generation are not supported.
- The 400,000-token context window is smaller than GPT-4.1 nano's 1,047,576-token window.
- OpenAI's launch evaluations show lower GPQA Diamond and AIME 2025 performance than GPT-5 mini and GPT-5.
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
- Native audio or video processing and image or audio generation.
- High-stakes decisions without independent verification and qualified human review.
- Tasks requiring current factual knowledge without retrieval or other external information.
- Workloads requiring approximately one million tokens in a single context.
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.