EAT supports terminal selection-control sequences, commonly called OSC 52. Trust therefore extends to any local program, SSH peer, router, or other output source that reaches its parser. Displaying an untrusted file through a program that does not sanitise control sequences can also exercise this interface.
In the audited EAT 0.9.4 release, eat-enable-kill-from-terminal defaults to
non-nil. Despite its name, this is the terminal-to-Emacs direction: a terminal
program can place text in the kill ring. eat-enable-yank-to-terminal defaults
to nil for security; enabling it lets a terminal program request current
kill-ring text. Check the installed defaults again after an EAT upgrade.
For output you do not fully trust, disable both directions globally through Customize or locally in the EAT buffer:
(setq-local eat-enable-kill-from-terminal nil
eat-enable-yank-to-terminal nil)
Evaluate this with M-: in that buffer before processing untrusted output. Reserve kill-ring read-back for programs and remote endpoints trusted with whatever the kill ring currently contains.
Emacsvox changes neither option. A terminal-originated selection payload is not an accessibility command: its contents are neither spoken nor retained as terminal screen text. Content-free paste announcements apply to explicit user paste commands, not these terminal-originated sequences.