Details
prompt_embeds is far more familiar here than M-RoPE, and it is understood that each model that supports it is responsible for defining its own get_mrope_input_positions which have varying implementations. There is insufficient knowledge to be prescriptive in how the two features should interact in the offline case, other than possibly raising a validation error earlier on preventing that combination (which would emulate the current assertion behavior). Regardless, in offline mode, the chances of a remote user being able to exploit this are slim-to-nil compared to the online case which is incredibly straightforward.
Impact
_What kind of vulnerability is it? Who is impacted?_
- Denial of Service caused by an incorrect assertion inside of the
GPUModelRunnerwhich causes a fatal EngineCore exception - Any configuration with
--enable-prompt-embedsand M-RoPE-supported model is vulnerable - The attack is extremely easy from the remote attacker's perspective (copying the official
prompt_embedsonline mode docs examples almost-verbatim, accounting for model-name and connection details, of course, will induce a guaranteed shutdown)