Knowledge cutoff date is disclosed where relevant
Why it matters
Language models have a training cutoff and cannot know about events, legislation, software releases, or market conditions that postdate it. When an application provides no disclosure — neither in the system prompt nor the UI — users treat AI responses as current, leading to decisions based on outdated information. For compliance-sensitive domains (GDPR enforcement updates, securities regulations, medical guidelines), acting on stale AI output can cause real harm. NIST AI RMF GOVERN-1.1 requires transparency about AI system limitations. OWASP LLM09 identifies temporal misinformation as an LLM risk category.
Severity rationale
High because users without cutoff disclosure will act on stale AI information as if it were current, with no signal that facts, laws, or specifications may have materially changed.
Remediation
Add a cutoff disclosure to the system prompt with the model's specific training cutoff date:
const systemPrompt = `
Your knowledge cutoff is [MODEL_CUTOFF_DATE]. For questions about recent events,
current prices, active legislation, or software versions, proactively note that
your information may be outdated and direct the user to verify with a current source.
`
Alternatively, add a static footer or tooltip in the chat UI — for example, src/components/chat/ChatPanel.tsx — displaying: "AI responses reflect training data through [date]. Verify time-sensitive information independently."
DetectionPro
The detection method for this pattern is part of AuditBuffet Pro.
The full method (what to look for, pass and fail conditions, and how results get reported) ships inside the AI Response Quality Audit. The pattern definition, severity rationale, and remediation remain openly licensed under CC-BY-4.0.
External references
- owasp-llm:2025 · LLM09 — Misinformation
- nist-ai-rmf:1.0 · GOVERN 1.1 — Transparency and accountability policies
Taxons
History
- 2026-04-18·v1.0.0·Initial import from ai-response-quality·automated