Nixpkgs Security Tracker

Login with GitHub

Published issues

All published security issues are tracked and resolved on GitHub.

NIXPKGS-2026-0230
published on 15 Feb 2026
updated 3 weeks ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    2 maintainers
    • @SuperSandro2000
    • @dotlambda
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
vaultwarden has Full Cipher Enumeration Ignoring Organization Collection Permissions

vaultwarden is an unofficial Bitwarden compatible server written in Rust, formerly known as bitwarden_rs. Prior to 1.35.3, a regular organization member can retrieve all ciphers within an organization, regardless of collection permissions. The endpoint /ciphers/organization-details is accessible to any organization member and internally uses Cipher::find_by_org to retrieve all ciphers. These ciphers are returned with CipherSyncType::Organization without enforcing collection-level access control. This vulnerability is fixed in 1.35.3.

Affected products

vaultwarden
  • ==< 1.35.3

Matching in nixpkgs

Package maintainers

Ignored maintainers (2)
Upstream advisory: https://github.com/dani-garcia/vaultwarden/security/advisories/GHSA-h265-g7rm-h337
NIXPKGS-2026-0249
published on 15 Feb 2026
updated 3 weeks ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed package gobusybox
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Busybox: busybox: arbitrary file overwrite and potential code execution via incomplete path sanitization

A flaw was found in BusyBox. Incomplete path sanitization in its archive extraction utilities allows an attacker to craft malicious archives that when extracted, and under specific conditions, may write to files outside the intended directory. This can lead to arbitrary file overwrite, potentially enabling code execution through the modification of sensitive system files.

Affected products

busybox

Matching in nixpkgs

Upstream patch: https://git.busybox.net/busybox/commit/archival?id=3fb6b31c716669e12f75a2accd31bb7685b1a1cb
NIXPKGS-2026-0232
published on 15 Feb 2026
updated 3 weeks ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed package gnome-recipes
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Tandoor Recipes affected by Blind SSRF with Internal Network Access via Recipe Import

Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. Prior to 2.5.1, there is a Blind Server-Side Request Forgery (SSRF) vulnerability in the Cookmate recipe import feature of Tandoor Recipes. The application fails to validate the destination URL after following HTTP redirects, allowing any authenticated user (including standard users without administrative privileges) to force the server to connect to arbitrary internal or external resources. The vulnerability lies in cookbook/integration/cookmate.py, within the Cookmate integration class. This vulnerability can be leveraged to scan internal network ports, access cloud instance metadata (e.g., AWS/GCP Metadata Service), or disclose the server's real IP address. This vulnerability is fixed in 2.5.1.

Affected products

recipes
  • ==< 2.5.1

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/TandoorRecipes/recipes/security/advisories/GHSA-j6xg-85mh-qqf7
Upstream patch: https://github.com/TandoorRecipes/recipes/commit/fdf22c5e745740db1fec29d6b4bd3df5d340e6ab
NIXPKGS-2026-0227
published on 11 Feb 2026
updated 3 weeks, 5 days ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
ckolivas lrzip stream.c lzma_decompress_buf use after free

A vulnerability was found in ckolivas lrzip up to 0.651. This impacts the function lzma_decompress_buf of the file stream.c. Performing a manipulation results in use after free. Attacking locally is a requirement. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.

Affected products

lrzip
  • ==0.651

Matching in nixpkgs

Upstream issue: https://github.com/ckolivas/lrzip/issues/262
NIXPKGS-2026-0217
published on 11 Feb 2026
updated 3 weeks, 5 days ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    23 packages
    • faraday
    • faraday-cli
    • faraday-agent-dispatcher
    • ocamlPackages.faraday
    • ocamlPackages.faraday-lwt
    • ocamlPackages.faraday-async
    • ocamlPackages_latest.faraday
    • rubyPackages.faraday-net_http
    • ocamlPackages.faraday-lwt-unix
    • ocamlPackages_latest.faraday-lwt
    • python312Packages.faraday-plugins
    • python313Packages.faraday-plugins
    • python314Packages.faraday-plugins
    • rubyPackages_3_1.faraday-net_http
    • rubyPackages_3_2.faraday-net_http
    • ocamlPackages_latest.faraday-async
    • ocamlPackages_latest.faraday-lwt-unix
    • python312Packages.faraday-agent-parameters-types
    • python313Packages.faraday-agent-parameters-types
    • rubyPackages_4_0.faraday-net_http
    • rubyPackages_3_4.faraday-net_http
    • rubyPackages_3_3.faraday-net_http
    • python314Packages.faraday-agent-parameters-types
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Faraday affected by SSRF via protocol-relative URL host override in build_exclusive_url

Faraday is an HTTP client library abstraction layer that provides a common interface over many adapters. Prior to 2.14.1, Faraday's build_exclusive_url method (in lib/faraday/connection.rb) uses Ruby's URI#merge to combine the connection's base URL with a user-supplied path. Per RFC 3986, protocol-relative URLs (e.g. //evil.com/path) are treated as network-path references that override the base URL's host/authority component. This means that if any application passes user-controlled input to Faraday's get(), post(), build_url(), or other request methods, an attacker can supply a protocol-relative URL like //attacker.com/endpoint to redirect the request to an arbitrary host, enabling Server-Side Request Forgery (SSRF). This vulnerability is fixed in 2.14.1.

Affected products

faraday
  • ==< 2.14.1

Matching in nixpkgs

Upstream advisory: https://github.com/lostisland/faraday/security/advisories/GHSA-33mh-2634-fwr2
Upstream patch: https://github.com/lostisland/faraday/commit/a6d3a3a0bf59c2ab307d0abd91bc126aef5561bc
NIXPKGS-2026-0219
published on 11 Feb 2026
updated 3 weeks, 5 days ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed package adminerevo
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Adminer has an Unauthenticated Persistent DoS via Array Injection in ?script=version Endpoint

Adminer is open-source database management software. Adminer v5.4.1 and earlier has a version check mechanism where adminer.org sends signed version info via JavaScript postMessage, which the browser then POSTs to ?script=version. This endpoint lacks origin validation and accepts POST data from any source. An attacker can POST version[] parameter which PHP converts to an array. On next page load, openssl_verify() receives this array instead of string and throws TypeError, returning HTTP 500 to all users. Upgrade to Adminer 5.4.2.

Affected products

adminer
  • ==>= 4.6.2, < 5.4.2

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/vrana/adminer/security/advisories/GHSA-q4f2-39gr-45jh
Upstream patch: https://github.com/vrana/adminer/commit/21d3a3150388677b18647d68aec93b7850e457d3
NIXPKGS-2026-0224
published on 11 Feb 2026
updated 3 weeks, 5 days ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
aardappel lobster Parsing parser.h ParseStatements memory corruption

A vulnerability has been found in aardappel lobster up to 2025.4. Affected by this issue is the function lobster::Parser::ParseStatements in the library dev/src/lobster/parser.h of the component Parsing. The manipulation leads to memory corruption. The attack can only be performed from a local environment. The exploit has been disclosed to the public and may be used. The identifier of the patch is 2f45fe860d00990e79e13250251c1dde633f1f89. Applying a patch is the recommended action to fix this issue.

Affected products

lobster
  • ==2025.1
  • ==2025.0
  • ==2025.3
  • ==2025.4
  • ==2025.2

Matching in nixpkgs

Package maintainers

Upstream patch: https://github.com/aardappel/lobster/commit/2f45fe860d00990e79e13250251c1dde633f1f89
NIXPKGS-2026-0222
published on 11 Feb 2026
updated 3 weeks, 5 days ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
aardappel lobster wfc.h WaveFunctionCollapse memory corruption

A flaw has been found in aardappel lobster up to 2025.4. Affected by this vulnerability is the function WaveFunctionCollapse in the library dev/src/lobster/wfc.h. Executing a manipulation can lead to memory corruption. The attack can only be executed locally. The exploit has been published and may be used. This patch is called c2047a33e1ac2c42ab7e8704b33f7ea518a11ffd. It is advisable to implement a patch to correct this issue.

Affected products

lobster
  • ==2025.1
  • ==2025.0
  • ==2025.3
  • ==2025.4
  • ==2025.2

Matching in nixpkgs

Package maintainers

Upstream patch: https://github.com/aardappel/lobster/commit/c2047a33e1ac2c42ab7e8704b33f7ea518a11ffd
Upstream issue: https://github.com/aardappel/lobster/issues/395
NIXPKGS-2026-0220
published on 11 Feb 2026
updated 3 weeks, 5 days ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    4 packages
    • filebrowser-quantum
    • python312Packages.filebrowser-safe
    • python313Packages.filebrowser-safe
    • python314Packages.filebrowser-safe
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
File Browser has an Authentication Bypass in User Password Update

File Browser provides a file managing interface within a specified directory and it can be used to upload, delete, preview, rename and edit files. Prior to 2.57.1, a case-sensitivity flaw in the password validation logic allows any authenticated user to change their password (or an admin to change any user's password) without providing the current password. By using Title Case field name "Password" instead of lowercase "password" in the API request, the current_password verification is completely bypassed. This enables account takeover if an attacker obtains a valid JWT token through XSS, session hijacking, or other means. This vulnerability is fixed in 2.57.1.

Affected products

filebrowser
  • ==< 2.57.1

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/filebrowser/filebrowser/security/advisories/GHSA-hxw8-4h9j-hq2r
Upstream patch: https://github.com/filebrowser/filebrowser/commit/ff2f00498cff151e2fb1f5f0b16963bf33c3d6d4
NIXPKGS-2026-0218
published on 11 Feb 2026
updated 3 weeks, 5 days ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    13 packages
    • python312Packages.django-cryptography
    • python313Packages.django-cryptography
    • python314Packages.django-cryptography
    • python312Packages.mypy-boto3-payment-cryptography
    • python313Packages.mypy-boto3-payment-cryptography
    • python314Packages.mypy-boto3-payment-cryptography
    • python312Packages.mypy-boto3-payment-cryptography-data
    • python313Packages.mypy-boto3-payment-cryptography-data
    • python314Packages.mypy-boto3-payment-cryptography-data
    • python312Packages.types-aiobotocore-payment-cryptography
    • python313Packages.types-aiobotocore-payment-cryptography
    • python312Packages.types-aiobotocore-payment-cryptography-data
    • python313Packages.types-aiobotocore-payment-cryptography-data
  • @LeSuisse removed
    5 maintainers
    • @SuperSandro2000
    • @centromere
    • @mbalatsko
    • @fabaff
    • @mdaniels5757
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
cryptography Subgroup Attack Due to Missing Subgroup Validation for SECT Curves

cryptography is a package designed to expose cryptographic primitives and recipes to Python developers. Prior to 46.0.5, the public_key_from_numbers (or EllipticCurvePublicNumbers.public_key()), EllipticCurvePublicNumbers.public_key(), load_der_public_key() and load_pem_public_key() functions do not verify that the point belongs to the expected prime-order subgroup of the curve. This missing validation allows an attacker to provide a public key point P from a small-order subgroup. This can lead to security issues in various situations, such as the most commonly used signature verification (ECDSA) and shared key negotiation (ECDH). When the victim computes the shared secret as S = [victim_private_key]P via ECDH, this leaks information about victim_private_key mod (small_subgroup_order). For curves with cofactor > 1, this reveals the least significant bits of the private key. When these weak public keys are used in ECDSA , it's easy to forge signatures on the small subgroup. Only SECT curves are impacted by this. This vulnerability is fixed in 46.0.5.

Affected products

cryptography
  • ==< 46.0.5

Matching in nixpkgs

Package maintainers

Ignored maintainers (2)
Upstream advisory: https://github.com/pyca/cryptography/security/advisories/GHSA-r6ph-v2qm-q3c2
Upstream patch: https://github.com/pyca/cryptography/commit/0eebb9dbb6343d9bc1d91e5a2482ed4e054a6d8c