CVE-2025-54864: Hydra missing authentication when triggering evaluations through GitHub and Gitea plugins
Hydra is a continuous integration service for Nix based projects. Prior to commit f7bda02, /api/push-github and /api/push-gitea are called by the corresponding forge without HTTP Basic authentication. Both forges do however feature HMAC signing with a secret key. Triggering an evaluation can be very taxing on the infrastructure when large evaluations are done, introducing potential denial of service attacks on the host running the evaluator. This issue has been patched by commit f7bda02. A workaround involves blocking /api/push-github and /api/push-gitea via a reverse proxy.
Affected Software
Remediation
Event History
Frequently Asked Questions
What is the severity of CVE-2025-54864?
CVE-2025-54864 is classified as a medium severity vulnerability due to improper authentication in the API calls.
How do I fix CVE-2025-54864?
To fix CVE-2025-54864, upgrade to Hydra version f7bda02 or later, which implements proper HTTP Basic authentication.
What software is affected by CVE-2025-54864?
CVE-2025-54864 affects Hydra continuous integration service versions prior to f7bda02.
What kind of attack does CVE-2025-54864 enable?
CVE-2025-54864 enables unauthorized access to API endpoints without proper authentication, potentially allowing malicious actors to exploit the service.
Is there a workaround for CVE-2025-54864?
There is no recommended workaround for CVE-2025-54864; the best action is to upgrade to the secure version.