The issue was indeed a bug in the latest Discourse version. Communiteq is patching it on my forum instance. For more info see here: