Nixpkgs security tracker

Login with GitHub

Published issues

All published security issues are tracked and resolved on GitHub.

NIXPKGS-2026-0945
published on
Permalink CVE-2026-34528
8.1 HIGH
  • CVSS version: 3.1
  • Attack vector (AV): NETWORK
  • Attack complexity (AC): HIGH
  • Privileges required (PR): NONE
  • User interaction (UI): NONE
  • Scope (S): UNCHANGED
  • Confidentiality impact (C): HIGH
  • Integrity impact (I): HIGH
  • Availability impact (A): HIGH
updated 12 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed package filebrowser-quantum
  • @LeSuisse removed package python312Packages.filebrowser-safe
  • @LeSuisse removed package python313Packages.filebrowser-safe
  • @LeSuisse removed package python314Packages.filebrowser-safe
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
File Browser's Signup Grants Execution Permissions When Default Permissions Includes Execution

File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. Prior to version 2.62.2, the signupHandler in File Browser applies default user permissions via d.settings.Defaults.Apply(user), then strips only Admin. The Execute permission and Commands list from the default user template are not stripped. When an administrator has enabled signup, server-side execution, and set Execute=true in the default user template, any unauthenticated user who self-registers inherits shell execution capabilities and can run arbitrary commands on the server. This issue has been patched in version 2.62.2.

Affected products

filebrowser
  • ==< 2.62.2

Matching in nixpkgs

Ignored packages (4)

Package maintainers

Advisory: https://github.com/filebrowser/filebrowser/security/advisories/GHSA-x8jc-jvqm-pm3f
NIXPKGS-2026-0944
published on
updated 12 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed package temporalite
  • @LeSuisse removed package temporal-cli
  • @LeSuisse removed package temporal_capi
  • @LeSuisse removed package temporal-ui-server
  • @LeSuisse removed package python312Packages.temporalio
  • @LeSuisse removed package python313Packages.temporalio
  • @LeSuisse removed package python314Packages.temporalio
  • @LeSuisse removed package haskellPackages.temporal-media
  • @LeSuisse removed package terraform-providers.temporalcloud
  • @LeSuisse removed package postgresqlPackages.temporal_tables
  • @LeSuisse removed package haskellPackages.temporal-api-protos
  • @LeSuisse removed package postgresql13Packages.temporal_tables
  • @LeSuisse removed package postgresql14Packages.temporal_tables
  • @LeSuisse removed package postgresql15Packages.temporal_tables
  • @LeSuisse removed package postgresql16Packages.temporal_tables
  • @LeSuisse removed package postgresql17Packages.temporal_tables
  • @LeSuisse removed package postgresql18Packages.temporal_tables
  • @LeSuisse removed package haskellPackages.temporal-music-notation
  • @LeSuisse removed package haskellPackages.temporal-music-notation-demo
  • @LeSuisse removed package terraform-providers.temporalio_temporalcloud
  • @LeSuisse removed package haskellPackages.temporal-music-notation-western
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Cross Namespace Access via Batch Operation

A writer role user in an attacker-controlled namespace could signal, delete, and reset workflows or activities in a victim namespace on the same cluster. Exploitation requires the attacker to know or guess specific victim workflow ID(s) and, for signal operations, signal names. This was due to a bug introduced in Temporal Server v1.29.0 which inadvertently allowed an attacker to control the namespace name value instead of using the server's own trusted name value within the batch activity code. The batch activity validated the namespace ID but did not cross-check the namespace name against the worker's bound namespace, allowing the per-namespace worker's privileged credentials to operate on an arbitrary namespace. Exploitation requires a server configuration where internal components have cross-namespace authorization, such as deployment of the internal-frontend service or equivalent TLS-based authorization for internal identities. This vulnerability also impacted Temporal Cloud when the attacker and victim namespaces were on the same cell, with the same preconditions as self-hosted clusters.

Affected products

temporal
  • <1.30.3
  • <1.29.5

Matching in nixpkgs

pkgs.temporal

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

Ignored packages (21)

pkgs.temporalite

Experimental distribution of Temporal that runs as a single process

pkgs.temporal-cli

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

Package maintainers

https://github.com/temporalio/temporal/releases/tag/v1.29.5
https://github.com/temporalio/temporal/releases/tag/v1.30.3
NIXPKGS-2026-0943
published on
Permalink CVE-2026-35092
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 12 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed package corosync-qdevice
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Corosync: corosync: denial of service via integer overflow in join message validation

A flaw was found in Corosync. An integer overflow vulnerability in Corosync's join message sanity validation allows a remote, unauthenticated attacker to send crafted User Datagram Protocol (UDP) packets. This can cause the service to crash, leading to a denial of service. This vulnerability specifically affects Corosync deployments configured to use totemudp/totemudpu mode.

Affected products

rhcos
corosync

Matching in nixpkgs

pkgs.corosync

Group Communication System with features for implementing high availability within applications

Ignored packages (1)

Package maintainers

No upstream fix (2026-04-02)

RH tracking issue: https://bugzilla.redhat.com/show_bug.cgi?id=2453169
NIXPKGS-2026-0942
published on
Permalink CVE-2026-35091
8.2 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): LOW
  • Integrity impact (I): NONE
  • Availability impact (A): HIGH
updated 12 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed package corosync-qdevice
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Corosync: corosync: denial of service and information disclosure via crafted udp packet

A flaw was found in Corosync. A remote unauthenticated attacker can exploit a wrong return value vulnerability in the Corosync membership commit token sanity check by sending a specially crafted User Datagram Protocol (UDP) packet. This can lead to an out-of-bounds read, causing a denial of service (DoS) and potentially disclosing limited memory contents. This vulnerability affects Corosync when running in totemudp/totemudpu mode, which is the default configuration.

Affected products

rhcos
corosync

Matching in nixpkgs

pkgs.corosync

Group Communication System with features for implementing high availability within applications

Ignored packages (1)

Package maintainers

No upstream fix (2026-04-02)

RH tracking issue: https://bugzilla.redhat.com/show_bug.cgi?id=2453169
NIXPKGS-2026-0941
published on
Permalink CVE-2026-34376
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): HIGH
  • Integrity impact (I): NONE
  • Availability impact (A): NONE
updated 12 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
PdfDing: Password-protected share bypass via direct serve endpoint

PdfDing is a selfhosted PDF manager, viewer and editor offering a seamless user experience on multiple devices. Prior to version 1.7.0, an access-control vulnerability allows unauthenticated users to retrieve password-protected shared PDFs by directly calling the file-serving endpoint without completing the password verification flow. This results in unauthorized access to confidential documents that users expected to be protected by a shared-link password. This issue has been patched in version 1.7.0.

Affected products

PdfDing
  • ==< 1.7.0

Matching in nixpkgs

pkgs.pdfding

Selfhosted PDF manager, viewer and editor offering a seamless user experience on multiple devices

Package maintainers

Advisory: https://github.com/mrmn2/PdfDing/security/advisories/GHSA-42x7-vvj4-4cj3
Patch: https://github.com/mrmn2/PdfDing/commit/ae579ea98c5603d1435e0d90e81d72151564088a
NIXPKGS-2026-0940
published on
Permalink CVE-2026-34530
6.9 MEDIUM
  • CVSS version: 3.1
  • Attack vector (AV): NETWORK
  • Attack complexity (AC): LOW
  • Privileges required (PR): HIGH
  • User interaction (UI): REQUIRED
  • Scope (S): CHANGED
  • Confidentiality impact (C): HIGH
  • Integrity impact (I): LOW
  • Availability impact (A): NONE
updated 12 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed package filebrowser-quantum
  • @LeSuisse removed package python312Packages.filebrowser-safe
  • @LeSuisse removed package python313Packages.filebrowser-safe
  • @LeSuisse removed package python314Packages.filebrowser-safe
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
File Browser is vulnerable to Stored Cross-Site Scripting via text/template branding injection

File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. Prior to version 2.62.2, the SPA index page in File Browser is vulnerable to Stored Cross-Site Scripting (XSS) via admin-controlled branding fields. An admin who sets branding.name to a malicious payload injects persistent JavaScript that executes for ALL visitors, including unauthenticated users. This issue has been patched in version 2.62.2.

Affected products

filebrowser
  • ==< 2.62.2

Matching in nixpkgs

Ignored packages (4)

Package maintainers

Advisory: https://github.com/filebrowser/filebrowser/security/advisories/GHSA-xfqj-3vmx-63wv
NIXPKGS-2026-0939
published on
Permalink CVE-2026-34531
6.5 MEDIUM
  • CVSS version: 3.1
  • Attack vector (AV): NETWORK
  • Attack complexity (AC): HIGH
  • Privileges required (PR): NONE
  • User interaction (UI): NONE
  • Scope (S): UNCHANGED
  • Confidentiality impact (C): LOW
  • Integrity impact (I): HIGH
  • Availability impact (A): NONE
updated 12 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Flask-HTTPAuth invokes token verification callback when missing or empty token was given by client

Flask-HTTPAuth provides Basic, Digest and Token HTTP authentication for Flask routes. Prior to version 4.8.1, in a situation where the client makes a request to a token protected resource without passing a token, or passing an empty token, Flask-HTTPAuth would invoke the application's token verification callback function with the token argument set to an empty string. If the application had any users in its database with an empty string set as their token, then it could potentially authenticate the client request against any of those users. This issue has been patched in version 4.8.1.

Affected products

Flask-HTTPAuth
  • ==< 4.8.1

Matching in nixpkgs

Package maintainers

Advisory: https://github.com/miguelgrinberg/Flask-HTTPAuth/security/advisories/GHSA-p44q-vqpr-4xmg
Patch: https://github.com/miguelgrinberg/flask-httpauth/commit/b15ffe9e50e110d7174ccd944f642079e1dcf9ee
NIXPKGS-2026-0938
published on
Permalink CVE-2026-4370
10.0 CRITICAL
  • CVSS version: 3.1
  • Attack vector (AV): NETWORK
  • Attack complexity (AC): LOW
  • Privileges required (PR): NONE
  • User interaction (UI): NONE
  • Scope (S): CHANGED
  • Confidentiality impact (C): HIGH
  • Integrity impact (I): HIGH
  • Availability impact (A): HIGH
updated 12 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed package jujutsu
  • @LeSuisse removed package jujuutils
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Improper TLS Client/Server authentication and certificate verification on Database Cluster

A vulnerability was identified in Juju from version 3.2.0 until 3.6.19 and from version 4.0 until 4.0.4, where the internal Dqlite database cluster fails to perform proper TLS client and server authentication. Specifically, the Juju controller's database endpoint does not validate client certificates when a new node attempts to join the cluster. An unauthenticated attacker with network reachability to the Juju controller's Dqlite port can exploit this flaw to join the database cluster. Once joined, the attacker gains full read and write access to the underlying database, allowing for total data compromise.

Affected products

juju
  • <4.0.4
  • <3.6.20

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

Advisory: https://github.com/juju/juju/security/advisories/GHSA-gvrj-cjch-728p
NIXPKGS-2026-0937
published on
Permalink CVE-2026-34222
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): HIGH
  • Integrity impact (I): NONE
  • Availability impact (A): NONE
updated 12 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Open WebUI has Broken Access Control in Tool Valves

Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to version 0.8.11, there is a broken access control vulnerability in tool values. This issue has been patched in version 0.8.11.

Affected products

open-webui
  • ==< 0.8.11

Matching in nixpkgs

Package maintainers

Advisory: https://github.com/open-webui/open-webui/security/advisories/GHSA-7429-hxcv-268m
NIXPKGS-2026-0936
published on
Permalink CVE-2026-34529
7.6 HIGH
  • CVSS version: 3.1
  • Attack vector (AV): NETWORK
  • Attack complexity (AC): LOW
  • Privileges required (PR): LOW
  • User interaction (UI): REQUIRED
  • Scope (S): CHANGED
  • Confidentiality impact (C): HIGH
  • Integrity impact (I): LOW
  • Availability impact (A): NONE
updated 12 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed package filebrowser-quantum
  • @LeSuisse removed package python312Packages.filebrowser-safe
  • @LeSuisse removed package python313Packages.filebrowser-safe
  • @LeSuisse removed package python314Packages.filebrowser-safe
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
File Browser is vulnerable to Stored Cross-site Scripting via crafted EPUB file

File Browser is a file managing interface for uploading, deleting, previewing, renaming, and editing files within a specified directory. Prior to version 2.62.2, the EPUB preview function in File Browser is vulnerable to Stored Cross-Site Scripting (XSS). JavaScript embedded in a crafted EPUB file executes in the victim's browser when they preview the file. This issue has been patched in version 2.62.2.

Affected products

filebrowser
  • ==< 2.62.2

Matching in nixpkgs

Ignored packages (4)

Package maintainers

Advisory: https://github.com/filebrowser/filebrowser/security/advisories/GHSA-5vpr-4fgw-f69h