Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process. The following link provides references to all essential vulnerability management information. If something is wrong or missing, please contact a member of PSIRT. https://spaces.redhat.com/display/PRODSEC/Vulnerability+Management+-+Essential+Documents+for+Engineering+Teams
This security issue doesn't impact Toolbx, even though the vulnerable code is present in Toolbx's dependency chain. github.com/go-viper/mapstructure/v2 is an indirect dependency of Toolbx because of github.com/spf13/viper. Toolbx uses Viper to read and parse its configuration files, which don't have any sensitive data. Therefore, there's no sensitive data for mapstructure to leak in the logs. The github.com/go-viper/mapstructure/v2 version has been updated in Toolbx upstream, merely to keep the dependencies updated, but there's no need to do a downstream build, because there's no security issue to be addressed.