Github user michaelandrepearce commented on the issue:
https://github.com/apache/activemq-artemis/pull/2093
@clebertsuconic well the bug is been there for ages, just more
evident/exposed since 2.5.0 where security check was corrected, so made it more
apparent. If its easy to re-spin 2.6.0 yes i would probably re-spin it.
It is a blocker for my org, as pre-2.5.0 with the security we have as the
bug in security hid the bug in client code, so i would imagine it could be a
blocker for other users.
---
