# CVE-2024-45049: Nix Hydra Missing authentication when triggering evaluations

> Attackers can trigger unauthenticated evaluations in Nix Hydra, potentially causing denial of service by consuming system resources.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Aug 2024
- **Updated:** 28 Aug 2024
- **Also known as:** GHSA-xv29-v93r-2f5v

## What is CVE-2024-45049?

CVE-2024-45049 is a high-severity missing authorization vulnerability in NixOS hydra, published on 27 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Hydra is a Continuous Integration service for Nix based projects. It is possible to trigger evaluations in Hydra without any authentication. Depending on the size of evaluations, this can impact the availability of systems. The problem can be fixed by applying https://github.com/NixOS/hydra/commit/f73043378907c2c7e44f633ad764c8bdd1c947d5 to any Hydra package. Users are advised to upgrade. Users unable to upgrade should deny the `/api/push` route in a reverse proxy. This also breaks the "Evaluate jobset" button in the frontend.

Weakness: CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2024-45049?

It affects 1 product.


Products: Nixos Hydra.

## How do I fix CVE-2024-45049?

No fix has been published for CVE-2024-45049 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-45049 being exploited?

There is no known exploitation of CVE-2024-45049 in the wild and no public exploit code.

## Other vulnerabilities in NixOS hydra

- [CVE-2025-54800](https://insights.sbomify.com/CVE-2025-54800/): Hydra persistent XSS in build metrics (high 7.1)
- [CVE-2025-54864](https://insights.sbomify.com/CVE-2025-54864/): Hydra missing authentication when triggering evaluations through GitHub and Gitea plugins (medium 6.9)
- [CVE-2024-32657](https://insights.sbomify.com/CVE-2024-32657/): Hydra has persistent XSS vulnerability serving HTML build outputs (medium 4.6)
- [CVE-2025-32435](https://insights.sbomify.com/CVE-2025-32435/): Hydra no restricted eval after nix-eval-jobs migration (low 2.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-45049 and fix it if it is affected.

What it is: CVE-2024-45049 is a high-severity missing authorization vulnerability in NixOS hydra, published on 27 Aug 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-45049 in the wild and no public exploit code.

Affected product: NixOS hydra. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-45049/ (Markdown: https://insights.sbomify.com/CVE-2024-45049/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-45049
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-45049
- OSV: https://osv.dev/vulnerability/CVE-2024-45049

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-45049/
Summaries are generated and may contain mistakes; the official description above is the record.