Nixpkgs Security Tracker

Login with GitHub

Published issues

All published security issues are tracked and resolved on GitHub.

NIXPKGS-2026-0089
published on 27 Jan 2026
updated 1 month, 1 week ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed package unixtools.ping
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
ping in iputils through 20240905 allows a denial of service …

ping in iputils through 20240905 allows a denial of service (application error or incorrect data collection) via a crafted ICMP Echo Reply packet, because of a signed 64-bit integer overflow in timestamp multiplication.

Affected products

iputils
  • =<20240905
  • <20250602

Matching in nixpkgs

Package maintainers

Upstream patch/advisory: https://github.com/iputils/iputils/commit/070cfacd7348386173231fb16fad4983d4e6ae40
Release notes: https://github.com/iputils/iputils/releases/tag/20250602
NIXPKGS-2026-0090
published on 27 Jan 2026
updated 1 month, 1 week ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Shaarli vulnerable to stored XSS via Suggested Tags

Shaarli is a personal bookmarking service. Prior to version 0.16.0, crafting a malicious tag which starting with `"` prematurely ends the `<input>` tag on the start page and allows an attacker to add arbitrary html leading to a possible XSS attack. Version 0.16.0 fixes the issue.

Affected products

Shaarli
  • ==< 0.16.0

Matching in nixpkgs

pkgs.shaarli

Personal, minimalist, super-fast, database free, bookmarking service

Package maintainers

Upstream advisory: https://github.com/shaarli/Shaarli/security/advisories/GHSA-g3xq-mj52-f8pg
Upstream patch: https://github.com/shaarli/Shaarli/commit/b854c789289c4b0dfbb7c1e5793bae7d8f94e063
NIXPKGS-2026-0088
published on 26 Jan 2026
updated 1 month, 1 week ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed package moodle-dl
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Moodle: moodle: remote code execution via insufficient restore input validation

A flaw was found in Moodle. An attacker with access to the restore interface could trigger server-side execution of arbitrary code. This is due to insufficient validation of restore input, which leads to unintended interpretation by core restore routines. Successful exploitation could result in a full compromise of the Moodle application.

Affected products

moodle
  • <5.1.1
  • <5.0.4
  • <4.5.8
  • <4.1.0
  • <4.1.22
  • <4.4.12

Matching in nixpkgs

pkgs.moodle

Free and open-source learning management system (LMS) written in PHP

Package maintainers

Upstream advisory: https://moodle.org/mod/forum/discuss.php?d=471297#p1892199
Upstream patch: https://github.com/moodle/moodle/commit/1e7ff52667b88025ac919dbd84ee6a81dcc3166b
NIXPKGS-2026-0083
published on 23 Jan 2026
updated 1 month, 1 week ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    4 packages
    • fleetctl
    • fleeting-plugin-aws
    • python313Packages.types-aiobotocore-iotfleetwise
    • python312Packages.types-aiobotocore-iotfleetwise
  • @LeSuisse removed
    3 maintainers
    • @katexochen
    • @ulrikstrid
    • @asauzeau
  • @LeSuisse added maintainer @commiterate
  • @LeSuisse removed
    4 maintainers
    • @dotlambda
    • @fabaff
    • @mweinelt
    • @mbalatsko
  • @LeSuisse removed
    12 packages
    • python313Packages.types-aiobotocore-iotfleethub
    • python312Packages.types-aiobotocore-iotfleethub
    • home-assistant-component-tests.tesla_fleet
    • python313Packages.mypy-boto3-iotfleetwise
    • python312Packages.mypy-boto3-iotfleetwise
    • python313Packages.mypy-boto3-iotfleethub
    • python312Packages.mypy-boto3-iotfleethub
    • haskellPackages.amazonka-iotfleetwise
    • haskellPackages.amazonka-iotfleethub
    • python313Packages.tesla-fleet-api
    • python312Packages.tesla-fleet-api
    • azure-cli-extensions.fleet
  • @LeSuisse removed maintainer @commiterate
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Fleet has an Access Control vulnerability in debug/pprof endpoints

Fleet is open source device management software. A broken access control issue in versions prior to 4.78.3, 4.77.1, 4.76.2, 4.75.2, and 4.53.3 allowed authenticated users to access debug and profiling endpoints regardless of role. As a result, low-privilege users could view internal server diagnostics and trigger resource-intensive profiling operations. Fleet’s debug/pprof endpoints are accessible to any authenticated user regardless of role, including the lowest-privilege “Observer” role. This allows low-privilege users to access sensitive server internals, including runtime profiling data and in-memory application state, and to trigger CPU-intensive profiling operations that could lead to denial of service. Versions 4.78.3, 4.77.1, 4.76.2, 4.75.2, and 4.53.3 fix the issue. If an immediate upgrade is not possible, users should put the debug/pprof endpoints behind an IP allowlist as a workaround.

Affected products

fleet
  • ==>= 4.78.0, < 4.78.3
  • ==>= 4.76.0, < 4.76.2
  • ==>= 4.77.0, < 4.77.1
  • ==< 4.53.3
  • ==>= 4.75.0, < 4.75.2

Matching in nixpkgs

Package maintainers

Ignored maintainers (1)
Upstream advisory: https://github.com/fleetdm/fleet/security/advisories/GHSA-4r5r-ccr6-q6f6
NIXPKGS-2026-0080
published on 23 Jan 2026
updated 1 month, 1 week 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-0079
published on 23 Jan 2026
updated 1 month, 1 week 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-0078
published on 23 Jan 2026
updated 1 month, 1 week 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-0085
published on 23 Jan 2026
updated 1 month, 1 week 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 1 month, 1 week 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 1 month, 1 week 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