In chainmaker-go (aka ChainMaker) before 2.3.6, multiple updates to a single nodes configuration can cause other normal nodes to perform concurrent read and write operations on a map, leading to a panic.
The product utilizes a shared resource in a concurrent manner, but it does not correctly synchronize access to the resource.