Nixpkgs Security Tracker

Login with GitHub

Published issues

All published security issues are tracked and resolved on GitHub.

NIXPKGS-2026-0080
published on 23 Jan 2026
updated 4 weeks, 1 day ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    2 packages
    • python313Packages.sigstore-rekor-types
    • python312Packages.sigstore-rekor-types
  • @LeSuisse removed
    2 maintainers
    • @developer-guy
    • @06kellyjac
  • @LeSuisse added
    2 maintainers
    • @fabaff
    • @Bot-wxt1221
  • @LeSuisse removed
    2 maintainers
    • @fabaff
    • @Bot-wxt1221
  • @LeSuisse removed package rekor-cli
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Rekor COSE v0.0.1 Canonicalize crashes when passed empty Message

Rekor is a software supply chain transparency log. In versions 1.4.3 and below, the entry implementation can panic on attacker-controlled input when canonicalizing a proposed entry with an empty spec.message, causing nil Pointer Dereference. Function validate() returns nil (success) when message is empty, leaving sign1Msg uninitialized, and Canonicalize() later dereferences v.sign1Msg.Payload. A malformed proposed entry of the cose/v0.0.1 type can cause a panic on a thread within the Rekor process. The thread is recovered so the client receives a 500 error message and service still continues, so the availability impact of this is minimal. This issue has been fixed in version 1.5.0.

Affected products

rekor
  • ==< 1.5.0

Matching in nixpkgs

Package maintainers

Ignored maintainers (2)
https://github.com/sigstore/rekor/security/advisories/GHSA-273p-m2cw-6833
NIXPKGS-2026-0078
published on 23 Jan 2026
updated 4 weeks, 1 day ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    4 packages
    • pkgsRocm.vllm
    • python312Packages.vllm
    • python313Packages.vllm
    • pkgsRocm.python3Packages.vllm
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
vLLM affected by RCE via auto_map dynamic module loading during model initialization

vLLM is an inference and serving engine for large language models (LLMs). Starting in version 0.10.1 and prior to version 0.14.0, vLLM loads Hugging Face `auto_map` dynamic modules during model resolution without gating on `trust_remote_code`, allowing attacker-controlled Python code in a model repo/path to execute at server startup. An attacker who can influence the model repo/path (local directory or remote Hugging Face repo) can achieve arbitrary code execution on the vLLM host during model load. This happens before any request handling and does not require API access. Version 0.14.0 fixes the issue.

Affected products

vllm
  • ==>= 0.10.1, < 0.14.0

Matching in nixpkgs

pkgs.vllm

High-throughput and memory-efficient inference and serving engine for LLMs

Package maintainers

Upstream advisory: https://github.com/vllm-project/vllm/security/advisories/GHSA-2pc9-4j83-qjmr
Upstream fix: https://github.com/vllm-project/vllm/commit/78d13ea9de4b1ce5e4d8a5af9738fea71fb024e5
NIXPKGS-2026-0079
published on 23 Jan 2026
updated 4 weeks, 1 day ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
WordPress Merge + Minify + Refresh plugin <= 2.14 - Cross Site Request Forgery (CSRF) vulnerability

Cross-Site Request Forgery (CSRF) vulnerability in launchinteractive Merge + Minify + Refresh merge-minify-refresh allows Cross Site Request Forgery.This issue affects Merge + Minify + Refresh: from n/a through <= 2.14.

Affected products

merge-minify-refresh
  • =<<= 2.14

Matching in nixpkgs

Needs to be upgraded to 2.15: https://wordpress.org/plugins/merge-minify-refresh/#developers

Upstream fix: https://github.com/Launch-Interactive/Merge-Minify-Refresh/commit/653e114c01940c43c50418ae1489ad2ce23cbe04
NIXPKGS-2026-0085
published on 23 Jan 2026
updated 4 weeks, 1 day ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    15 packages
    • fleeting-plugin-aws
    • azure-cli-extensions.fleet
    • python312Packages.tesla-fleet-api
    • python313Packages.tesla-fleet-api
    • haskellPackages.amazonka-iotfleethub
    • haskellPackages.amazonka-iotfleetwise
    • python312Packages.mypy-boto3-iotfleethub
    • python313Packages.mypy-boto3-iotfleethub
    • python312Packages.mypy-boto3-iotfleetwise
    • python313Packages.mypy-boto3-iotfleetwise
    • home-assistant-component-tests.tesla_fleet
    • python312Packages.types-aiobotocore-iotfleethub
    • python313Packages.types-aiobotocore-iotfleethub
    • python312Packages.types-aiobotocore-iotfleetwise
    • python313Packages.types-aiobotocore-iotfleetwise
  • @LeSuisse removed maintainer @asauzeau
  • @LeSuisse added
    6 maintainers
    • @commiterate
    • @dotlambda
    • @fabaff
    • @mweinelt
    • @mbalatsko
    • @katexochen
  • @LeSuisse removed package fleetctl
  • @LeSuisse added maintainer @ulrikstrid
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Fleet Windows MDM endpoint has a Cross-site Scripting vulnerability

fleetdm/fleet is open source device management software. Prior to versions 4.78.2, 4.77.1, 4.76.2, 4.75.2, and 4.53.3, if Windows MDM is enabled, an unauthenticated attacker can exploit this XSS vulnerability to steal a Fleet administrator's authentication token (FLEET::auth_token) from localStorage. This could allow unauthorized access to Fleet, including administrative access, visibility into device data, and modification of configuration. Versions 4.78.2, 4.77.1, 4.76.2, 4.75.2, and 4.53.3 fix the issue. If an immediate upgrade is not possible, affected Fleet users should temporarily disable Windows MDM.

Affected products

fleet
  • ==>= 4.78.0, < 4.78.2
  • ==>= 4.76.0, < 4.76.2
  • ==>= 4.77.0, < 4.77.1
  • ==< 4.53.3

Matching in nixpkgs

Package maintainers

Ignored maintainers (1)

Additional maintainers

Upstream advisory: https://github.com/fleetdm/fleet/security/advisories/GHSA-gfpw-jgvr-cw4j
NIXPKGS-2026-0081
published on 23 Jan 2026
updated 4 weeks, 1 day ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    3 packages
    • rekor-cli
    • python312Packages.sigstore-rekor-types
    • python313Packages.sigstore-rekor-types
  • @LeSuisse removed
    2 maintainers
    • @developer-guy
    • @06kellyjac
  • @LeSuisse added
    2 maintainers
    • @fabaff
    • @Bot-wxt1221
  • @LeSuisse removed
    3 maintainers
    • @LeSuisse
    • @Bot-wxt1221
    • @fabaff
  • @LeSuisse added maintainer @LeSuisse
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Rekor affected by Server-Side Request Forgery (SSRF) via provided public key URL

Rekor is a software supply chain transparency log. In versions 1.4.3 and below, attackers can trigger SSRF to arbitrary internal services because /api/v1/index/retrieve supports retrieving a public key via user-provided URL. Since the SSRF only can trigger GET requests, the request cannot mutate state. The response from the GET request is not returned to the caller so data exfiltration is not possible. A malicious actor could attempt to probe an internal network through Blind SSRF. The issue has been fixed in version 1.5.0. To workaround this issue, disable the search endpoint with --enable_retrieve_api=false.

Affected products

rekor
  • ==< 1.5.0

Matching in nixpkgs

Package maintainers

Ignored maintainers (2)
https://github.com/sigstore/rekor/security/advisories/GHSA-4c4x-jm2x-pf9j
NIXPKGS-2026-0086
published on 23 Jan 2026
updated 4 weeks, 1 day ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @mweinelt accepted
  • @LeSuisse removed maintainer @peterhoeg
  • @LeSuisse published on GitHub
FreeRDP has heap-buffer-overflow in planar_decompress_plane_rle

FreeRDP is a free implementation of the Remote Desktop Protocol. Prior to version 3.21.0,`freerdp_bitmap_decompress_planar` does not validate `nSrcWidth`/`nSrcHeight` against `planar->maxWidth`/`maxHeight` before RLE decode. A malicious server can trigger a client‑side heap buffer overflow, causing a crash (DoS) and potential heap corruption with code‑execution risk depending on allocator behavior and surrounding heap layout. Version 3.21.0 contains a patch for the issue.

Affected products

FreeRDP
  • ==< 3.21.0

Matching in nixpkgs

Package maintainers

Ignored maintainers (1)
Fixed in https://github.com/NixOS/nixpkgs/pull/481912 and https://github.com/NixOS/nixpkgs/pull/481941
NIXPKGS-2026-0067
published on 21 Jan 2026
updated 1 month ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed package open5gs-webui
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Open5GS GTPv2 Bearer Response denial of service

A vulnerability has been found in Open5GS up to 2.7.6. Affected by this vulnerability is an unknown functionality of the component GTPv2 Bearer Response Handler. Such manipulation leads to denial of service. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. The name of the patch is 98f76e98df35cd6a35e868aa62715db7f8141ac1. A patch should be applied to remediate this issue.

Affected products

Open5GS
  • ==2.7.3
  • ==2.7.5
  • ==2.7.0
  • ==2.7.4
  • ==2.7.1
  • ==2.7.6
  • ==2.7.2

Matching in nixpkgs

Package maintainers

Upstream patch: https://github.com/open5gs/open5gs/commit/98f76e98df35cd6a35e868aa62715db7f8141ac1
NIXPKGS-2026-0077
published on 21 Jan 2026
updated 1 month ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    3 packages
    • vscode-extensions.ms-toolsai.datawrangler
    • python312Packages.awswrangler
    • python313Packages.awswrangler
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
OS Command Injection in `wrangler pages deploy`

SummaryA command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. Root causeThe commitHash variable, derived from user input via the --commit-hash CLI argument, is interpolated directly into a shell command using template literals (e.g.,  execSync(`git show -s --format=%B ${commitHash}`)). Shell metacharacters are interpreted by the shell, enabling command execution. ImpactThis vulnerability is generally hard to exploit, as it requires --commit-hash to be attacker controlled. The vulnerability primarily affects CI/CD environments where `wrangler pages deploy` is used in automated pipelines and the --commit-hash parameter is populated from external, potentially untrusted sources. An attacker could exploit this to: * Run any shell command. * Exfiltrate environment variables. * Compromise the CI runner to install backdoors or modify build artifacts. Credits Disclosed responsibly by kny4hacker. Mitigation * Wrangler v4 users are requested to upgrade to Wrangler v4.59.1 or higher. * Wrangler v3 users are requested to upgrade to Wrangler v3.114.17 or higher. * Users on Wrangler v2 (EOL) should upgrade to a supported major version.

Affected products

Wrangler
  • =<v4.59.0
  • =<v3.114.16
  • ==v2.0.15+

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/cloudflare/workers-sdk/security/advisories/GHSA-36p8-mvp6-cv38
NIXPKGS-2026-0076
published on 21 Jan 2026
updated 1 month ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    4 packages
    • terraform-providers.keycloak
    • python312Packages.python-keycloak
    • python313Packages.python-keycloak
    • terraform-providers.keycloak_keycloak
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Keycloak: org.keycloak:keycloak-services: user can refresh offline session even after client's offline_access scope was removed

A flaw was found in Keycloak. An offline session continues to be valid when the offline_access scope is removed from the client. The refresh token is accepted and you can continue to request new tokens for the session. As it can lead to a situation where an administrator removes the scope, and assumes that offline sessions are no longer available, but they are.

Affected products

keycloak
  • <26.4.3
keycloak-server
rhbk/keycloak-rhel9
  • *
rhbk/keycloak-rhel9-operator
  • *
rhbk/keycloak-operator-bundle
  • *
Red Hat build of Keycloak 26.2.11

Matching in nixpkgs

Package maintainers

Upstream fix: https://github.com/keycloak/keycloak/commit/e0c1f2ee0fd14ba76338d9c2c213d45d0e857450
NIXPKGS-2026-0075
published on 21 Jan 2026
updated 1 month ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed package libcdio-paranoia
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Buffer Overflow Vulnerability in libcdio v2.1.0 allows an attacker to …

Buffer Overflow Vulnerability in libcdio v2.1.0 allows an attacker to execute arbitrary code via a crafted ISO 9660 image file.

Affected products

n/a
  • ==n/a
libcdio
  • ==2.1.0

Matching in nixpkgs

Upstream fix: https://github.com/libcdio/libcdio/commit/417478a7474af41c27ab3f876f31783fa06a5dbc
Fixed in 2.3.0: https://github.com/libcdio/libcdio/releases/tag/2.3.0