Kea configuration and API directives can be used to load a malicious hook library. Many common configurations run Kea as root, leave the API entry points unsecured by default, and/or place the control sockets in insecure paths.
This issue has been addressed in the following products: Red Hat Enterprise Linux 10 Via RHSA-2025:9178 https://access.redhat.com/errata/RHSA-2025:9178