Thanks, but the patch is incorrect.  The model consistently stores its data as surrogateescaped strings, and this assumption is baked in to other parts of the code.  So the correct fix is to do the surrogateescape encoding at the time the payload is set.

It might in fact be better to store a binary payload as binary, but making that kind of change to the model requires much more extensive review and testing.