Nixpkgs security tracker

Login with GitHub

Published issues

All published security issues are tracked and resolved on GitHub.

NIXPKGS-2026-0964
published on
Permalink CVE-2026-34976
10.0 CRITICAL
  • CVSS version: 3.1
  • Attack vector (AV): NETWORK
  • Attack complexity (AC): LOW
  • Privileges required (PR): NONE
  • User interaction (UI): NONE
  • Scope (S): CHANGED
  • Confidentiality impact (C): HIGH
  • Integrity impact (I): HIGH
  • Availability impact (A): HIGH
updated 3 weeks, 5 days ago by @LeSuisse Activity log
  • Created suggestion
  • @LeSuisse ignored
    5 packages
    • coqPackages.dpdgraph
    • perlPackages.GDGraph
    • perl5Packages.GDGraph
    • perl538Packages.GDGraph
    • perl540Packages.GDGraph
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Dgraph Affected by Pre-Auth Database Overwrite + SSRF + File Read via restoreTenant Missing Authorization

Dgraph is an open source distributed GraphQL database. Prior to 25.3.1, the restoreTenant admin mutation is missing from the authorization middleware config (admin.go), making it completely unauthenticated. Unlike the similar restore mutation which requires Guardian-of-Galaxy authentication, restoreTenant executes with zero middleware. This mutation accepts attacker-controlled backup source URLs (including file:// for local filesystem access), S3/MinIO credentials, encryption key file paths, and Vault credential file paths. An unauthenticated attacker can overwrite the entire database, read server-side files, and perform SSRF. This vulnerability is fixed in 25.3.1.

Affected products

dgraph
  • ==< 25.3.1

Matching in nixpkgs

Ignored packages (5)

Package maintainers

NIXPKGS-2026-0963
published on
Permalink CVE-2026-34371
6.3 MEDIUM
  • CVSS version: 3.1
  • Attack vector (AV): NETWORK
  • Attack complexity (AC): HIGH
  • Privileges required (PR): LOW
  • User interaction (UI): NONE
  • Scope (S): CHANGED
  • Confidentiality impact (C): NONE
  • Integrity impact (I): HIGH
  • Availability impact (A): NONE
updated 3 weeks, 5 days ago by @LeSuisse Activity log
  • Created suggestion
  • @LeSuisse deleted maintainer @niklaskorz maintainer.delete
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
LibreChat Affected by Arbitrary File Write via `execute_code` Artifact Filename Traversal

LibreChat is a ChatGPT clone with additional features. Prior to 0.8.4, LibreChat trusts the name field returned by the execute_code sandbox when persisting code-generated artifacts. On deployments using the default local file strategy, a malicious artifact filename containing traversal sequences (for example, ../../../../../app/client/dist/poc.txt) is concatenated into the server-side destination path and written with fs.writeFileSync() without sanitization. This gives any user who can trigger execute_code an arbitrary file write primitive as the LibreChat server user. This vulnerability is fixed in 0.8.4.

Affected products

LibreChat
  • ==< 0.8.4

Matching in nixpkgs

pkgs.librechat

Open-source app for all your AI conversations, fully customizable and compatible with any AI provider

Package maintainers

Ignored maintainers (1)
NIXPKGS-2026-0962
published on
Permalink CVE-2026-35533
7.8 HIGH
  • CVSS version: 3.1
  • Attack vector (AV): LOCAL
  • Attack complexity (AC): HIGH
  • Privileges required (PR): NONE
  • User interaction (UI): REQUIRED
  • Scope (S): CHANGED
  • Confidentiality impact (C): HIGH
  • Integrity impact (I): HIGH
  • Availability impact (A): HIGH
updated 3 weeks, 5 days ago by @LeSuisse Activity log
  • Created suggestion
  • @LeSuisse ignored
    10 packages
    • haskellPackages.promises
    • python312Packages.promise
    • python313Packages.promise
    • python314Packages.promise
    • ocamlPackages.promise_jsoo
    • python312Packages.heatmiserv3
    • python313Packages.heatmiserv3
    • python314Packages.heatmiserv3
    • haskellPackages.unsafe-promises
    • ocamlPackages_latest.promise_jsoo
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
mise has a local settings bypass config trust checks

mise manages dev tools like node, python, cmake, and terraform. From 2026.2.18 through 2026.4.5, mise loads trust-control settings from a local project .mise.toml before the trust check runs. An attacker who can place a malicious .mise.toml in a repository can make that same file appear trusted and then reach dangerous directives such as [env] _.source, templates, hooks, or tasks.

Affected products

mise
  • ==>= 2026.2.18, <= 2026.4.5

Matching in nixpkgs

Ignored packages (10)

Package maintainers

NIXPKGS-2026-0961
published on
updated 3 weeks, 5 days ago by @LeSuisse Activity log
  • Created suggestion
  • @LeSuisse ignored
    8 packages
    • botan2
    • emiluaPlugins.botan
    • python312Packages.botan3
    • python313Packages.botan3
    • python314Packages.botan3
    • haskellPackages.botan-low
    • haskellPackages.botan-bindings
    • chickenPackages_5.chickenEggs.botan
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Botan has a certificate authentication bypass due to trust anchor confusion

Botan is a C++ cryptography library. In 3.11.0, the function Certificate_Store::certificate_known had a misleading name; it would return true if any certificate in the store had a DN (and subject key identifier, if set) matching that of the argument. It did not check that the cert it found and the cert it was passed were actually the same certificate. In 3.11.0 an extension of path validation logic was made which assumed that certificate_known only returned true if the certificates were in fact identical. The impact is that if an end entity certificate is presented, and its DN (and subject key identifier, if set) match that of any trusted root, the end entity certificate is accepted immediately as if it itself were a trusted root. , This vulnerability is fixed in 3.11.1.

Affected products

botan
  • ==>= 3.11.0, < 3.11.1

Matching in nixpkgs

Ignored packages (8)

pkgs.botan2

Cryptographic algorithms library

Package maintainers

NIXPKGS-2026-0960
published on
updated 3 weeks, 5 days ago by @LeSuisse Activity log
  • Created suggestion
  • @LeSuisse ignored
    8 packages
    • emiluaPlugins.botan
    • python312Packages.botan3
    • python313Packages.botan3
    • python314Packages.botan3
    • haskellPackages.botan-low
    • haskellPackages.botan-bindings
    • chickenPackages_5.chickenEggs.botan
    • botan2
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Botan has a TLS 1.3 certificate authentication bypass

Botan is a C++ cryptography library. Prior to version 3.11.1, the TLS 1.3 implementation allowed ApplicationData records to be processed prior to the Finished message being received. A server which is attempting to enforce client authentication via certificates can by bypassed by a client which entirely omits Certificate, CertificateVerify, and the Finished message and instead sends application data records. This vulnerability is fixed in 3.11.1.

Affected products

botan
  • ==< 3.11.1

Matching in nixpkgs

Ignored packages (8)

pkgs.botan2

Cryptographic algorithms library

Package maintainers

NIXPKGS-2026-0959
published on
Permalink CVE-2026-35046
5.4 MEDIUM
  • CVSS version: 3.1
  • Attack vector (AV): NETWORK
  • Attack complexity (AC): LOW
  • Privileges required (PR): LOW
  • User interaction (UI): REQUIRED
  • Scope (S): CHANGED
  • Confidentiality impact (C): LOW
  • Integrity impact (I): LOW
  • Availability impact (A): NONE
updated 3 weeks, 5 days ago by @LeSuisse Activity log
  • Created suggestion
  • @LeSuisse ignored package gnome-recipes
  • @LeSuisse deleted maintainer @jvanbruegge maintainer.delete
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Tandoor has a Stored CSS Injection via <style> Tag in Recipe Instructions (API-Level)

Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. Prior to 2.6.4, Tandoor Recipes allows authenticated users to inject arbitrary <style> tags into recipe step instructions. The bleach.clean() sanitizer explicitly whitelists the <style> tag, causing the backend to persist and serve unsanitized CSS payloads via the API. Any client consuming instructions_markdown from the API and rendering it as HTML without additional sanitization will execute attacker-controlled CSS — enabling UI redressing, phishing overlays, visual defacement, and CSS-based data exfiltration. This vulnerability is fixed in 2.6.4.

Affected products

recipes
  • ==< 2.6.4

Matching in nixpkgs

pkgs.tandoor-recipes

Application for managing recipes, planning meals, building shopping lists and much much more!

Ignored packages (1)

Package maintainers

Ignored maintainers (1)
NIXPKGS-2026-0958
published on
Permalink CVE-2026-35045
8.1 HIGH
  • CVSS version: 3.1
  • Attack vector (AV): NETWORK
  • Attack complexity (AC): LOW
  • Privileges required (PR): LOW
  • User interaction (UI): NONE
  • Scope (S): UNCHANGED
  • Confidentiality impact (C): HIGH
  • Integrity impact (I): HIGH
  • Availability impact (A): NONE
updated 1 week, 5 days ago by @ADMIN Activity log
  • Created suggestion
  • @LeSuisse ignored package gnome-recipes
  • @LeSuisse deleted maintainer @jvanbruegge maintainer.delete
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
  • @LeSuisse accepted
  • @ADMIN published on GitHub
Tandoor Recipes Affected by Private Recipe Exposure and Unauthorized Modification

Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. Prior to 2.6.4, the PUT /api/recipe/batch_update/ endpoint in Tandoor Recipes allows any authenticated user within a Space to modify any recipe in that Space, including recipes marked as private by other users. This bypasses all object-level authorization checks enforced on standard single-recipe endpoints (PUT /api/recipe/{id}/), enabling forced exposure of private recipes, unauthorized self-grant of access via the shared list, and metadata tampering. This vulnerability is fixed in 2.6.4.

Affected products

recipes
  • ==< 2.6.4

Matching in nixpkgs

pkgs.tandoor-recipes

Application for managing recipes, planning meals, building shopping lists and much much more!

Ignored packages (1)

Package maintainers

Ignored maintainers (1)
NIXPKGS-2026-0957
published on
Permalink CVE-2026-35489
7.3 HIGH
  • CVSS version: 3.1
  • Attack vector (AV): NETWORK
  • Attack complexity (AC): LOW
  • Privileges required (PR): NONE
  • User interaction (UI): NONE
  • Scope (S): UNCHANGED
  • Confidentiality impact (C): LOW
  • Integrity impact (I): LOW
  • Availability impact (A): LOW
updated 3 weeks, 5 days ago by @LeSuisse Activity log
  • Created suggestion
  • @LeSuisse ignored package gnome-recipes
  • @LeSuisse deleted maintainer @jvanbruegge maintainer.delete
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Tandoor Recipes — `amount`/`unit` bypass serializer in `food/{id}/shopping/`

Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. Prior to 2.6.4, the POST /api/food/{id}/shopping/ endpoint reads amount and unit directly from request.data and passes them without validation to ShoppingListEntry.objects.create(). Invalid amount values (non-numeric strings) cause an unhandled exception and HTTP 500. A unit ID from a different Space can be associated cross-space, leaking foreign-key references across tenant boundaries. All other endpoints creating ShoppingListEntry use ShoppingListEntrySerializer, which validates and sanitizes these fields. This vulnerability is fixed in 2.6.4.

Affected products

recipes
  • ==< 2.6.4

Matching in nixpkgs

pkgs.tandoor-recipes

Application for managing recipes, planning meals, building shopping lists and much much more!

Ignored packages (1)

Package maintainers

Ignored maintainers (1)
NIXPKGS-2026-0956
published on
Permalink CVE-2026-35488
8.1 HIGH
  • CVSS version: 3.1
  • Attack vector (AV): NETWORK
  • Attack complexity (AC): LOW
  • Privileges required (PR): LOW
  • User interaction (UI): NONE
  • Scope (S): UNCHANGED
  • Confidentiality impact (C): NONE
  • Integrity impact (I): HIGH
  • Availability impact (A): HIGH
updated 3 weeks, 5 days ago by @LeSuisse Activity log
  • Created suggestion
  • @LeSuisse ignored package gnome-recipes
  • @LeSuisse deleted maintainer @jvanbruegge maintainer.delete
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Tandoor Recipes — CustomIsShared permits DELETE/PUT on RecipeBook by shared (read-only) users

Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. Prior to 2.6.4, RecipeBookViewSet and RecipeBookEntryViewSet use CustomIsShared as an alternative permission class, but CustomIsShared.has_object_permission() returns True for all HTTP methods — including DELETE, PUT, and PATCH — without checking request.method in SAFE_METHODS. Any user who is in the shared list of a RecipeBook can delete or overwrite it, even though shared access is semantically read-only. This vulnerability is fixed in 2.6.4.

Affected products

recipes
  • ==< 2.6.4

Matching in nixpkgs

pkgs.tandoor-recipes

Application for managing recipes, planning meals, building shopping lists and much much more!

Ignored packages (1)

Package maintainers

Ignored maintainers (1)
NIXPKGS-2026-0955
published on
updated 3 weeks, 5 days ago by @LeSuisse Activity log
  • Created suggestion
  • @LeSuisse ignored
    7 packages
    • mpc-qt
    • flatpak-builder
    • flatpak-xdg-utils
    • libsForQt5.flatpak-kcm
    • kdePackages.flatpak-kcm
    • plasma5Packages.flatpak-kcm
    • haskellPackages.cabal-flatpak
  • @LeSuisse deleted maintainer @getchoo maintainer.delete
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Flatpak affected by arbitrary file deletion on the host filesystem

Flatpak is a Linux application sandboxing and distribution framework. Prior to 1.16.4, the caching for ld.so removes outdated cache files without properly checking that the app controlled path to the outdated cache is in the cache directory. This allows Flatpak apps to delete arbitrary files on the host. This vulnerability is fixed in 1.16.4.

Affected products

flatpak
  • ==< 1.16.4

Matching in nixpkgs

pkgs.flatpak

Linux application sandboxing and distribution framework

Ignored packages (7)

Package maintainers

Ignored maintainers (1)