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 motivated me to fix our renovate setup, and this got fixed in https://github.com/bootc-dev/bootc/pull/1566
Note our tracing setup changed in https://github.com/bootc-dev/bootc/pull/1522/commits/bf74ecbcc3fdefeaab598cb3fb6d06d926691021 - We only logged messages at ERROR level or above before - There's very little usage of tracing::error! in our code base, only a few hits - Almost all input that is provided comes from privileged code anyways Hence I don't think we need to do any special releases for this and can just roll the fix into our next scheduled release. OR TL;DR I think bootc is not vulnerable to this.