Nixpkgs security tracker

Login with GitHub

Published issues

All published security issues are tracked and resolved on GitHub.

NIXPKGS-2026-1077
published on
Permalink CVE-2026-40386
4.0 MEDIUM
  • CVSS version: 3.1
  • Attack vector (AV): LOCAL
  • Attack complexity (AC): HIGH
  • Privileges required (PR): NONE
  • User interaction (UI): NONE
  • Scope (S): UNCHANGED
  • Confidentiality impact (C): LOW
  • Integrity impact (I): NONE
  • Availability impact (A): LOW
updated 10 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
In libexif through 0.6.25, an integer underflow in size checking …

In libexif through 0.6.25, an integer underflow in size checking for Fuji and Olympus MakerNote decoding could be used by attackers to crash or leak information out of libexif-using programs.

Affected products

libexif
  • =<0.6.25

Matching in nixpkgs

pkgs.libexif

Library to read and manipulate EXIF data in digital photographs

NIXPKGS-2026-1076
published on
Permalink CVE-2026-40385
4.0 MEDIUM
  • CVSS version: 3.1
  • Attack vector (AV): LOCAL
  • Attack complexity (AC): HIGH
  • Privileges required (PR): NONE
  • User interaction (UI): NONE
  • Scope (S): UNCHANGED
  • Confidentiality impact (C): LOW
  • Integrity impact (I): NONE
  • Availability impact (A): LOW
updated 10 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
In libexif through 0.6.25, an unsigned 32bit integer overflow in …

In libexif through 0.6.25, an unsigned 32bit integer overflow in Nikon MakerNote handling could be used by local attackers to cause crashes or information leaks. This only affects 32bit systems.

Affected products

libexif
  • =<0.6.25

Matching in nixpkgs

pkgs.libexif

Library to read and manipulate EXIF data in digital photographs

No tier 1 or tier 2 support of 32 bits systems.
NIXPKGS-2026-1075
published on
updated 1 day, 5 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse ignored
    2 references
  • @LeSuisse ignored
    6 packages
    • vscode-extensions.gleam.gleam
    • tree-sitter-grammars.tree-sitter-gleam
    • vimPlugins.nvim-treesitter-parsers.gleam
    • python312Packages.tree-sitter-grammars.tree-sitter-gleam
    • python313Packages.tree-sitter-grammars.tree-sitter-gleam
    • python314Packages.tree-sitter-grammars.tree-sitter-gleam
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Improper Path Validation in Git Dependency Handling Allows Arbitrary File System Modification

Improper path validation vulnerability in the Gleam compiler's handling of git dependencies allows arbitrary file system modification during dependency download. Dependency names from gleam.toml and manifest.toml are incorporated into filesystem paths without sufficient validation or confinement to the intended dependency directory, allowing attacker-controlled paths (via relative traversal such as ../ or absolute paths) to target filesystem locations outside that directory. When resolving git dependencies (e.g. via gleam deps download), the computed path is used for filesystem operations including directory deletion and creation. This vulnerability occurs during the dependency resolution and download phase, which is generally expected to be limited to fetching and preparing dependencies within a confined directory. A malicious direct or transitive git dependency can exploit this issue to delete and overwrite arbitrary directories outside the intended dependency directory, including attacker-chosen absolute paths, potentially causing data loss. In some environments, this may be further leveraged to achieve code execution, for example by overwriting git hooks or shell configuration files. This issue affects Gleam from 1.9.0-rc1 until 1.15.3 and 1.16.0-rc1.

Affected products

gleam
  • *
gleam-lang/gleam
  • *

Matching in nixpkgs

Ignored packages (6)

Package maintainers

NIXPKGS-2026-1074
published on
updated 2 days, 12 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse ignored
    2 packages
    • jujutsu
    • jujuutils
  • @LeSuisse ignored reference In-Memory…
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Juju API Server Denial of Service and Authentication Replay via Unsynchronized Token Map

Improper synchronization of the userTokens map in the API server in Canonical Juju 4.0.5, 3.6.20, and 2.9.56 may allow an authenticated user to possibly cause a denial of service on the server or possibly reuse a single-use discharge token.

Affected products

juju
  • <3.6.21
  • <4.0.6
  • <2.9.57

Matching in nixpkgs

pkgs.juju

Open source modelling tool for operating software in the cloud

Ignored packages (2)

pkgs.jujuutils

Utilities around FireWire devices connected to a Linux computer

  • nixos-unstable 0.2
    • nixpkgs-unstable 0.2
    • nixos-unstable-small 0.2
  • nixos-25.11 0.2
    • nixos-25.11-small 0.2
    • nixpkgs-25.11-darwin 0.2

Package maintainers

NIXPKGS-2026-1073
published on
Permalink CVE-2026-40188
7.7 HIGH
  • CVSS version: 3.1
  • Attack vector (AV): NETWORK
  • Attack complexity (AC): LOW
  • Privileges required (PR): LOW
  • User interaction (UI): NONE
  • Scope (S): CHANGED
  • Confidentiality impact (C): NONE
  • Integrity impact (I): HIGH
  • Availability impact (A): NONE
updated 2 days, 12 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
goshs is Missing Write Protection for Parametric Data Values

goshs is a SimpleHTTPServer written in Go. From 1.0.7 to before 2.0.0-beta.4, the SFTP command rename sanitizes only the source path and not the destination, so it is possible to write outside of the root directory of the SFTP. This vulnerability is fixed in 2.0.0-beta.4.

Affected products

goshs
  • ==>= 1.0.7, < 2.0.0-beta.4

Matching in nixpkgs

Package maintainers

NIXPKGS-2026-1072
published on
Permalink CVE-2026-6067
7.5 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): NONE
  • Integrity impact (I): NONE
  • Availability impact (A): HIGH
updated 2 days, 12 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse ignored
    5 packages
    • nasmfmt
    • tree-sitter-grammars.tree-sitter-nasm
    • vimPlugins.nvim-treesitter-parsers.nasm
    • python314Packages.tree-sitter-grammars.tree-sitter-nasm
    • python313Packages.tree-sitter-grammars.tree-sitter-nasm
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
CVE-2026-6067

A heap buffer overflow vulnerability exists in the Netwide Assembler (NASM) due to a lack of bounds checking in the obj_directive() function. This vulnerability can be exploited by a user assembling a malicious .asm file, potentially leading to heap memory corruption, denial of service (crash), and arbitrary code execution.

Affected products

NASM
  • ==nasm-3.02rc5

Matching in nixpkgs

pkgs.nasm

80x86 and x86-64 assembler designed for portability and modularity

Ignored packages (5)

Package maintainers

NIXPKGS-2026-1071
published on
updated 2 days, 12 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Prefix-substitution forgery via integer overflow in wolfCrypt CMAC

An integer overflow existed in the wolfCrypt CMAC implementation, that could be exploited to forge CMAC tags. The function wc_CmacUpdate used the guard `if (cmac->totalSz != 0)` to skip XOR-chaining on the first block (where digest is all-zeros and the XOR is a no-op). However, totalSz is word32 and wraps to zero after 2^28 block flushes (4 GiB), causing the guard to erroneously discard the live CBC-MAC chain state. Any two messages sharing a common suffix beyond the 4 GiB mark then produce identical CMAC tags, enabling a zero-work prefix-substitution forgery. The fix removes the guard, making the XOR unconditional; the no-op property on the first block is preserved because digest is zero-initialized by wc_InitCmac_ex.

Affected products

wolfSSL
  • =<5.9.0

Matching in nixpkgs

pkgs.wolfssl

Small, fast, portable implementation of TLS/SSL for embedded devices

Package maintainers

NIXPKGS-2026-1070
published on
updated 2 days, 12 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse ignored
    19 packages
    • temporal-cli
    • temporal_capi
    • temporal-ui-server
    • haskellPackages.temporal-music-notation-western
    • terraform-providers.temporalio_temporalcloud
    • haskellPackages.temporal-music-notation-demo
    • haskellPackages.temporal-music-notation
    • postgresql18Packages.temporal_tables
    • postgresql17Packages.temporal_tables
    • postgresql16Packages.temporal_tables
    • postgresql15Packages.temporal_tables
    • postgresql14Packages.temporal_tables
    • haskellPackages.temporal-api-protos
    • postgresqlPackages.temporal_tables
    • terraform-providers.temporalcloud
    • haskellPackages.temporal-media
    • python314Packages.temporalio
    • python313Packages.temporalio
    • python312Packages.temporalio
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Missing Authentication on Streaming gRPC Replication Endpoint

The frontend gRPC server's streaming interceptor chain did not include the authorization interceptor. When a ClaimMapper and Authorizer are configured, unary RPCs enforce authentication and authorization, but the streaming AdminService/StreamWorkflowReplicationMessages endpoint accepted requests without credentials. This endpoint is registered on the same port as WorkflowService and cannot be disabled independently. An attacker with network access to the frontend port could open the replication stream without authentication. Data exfiltration is possible, but  only when a configured replication target is correctly configured and the attacker has knowledge of the cluster configuration, as the history service validates cluster IDs and peer membership before returning replication data. Temporal Cloud is not affected.

Affected products

temporal
  • =<1.30.3
  • =<1.29.5
  • =<1.28.3

Matching in nixpkgs

pkgs.temporal

Microservice orchestration platform which enables developers to build scalable applications without sacrificing productivity or reliability

Ignored packages (19)

pkgs.temporal-cli

Command-line interface for running Temporal Server and interacting with Workflows, Activities, Namespaces, and other parts of Temporal

Package maintainers

NIXPKGS-2026-1069
published on
updated 2 days, 12 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
wolfSSL EVP ChaCha20-Poly1305 AEAD authentication tag

In wolfSSL's EVP layer, the ChaCha20-Poly1305 AEAD decryption path in wolfSSL_EVP_CipherFinal (and related EVP cipher finalization functions) fails to verify the authentication tag before returning plaintext to the caller. When an application uses the EVP API to perform ChaCha20-Poly1305 decryption, the implementation computes or accepts the tag but does not compare it against the expected value.

Affected products

wolfSSL
  • <5.9.1

Matching in nixpkgs

pkgs.wolfssl

Small, fast, portable implementation of TLS/SSL for embedded devices

Package maintainers

NIXPKGS-2026-1068
published on
Permalink CVE-2026-40103
4.3 MEDIUM
  • 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): LOW
  • Availability impact (A): NONE
updated 2 days, 12 hours ago by @LeSuisse Activity log
Vikunja's Scoped API tokens with projects.background permission can delete project backgrounds

Vikunja is an open-source self-hosted task management platform. Prior to 2.3.0, Vikunja's scoped API token enforcement for custom project background routes is method-confused. A token with only projects.background can successfully delete a project background, while a token with only projects.background_delete is rejected. This is a scoped-token authorization bypass. This vulnerability is fixed in 2.3.0.

Affected products

vikunja
  • ==< 2.3.0

Matching in nixpkgs

pkgs.vikunja

Todo-app to organize your life

Ignored packages (1)

Package maintainers