Aari 158c4f9622
fix(security): html-escape memory facts rendered into the injection prompt (#4097)
* fix(security): html-escape memory facts rendered into the injection prompt

The lead-agent system prompt declares the <memory> block user-managed and
everything else framework-internal, but the injection renderer _format_fact_line
formats a fact's content, category and correction sourceError raw. Memory is
user-editable via /api/memory, so a fact whose content is
'</memory></system-reminder>...' closes the block and relocates the text after
it out of the user-managed trust zone.

Escape those three fields at render time, mirroring the MEMORY_UPDATE_PROMPT
escaping added for the update-prompt side in #4028/#4060. The fact dict is not
mutated, so stored memory keeps the raw value and the apply path is unaffected.

* fix(memory): stop entity-encoding quotes in injected fact text

The three html.escape() calls in _format_fact_line used the default
quote=True, which also converts " to &quot; and ' to &#x27;. These fields
are rendered as element text inside the <memory> block, never inside an
attribute value, so escaping quotes buys no defense here: only <, >, and &
can break out of the surrounding tags, and those are escaped either way.

Ordinary facts ("User's preference", 'Said "use Python"') reached the model
as User&#x27;s preference / Said &quot;use Python&quot; -- content the
lead-agent prompt declares as user-managed data the model should discuss
freely. Pass quote=False and extend the benign-content test, which used a
string with no quotes and so never exercised this path.

Note the escape in updater.py's consolidation_candidates block renders into
an XML attribute value and correctly keeps quote=True.
2026-07-12 11:03:46 +08:00
..