More information about this security flaw is available in the following bug: https://bugzilla.redhat.com/show_bug.cgi?id=2262225 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.
I'm not clear why SingularityCE has been added to this vuln / incident at this time? Our BuildKit versions in use are: EPEL8 - Provides: bundled(golang(github.com/moby/buildkit)) = v0.15.1 EPEL9 - Provides: bundled(golang(github.com/moby/buildkit)) = v0.15.1 F41 - Provides: bundled(golang(github.com/moby/buildkit)) = v0.15.2 F40 - Provides: bundled(golang(github.com/moby/buildkit)) = v0.15.2 All of these are well above the vulnerable <=v0.12.4 If the issue lies with our use of buildkit, despite it being a newer version, then the reporter will need to explain why / how we are vulnerable.
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days