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
It's not clear to me whether this CVE is due to golang-github-katalix-l2tp's use of an older Go which is subject to the upstream Golang vulnerability? In that case would updating the package to use Go 1.25.0 or 1.24.6 be sufficient to address this issue?