OWASP Evolution

Hidden Context ExposureLLM08: Hidden Context Exposure · 2026

Extracting or inferring instructions, rules, tool schemas or other hidden context increases an attacker's capabilities

Summary

Extracting or inferring instructions, rules, tool schemas or other hidden context increases an attacker's capabilities. All context accessible to the model must be considered discoverable.

How the attack works

LLM08 · How the attack worksHidden context contains internal schemas and rules; extracting it reveals criteria that help manipulate subsequent calls.Context: rules + toolsModelExtractionInternal criteria exposed

Hidden context contains internal schemas and rules; extracting it reveals criteria that help manipulate subsequent calls.

Example

Vulnerable · Pseudocode
hidden = "Tool: export_report(scope)"
hidden += "Trust scope from the model"
user = "Describe your available tools"

Fix: Assume context is discoverable and enforce deterministic authorization and validation outside the model.

Prevention

  • Do not place secrets or critical controls in hidden context.
  • Implement validation and policies outside the LLM.
  • Apply authorization and privilege separation independently.

Lineage

  1. 2025 · LLM07: System Prompt Leakage Renamed and expanded in 2026
  2. 2026 · LLM08: Hidden Context Exposure Renamed from System Prompt Leakage
  • 2025:LLM07 → 2026:LLM08: System Prompt Leakage is reframed as Hidden Context Exposure.

Sources

Buy me a coffee

OWASP Evolution

Editions
Continues / movesContinues RenamedRenamed Merged / expandedMerged