You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[security] Safe-prefix cache skips injection spanning the prefix boundary #82
The default safe-prefix cache marks a verified-clean prefix, then on append-only growth scans suffix only with no overlap. An injection phrase split across the prefix boundary (e.g. prefix "Please ignore pre" then append the remainder) can evade detection even though a full re-scan (cache off) correctly blocks.
Expected / acceptance criteria
Safe-prefix reuse re-scans an overlap window at the boundary (same philosophy as StreamScanner), or safe-prefix caching is disabled by default until that exists
Fail-closed: never allow a split pattern that full-document scan would block
Regression test: cache-on append that splits a known injection phrase must BLOCK (or equivalent deny) matching cache-off behavior
Notes
Repro sketch (cache enabled, shared document_id):
Scan "Please ignore pre" → allow / advance prefix
Scan same text + remainder of injection phrase → must block like cache disabled
Related: chunk/prefix cache keys currently ignore source and policy (separate issue if not fixed together).
Output redacted_text incomplete when safe-prefix merge is used
Oversized base64 path fail-open
Remote http:// only warns (no hard fail)
Tracked in .context/plans/adversarial-issue-backlog.md.
Activity
chiruu12 commentedon Jul 20, 2026
Deferred follow-ups (not separate issues yet)
redacted_textincomplete when safe-prefix merge is usedhttp://only warns (no hard fail)Tracked in
.context/plans/adversarial-issue-backlog.md.