Nixpkgs Security Tracker

Login with GitHub

Published issues

All published security issues are tracked and resolved on GitHub.

NIXPKGS-2026-0084
published on 23 Jan 2026
updated 1 month, 1 week ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    16 packages
    • fleetctl
    • 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 @ulrikstrid
  • @LeSuisse added maintainer @katexochen
  • @LeSuisse removed maintainer @asauzeau
  • @LeSuisse added
    5 maintainers
    • @commiterate
    • @dotlambda
    • @fabaff
    • @mweinelt
    • @mbalatsko
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Fleet has a JWT signature bypass vulnerability in Azure AD MDM enrollment

Fleet is open source device management software. In versions prior to 4.78.3, 4.77.1, 4.76.2, 4.75.2, and 4.53.3, a vulnerability in Fleet's Windows MDM enrollment flow could allow an attacker to submit forged authentication tokens that are not properly validated. Because JWT signatures were not verified, Fleet could accept attacker-controlled identity claims, enabling enrollment of unauthorized devices under arbitrary Azure AD user identities. 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, affected Fleet users should temporarily disable Windows MDM.

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)

Additional maintainers

Upstream advisory: https://github.com/fleetdm/fleet/security/advisories/GHSA-63m5-974w-448v
NIXPKGS-2026-0082
published on 23 Jan 2026
updated 1 month, 1 week ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
telnetd in GNU Inetutils through 2.7 allows remote authentication bypass …

telnetd in GNU Inetutils through 2.7 allows remote authentication bypass via a "-f root" value for the USER environment variable.

References

Affected products

Inetutils
  • =<2.7

Matching in nixpkgs

Package maintainers

Upstream advisory: https://lists.gnu.org/archive/html/bug-inetutils/2026-01/msg00004.html
NIXPKGS-2026-0067
published on 21 Jan 2026
updated 1 month, 2 weeks 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, 2 weeks 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, 2 weeks 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.

References

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, 2 weeks 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
NIXPKGS-2026-0064
published on 21 Jan 2026
updated 1 month, 2 weeks ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    4 packages
    • python312Packages.quickjs
    • python313Packages.quickjs
    • python312Packages.llm-tools-quickjs
    • python313Packages.llm-tools-quickjs
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
quickjs-ng quickjs Atomics Ops quickjs.c use after free

A vulnerability was detected in quickjs-ng quickjs up to 0.11.0. Affected is an unknown function of the file quickjs.c of the component Atomics Ops Handler. The manipulation results in use after free. The attack can be executed remotely. The exploit is now public and may be used. The patch is identified as ea3e9d77454e8fc9cb3ef3c504e9c16af5a80141. Applying a patch is advised to resolve this issue.

Affected products

quickjs
  • ==0.2
  • ==0.11.0
  • ==0.1
  • ==0.9
  • ==0.10
  • ==0.8
  • ==0.5
  • ==0.7
  • ==0.6
  • ==0.3
  • ==0.4

Matching in nixpkgs

Package maintainers

Quickjs-ng patch: https://github.com/quickjs-ng/quickjs/commit/ea3e9d77454e8fc9cb3ef3c504e9c16af5a80141
Pending PR for quickjs: https://github.com/bellard/quickjs/pull/483
NIXPKGS-2026-0074
published on 21 Jan 2026
updated 1 month, 2 weeks ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    3 packages
    • graphicsmagick-imagemagick-compat
    • tests.pkg-config.defaultPkgConfigPackages.MagickWand
    • tests.pkg-config.defaultPkgConfigPackages.ImageMagick
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Heap buffer overflow with attacker-controlled data in XBM parser

ImageMagick is free and open-source software used for editing and manipulating digital images. Prior to versions 7.1.2-13 and 6.9.13-38, a heap buffer overflow vulnerability in the XBM image decoder (ReadXBMImage) allows an attacker to write controlled data past the allocated heap buffer when processing a maliciously crafted image file. Any operation that reads or identifies an image can trigger the overflow, making it exploitable via common image upload and processing pipelines. Versions 7.1.2-13 and 6.9.13-38 fix the issue.

Affected products

ImageMagick
  • ==< 7.1.2-13
  • ==< 6.9.13-38

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/ImageMagick/ImageMagick/security/advisories/GHSA-r49w-jqq3-3gx8
Upstream fix: https://github.com/ImageMagick/ImageMagick/commit/2fae24192b78fdfdd27d766fd21d90aeac6ea8b8
NIXPKGS-2026-0073
published on 21 Jan 2026
updated 1 month, 2 weeks 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-server: too long and not settings compliant session

A flaw was found in Keycloak. Keycloak does not immediately enforce the disabling of the "Remember Me" realm setting on existing user sessions. Sessions created while "Remember Me" was active retain their extended session lifetime until they expire, overriding the administrator's recent security configuration change. This is a logic flaw in session management increases the potential window for successful session hijacking or unauthorized long-term access persistence. The flaw lies in the session expiration logic relying on the session-local "remember-me" flag without validating the current realm-level configuration.

References

Affected products

keycloak
  • <26.4.1
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/a34094100716b7c69ae38eaed6678ab4344d0a1d
NIXPKGS-2026-0072
published on 21 Jan 2026
updated 1 month, 2 weeks ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed
    24 packages
    • getconf
    • mtrace
    • locale
    • getent
    • iconv
    • libc
    • libiconv
    • glibcInfo
    • glibc_multi
    • glibc_memusage
    • glibcLocales
    • glibcLocalesUtf8
    • unixtools.getent
    • tests.hardeningFlags-clang.allExplicitDisabledGlibcxxAssertions
    • tests.hardeningFlags-gcc.allExplicitDisabledGlibcxxAssertions
    • tests.hardeningFlags-clang.glibcxxassertionsExplicitDisabled
    • tests.hardeningFlags-clang.glibcxxassertionsExplicitEnabled
    • tests.hardeningFlags-gcc.glibcxxassertionsExplicitDisabled
    • tests.hardeningFlags.allExplicitDisabledGlibcxxAssertions
    • tests.hardeningFlags-gcc.glibcxxassertionsExplicitEnabled
    • tests.hardeningFlags-clang.glibcxxassertionsStdenvUnsupp
    • tests.hardeningFlags-gcc.glibcxxassertionsStdenvUnsupp
    • unixtools.getconf
    • unixtools.locale
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
wordexp with WRDE_REUSE and WRDE_APPEND may return uninitialized memory

Calling wordexp with WRDE_REUSE in conjunction with WRDE_APPEND in the GNU C Library version 2.0 to version 2.42 may cause the interface to return uninitialized memory in the we_wordv member, which on subsequent calls to wordfree may abort the process.

Affected products

glibc
  • =<2.42

Matching in nixpkgs

Package maintainers

Upstream advisory: https://sourceware.org/git/?p=glibc.git;a=blob;f=advisories/GLIBC-SA-2026-0003;h=b7a6e83a1096b20e50613581f6de148302752ff3;hb=HEAD