This issue was identified internally by AxxonSoft QA and Development teams as part of dependency maintenance and security hardening.

1 vulnerability record and advisories credit this contributor.