I think I already fixed this problem in the past here:
191edf4

But it affected the version on docker hub because the python version is not updated there.
I will check how your solution affect the container and update.

By the way, the yaml.load was unsafe for a very long time, even when they stated in pyyaml 5.1 that it is supposed to be safe. E.g.:

This has been known to pyyaml for some time as reported in this issue, and it seems they finally fixed it in 5.2, e.g. the payload from the screenshot above will throw:

ConstructorError: could not determine a constructor for the tag 'tag:yaml.org,2002:python/object/apply:subprocess.Popen'
  in "<unicode string>", line 1, column 1:
    !!python/object/apply:subprocess ...
    ^

Anyway, in theory we should be fine assuming that we use pyyaml 5.2 but...

• KubiScan does not have pyyaml in its requirements.txt so it depends on its dependencies to grab proper version of pyyaml - this may end bandly e.g. if someone controls its dependencies
• From the last two comments in FullLoader is not much safer than UnsafeLoader yaml/pyyaml#321 (comment) it seems that there still might be some possibility of code execution through the default loader in 5.2, though it might be very hard to find proper gadgets

Also, this change works for me, but that's always good to do more testing :).

OK I see,
Thanks for notice.
I will try your fix