Nixpkgs Security Tracker

Login with GitHub

Published issues

All published security issues are tracked and resolved on GitHub.

NIXPKGS-2026-0153
published on 7 Feb 2026
updated 1 month ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    5 packages
    • asterisk-ldap
    • asterisk-module-sccp
    • python312Packages.asterisk-mbox
    • python313Packages.asterisk-mbox
    • python314Packages.asterisk-mbox
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Asterisk xml.c uses unsafe XML_PARSE_NOENT leading to potential XXE Injection

Asterisk is an open source private branch exchange and telephony toolkit. Prior to versions 20.7-cert9, 20.18.2, 21.12.1, 22.8.2, and 23.2.2, the ast_xml_open() function in xml.c parses XML documents using libxml with unsafe parsing options that enable entity expansion and XInclude processing. Specifically, it invokes xmlReadFile() with the XML_PARSE_NOENT flag and later processes XIncludes via xmlXIncludeProcess().If any untrusted or user-supplied XML file is passed to this function, it can allow an attacker to trigger XML External Entity (XXE) or XInclude-based local file disclosure, potentially exposing sensitive files from the host system. This can also be triggered in other cases in which the user is able to supply input in xml format that triggers the asterisk process to parse it. This issue has been patched in versions 20.7-cert9, 20.18.2, 21.12.1, 22.8.2, and 23.2.2.

Affected products

asterisk
  • ==< 23.2.2
  • ==< 21.12.1
  • ==< 20.7-cert9
  • ==< 20.18.2
  • ==< 22.8.2

Matching in nixpkgs

pkgs.asterisk_18

Software implementation of a telephone private branch exchange (PBX)

Package maintainers

Upstream advisory: https://github.com/asterisk/asterisk/security/advisories/GHSA-85x7-54wr-vh42
NIXPKGS-2026-0145
published on 7 Feb 2026
updated 1 month ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    6 packages
    • claude-code-acp
    • claude-code-bin
    • claude-code-router
    • gnomeExtensions.claude-code-switcher
    • vscode-extensions.anthropic.claude-code
    • gnomeExtensions.claude-code-usage-indicator
  • @LeSuisse removed
    8 maintainers
    • @omarjatoi
    • @malob
    • @markus1189
    • @storopoli
    • @xiaoxiangmoe
    • @mirkolenz
    • @Prince213
    • @honnip
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Claude Code Has Permission Deny Bypass Through Symbolic Links

Claude Code is an agentic coding tool. Prior to version 2.1.7, Claude Code failed to strictly enforce deny rules configured in settings.json when accessing files through symbolic links. If a user explicitly denied Claude Code access to a file (such as /etc/passwd) and Claude Code had access to a symbolic link pointing to that file, it was possible for Claude Code to read the restricted file through the symlink without triggering deny rule enforcement. This issue has been patched in version 2.1.7.

Affected products

claude-code
  • ==< 2.1.7

Matching in nixpkgs

Package maintainers

Ignored maintainers (3)
Upstream advisory: https://github.com/anthropics/claude-code/security/advisories/GHSA-4q92-rfm6-2cqx
NIXPKGS-2026-0147
published on 7 Feb 2026
updated 1 month ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    4 packages
    • openfga-cli
    • python312Packages.openfga-sdk
    • python313Packages.openfga-sdk
    • python314Packages.openfga-sdk
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
OpenFGA Improper Policy Enforcement

OpenFGA is a high-performance and flexible authorization/permission engine built for developers and inspired by Google Zanzibar. OpenFGA v1.8.5 to v1.11.2 ( openfga-0.2.22<= Helm chart <= openfga-0.2.51, v.1.8.5 <= docker <= v.1.11.2) are vulnerable to improper policy enforcement when certain Check calls are executed. The vulnerability requires a model that has a a relation directly assignable by a type bound public access and assignable by type bound non-public access, a tuple assigned for the relation that is a type bound public access, a tuple assigned for the same object with the same relation that is not type bound public access, and a tuple assigned for a different object that has an object ID lexicographically larger with the same user and relation which is not type bound public access. This vulnerability is fixed in v1.11.3.

Affected products

openfga
  • ==< 1.11.3

Matching in nixpkgs

pkgs.openfga

High performance and flexible authorization/permission engine built for developers and inspired by Google Zanzibar

Package maintainers

Upstream advisory: https://github.com/openfga/openfga/security/advisories/GHSA-jq9f-gm9w-rwm9
NIXPKGS-2026-0149
published on 7 Feb 2026
updated 1 month ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    5 packages
    • asterisk-ldap
    • asterisk-module-sccp
    • python312Packages.asterisk-mbox
    • python313Packages.asterisk-mbox
    • python314Packages.asterisk-mbox
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
The Asterisk embedded web server 's /httpstatus page echos user supplied values(cookie and query string) without sanitization

Asterisk is an open source private branch exchange and telephony toolkit. Prior to versions 20.7-cert9, 20.18.2, 21.12.1, 22.8.2, and 23.2.2, user supplied/control values for Cookies and any GET variable query Parameter are directly interpolated into the HTML of the page using ast_str_append. The endpoint at GET /httpstatus is the potential vulnerable endpoint relating to asterisk/main /http.c. This issue has been patched in versions 20.7-cert9, 20.18.2, 21.12.1, 22.8.2, and 23.2.2.

Affected products

asterisk
  • ==< 23.2.2
  • ==< 21.12.1
  • ==< 20.7-cert9
  • ==< 20.18.2
  • ==< 22.8.2

Matching in nixpkgs

pkgs.asterisk_18

Software implementation of a telephone private branch exchange (PBX)

Package maintainers

Upstream advisory: https://github.com/asterisk/asterisk/security/advisories/GHSA-v6hp-wh3r-cwxh
NIXPKGS-2026-0137
published on 7 Feb 2026
updated 1 month ago by @jopejoe1 Activity log
  • Created automatic suggestion
  • @jopejoe1 removed
    2 packages
    • rizinPlugins.sigdb
    • cutterPlugins.sigdb
  • @jopejoe1 accepted
  • @jopejoe1 removed maintainer @chayleaf
  • @jopejoe1 published on GitHub
Rizin has a heap overflow on mach0_chained_fixups.c

Rizin is a UNIX-like reverse engineering framework and command-line toolset. Prior to 0.8.2, a heap overflow can be exploited when a malicious mach0 file, having bogus entries for the dyld chained segments, is parsed by rizin. This vulnerability is fixed in 0.8.2.

Affected products

rizin
  • ==< 0.8.2

Matching in nixpkgs

pkgs.rizin

UNIX-like reverse engineering framework and command-line toolset

Package maintainers

Upstream fix: https://github.com/rizinorg/rizin/releases/tag/v0.8.2
Upstream advisory: https://github.com/rizinorg/rizin/security/advisories/GHSA-f3v7-xhmj-9cjj
Unstable fix: https://github.com/NixOS/nixpkgs/pull/486103
NIXPKGS-2026-0165
published on 7 Feb 2026
updated 1 month ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Suricata DCERPC: unbounded fragment buffering leads to memory exhaustion

Suricata is a network IDS, IPS and NSM engine. Prior to versions 8.0.3 and 7.0.14, crafted DCERPC traffic can cause Suricata to expand a buffer w/o limits, leading to memory exhaustion and the process getting killed. While reported for DCERPC over UDP, it is believed that DCERPC over TCP and SMB are also vulnerable. DCERPC/TCP in the default configuration should not be vulnerable as the default stream depth is limited to 1MiB. Versions 8.0.3 and 7.0.14 contain a patch. Some workarounds are available. For DCERPC/UDP, disable the parser. For DCERPC/TCP, the `stream.reassembly.depth` setting will limit the amount of data that can be buffered. For DCERPC/SMB, the `stream.reassembly.depth` can be used as well, but is set to unlimited by default. Imposing a limit here may lead to loss of visibility in SMB.

Affected products

suricata
  • ==< 7.0.14
  • ==>= 8.0.0, < 8.0.3

Matching in nixpkgs

pkgs.suricata

Free and open source, mature, fast and robust network threat detection engine

Package maintainers

Upstream advisory: https://github.com/OISF/suricata/security/advisories/GHSA-289c-h599-3xcx
NIXPKGS-2026-0163
published on 7 Feb 2026
updated 1 month ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
mruby JMPNOT-to-JMPIF Optimization vm.c mrb_vm_exec use after free

A flaw has been found in mruby up to 3.4.0. This affects the function mrb_vm_exec of the file src/vm.c of the component JMPNOT-to-JMPIF Optimization. Executing a manipulation can lead to use after free. The attack needs to be launched locally. The exploit has been published and may be used. This patch is called e50f15c1c6e131fa7934355eb02b8173b13df415. It is advisable to implement a patch to correct this issue.

Affected products

mruby
  • ==3.4.0
  • ==3.0
  • ==3.1
  • ==3.3
  • ==3.2

Matching in nixpkgs

Package maintainers

Upstream issue: https://github.com/mruby/mruby/issues/6701
Upstream fix: https://github.com/mruby/mruby/commit/e50f15c1c6e131fa7934355eb02b8173b13df415
NIXPKGS-2026-0157
published on 7 Feb 2026
updated 1 month ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed package open5gs-webui
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Open5GS PGW S5U Address sgwc_sxa_handle_session_modification_response null pointer dereference

A vulnerability was identified in Open5GS up to 2.7.6. This affects the function sgwc_s5c_handle_modify_bearer_response/sgwc_sxa_handle_session_modification_response of the component PGW S5U Address Handler. The manipulation leads to null pointer dereference. The attack can be initiated remotely. The exploit is publicly available and might be used. The identifier of the patch is f1bbd7b57f831e2a070780a7d8d5d4c73babdb59. Applying a patch is the recommended action to fix 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/f1bbd7b57f831e2a070780a7d8d5d4c73babdb59
NIXPKGS-2026-0161
published on 7 Feb 2026
updated 1 month ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    3 packages
    • python312Packages.nicegui-highcharts
    • python313Packages.nicegui-highcharts
    • python314Packages.nicegui-highcharts
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
NiceGUI's Path Traversal via Unsanitized FileUpload.name Enables Arbitrary File Write

NiceGUI is a Python-based UI framework. Prior to 3.7.0, NiceGUI's FileUpload.name property exposes client-supplied filename metadata without sanitization, enabling path traversal when developers use the pattern UPLOAD_DIR / file.name. Malicious filenames containing ../ sequences allow attackers to write files outside intended directories, with potential for remote code execution through application file overwrites in vulnerable deployment patterns. This design creates a prevalent security footgun affecting applications following common community patterns. Note: Exploitation requires application code incorporating file.name into filesystem paths without sanitization. Applications using fixed paths, generated filenames, or explicit sanitization are not affected. This vulnerability is fixed in 3.7.0.

Affected products

nicegui
  • ==< 3.7.0

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/zauberzeug/nicegui/security/advisories/GHSA-9ffm-fxg3-xrhh
NIXPKGS-2026-0159
published on 7 Feb 2026
updated 1 month ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    7 packages
    • qdrant-web-ui
    • python312Packages.qdrant-client
    • python313Packages.qdrant-client
    • python314Packages.qdrant-client
    • python312Packages.llama-index-vector-stores-qdrant
    • python313Packages.llama-index-vector-stores-qdrant
    • pkgsRocm.python3Packages.llama-index-vector-stores-qdrant
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Qdrant affected by arbitrary file write via `/logger` endpoint

Qdrant is a vector similarity search engine and vector database. From 1.9.3 to before 1.16.0, it is possible to append to arbitrary files via /logger endpoint using an attacker-controlled on_disk.log_file path. Minimal privileges are required (read-only access). This vulnerability is fixed in 1.16.0.

Affected products

qdrant
  • ==>= 1.9.3, < 1.16.0

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/qdrant/qdrant/security/advisories/GHSA-f632-vm87-2m2f
Upstream patch: https://github.com/qdrant/qdrant/commit/32b7fdfb7f542624ecd1f7c8d3e2b13c4e36a2c1