Parser and execution boundaries
High-impact cases where structured input, archives, queries, or serialized objects crossed into an interpreter or unsafe write primitive.
Pattern collection. This is original synthesis across public, source-verified disclosures; severity labels remain exactly as reported by each source.
Field lens
The key question is where data stops being data. Strong evidence identifies the interpreter, parser, extraction root, query engine, or process-launch boundary and confirms the smallest benign effect.
Evidence that changes the decision
- A controlled value changes command, query, object, or filesystem behavior.
- A non-executing control distinguishes parser behavior from a coincidental error.
- The disclosure bounds the execution or write context instead of assuming full compromise.
Control themes
- Use data-only parsers and parameterized APIs instead of evaluators or string-built commands.
- Canonicalize archive output paths and keep extraction inside a dedicated root.
- Apply least privilege so a parser or worker cannot turn one mistake into platform-wide access.