Nixpkgs Security Tracker

Login with GitHub

Published issues

All published security issues are tracked and resolved on GitHub.

NIXPKGS-2026-0289
published on 20 Feb 2026
updated 1 day, 13 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
opa-envoy-plugin has an Authorization Bypass via Double-Slash Path Misinterpretation in `input.parsed_path`

opa-envoy-plugun is a plugin to enforce OPA policies with Envoy. Versions prior to 1.13.2-envoy-2 have a vulnerability in how the `input.parsed_path` field is constructed. HTTP request paths are treated as full URIs when parsed; interpreting leading path segments prefixed with double slashes (`//`) as authority components, and therefore dropping them from the parsed path. This creates a path interpretation mismatch between authorization policies and backend servers, enabling attackers to bypass access controls by crafting requests where the authorization filter evaluates a different path than the one ultimately served. Version 1.13.2-envoy-2 fixes the issue.

Affected products

opa-envoy-plugin
  • ==< 1.13.2-envoy-2

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/open-policy-agent/opa-envoy-plugin/security/advisories/GHSA-9f29-v6mm-pw6w
Upstream patch: https://github.com/open-policy-agent/opa-envoy-plugin/security/advisories/GHSA-9f29-v6mm-pw6w
NIXPKGS-2026-0293
published on 20 Feb 2026
updated 1 day, 13 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Open WebUI vulnerable to Stored XSS via iFrame in citations model

Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to version 0.7.0, aanually modifying chat history allows setting the `html` property within document metadata. This causes the frontend to enter a code path that treats document contents as HTML, and render them in an iFrame when the citation is previewed. This allows stored XSS via a weaponized document payload in a chat. The payload also executes when the citation is viewed on a shared chat. Version 0.7.0 fixes the issue.

Affected products

open-webui
  • ==< 0.7.0

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/open-webui/open-webui/security/advisories/GHSA-xc8p-9rr6-97r2
Upstream patch: https://github.com/open-webui/open-webui/blob/6f1486ffd0cb288d0e21f41845361924e0d742b3/src/lib/components/chat/Messages/Citations/CitationModal.svelte#L163-L170
NIXPKGS-2026-0290
published on 20 Feb 2026
updated 1 day, 13 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
WordPress hCaptcha for WP plugin <= 4.22.0 - Broken Access Control vulnerability

Missing Authorization vulnerability in hcaptcha hCaptcha for WP hcaptcha-for-forms-and-more allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects hCaptcha for WP: from n/a through <= 4.22.0.

Affected products

hcaptcha-for-forms-and-more
  • =<<= 4.22.0

Matching in nixpkgs

NIXPKGS-2026-0287
published on 20 Feb 2026
updated 1 day, 13 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Go Ethereum affected by DoS via malicious p2p message

go-ethereum (geth) is a golang execution layer implementation of the Ethereum protocol. Prior to version 1.16.9, a vulnerable node can be forced to shutdown/crash using a specially crafted message. The problem is resolved in the v1.16.9 and v1.17.0 releases of Geth.

Affected products

go-ethereum
  • ==< 1.16.9

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/ethereum/go-ethereum/security/advisories/GHSA-2gjw-fg97-vg3r
Upstream patch: https://github.com/ethereum/go-ethereum/commit/895a8597cb16c02203e38707ed2d1da5c500fe60
NIXPKGS-2026-0285
published on 20 Feb 2026
updated 1 day, 13 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Cosign Certificate Chain Expiry Validation Issue Allows Issuing Certificate Expiry to Be Overlooked

Cosign provides code signing and transparency for containers and binaries. In versions 3.0.4 and below, an issuing certificate with a validity that expires before the leaf certificate will be considered valid during verification even if the provided timestamp would mean the issuing certificate should be considered expired. When verifying artifact signatures using a certificate, Cosign first verifies the certificate chain using the leaf certificate's "not before" timestamp and later checks expiry of the leaf certificate using either a signed timestamp provided by the Rekor transparency log or from a timestamp authority, or using the current time. The root and all issuing certificates are assumed to be valid during the leaf certificate's validity. There is no impact to users of the public Sigstore infrastructure. This may affect private deployments with customized PKIs. This issue has been fixed in version 3.0.5.

Affected products

cosign
  • ==< 3.0.5

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/sigstore/cosign/security/advisories/GHSA-wfqv-66vq-46rm
Upstream patch: https://github.com/sigstore/cosign/commit/3c9a7363f563db76d78e2de2cabd945450f3781e
NIXPKGS-2026-0291
published on 20 Feb 2026
updated 1 day, 13 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse removed package stalwart-cli
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Stalwart Mail Server has Out-of-Memory Denial of Service via Malformed Nested MIME Messages

Stalwart is a mail and collaboration server. A denial-of-service vulnerability exists in Stalwart Mail Server versions 0.13.0 through 0.15.4 where accessing a specially crafted email containing malformed nested `message/rfc822` MIME parts via IMAP or JMAP causes excessive CPU and memory consumption, potentially leading to an out-of-memory condition and server crash. The malformed structure causes the `mail-parser` crate to produce cyclical references in its parsed representation, which Stalwart then follows indefinitely. Version 0.15.5 contains a patch.

Affected products

stalwart
  • ==>= 0.13.0, < 0.15.5

Matching in nixpkgs

Ignored packages (1)

Package maintainers

Upstream advisory: https://github.com/stalwartlabs/stalwart/security/advisories/GHSA-jm95-876q-c9gw
NIXPKGS-2026-0286
published on 20 Feb 2026
updated 1 day, 13 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Go Ethereum Improperly Validates the ECIES Public Key in RLPx Handshake

go-ethereum (Geth) is a golang execution layer implementation of the Ethereum protocol. Prior to version 1.16.9, through a flaw in the ECIES cryptography implementation, an attacker may be able to extract bits of the p2p node key. The issue is resolved in the v1.16.9 and v1.17.0 releases of Geth. Geth maintainers recommend rotating the node key after applying the upgrade, which can be done by removing the file `<datadir>/geth/nodekey` before starting Geth.

Affected products

go-ethereum
  • ==< 1.16.9

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/ethereum/go-ethereum/security/advisories/GHSA-m6j8-rg6r-7mv8
NIXPKGS-2026-0288
published on 20 Feb 2026
updated 1 day, 13 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Go Ethereum affected by DoS via malicious p2p message

go-ethereum (geth) is a golang execution layer implementation of the Ethereum protocol. Prior to version 1.17.0, an attacker can cause high memory usage by sending a specially-crafted p2p message. The issue is resolved in the v1.17.0 release.

Affected products

go-ethereum
  • ==< 1.17.0

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/ethereum/go-ethereum/security/advisories/GHSA-689v-6xwf-5jf3
NIXPKGS-2026-0292
published on 20 Feb 2026
updated 1 day, 13 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
SillyTavern has Server-Side Request Forgery (SSRF) via Asset Download Endpoint that Allows Reading Internal Services

SillyTavern is a locally installed user interface that allows users to interact with text generation large language models, image generation engines, and text-to-speech voice models. In versions prior to 1.16.0, a Server-Side Request Forgery (SSRF) vulnerability in the asset download endpoint allows authenticated users to make arbitrary HTTP requests from the server and read the full response body, enabling access to internal services, cloud metadata, and private network resources. The vulnerability has been patched in the version 1.16.0 by introducing a whitelist domain check for asset download requests. It can be reviewed and customized by editing the `whitelistImportDomains` array in the `config.yaml` file.

Affected products

SillyTavern
  • ==< 1.16.0

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/SillyTavern/SillyTavern/security/advisories/GHSA-cccp-94vg-j92r
NIXPKGS-2026-0294
published on 20 Feb 2026
updated 1 day, 13 hours ago by @LeSuisse Activity log
  • Created automatic suggestion
  • @LeSuisse accepted
  • @LeSuisse published on GitHub
Open WebUI vulnerable to Stored XSS via iFrame embeds in response messages

Open WebUI is a self-hosted artificial intelligence platform designed to operate entirely offline. Prior to version 0.6.44, aanually modifying chat history allows setting the `embeds` property on a response message, the content of which is loaded into an iFrame with a sandbox that has `allow-scripts` and `allow-same-origin` set, ignoring the "iframe Sandbox Allow Same Origin" configuration. This enables stored XSS on the affected chat. This also triggers when the chat is in the shared format. The result is a shareable link containing the payload that can be distributed to any other users on the instance. Version 0.6.44 fixes the issue.

Affected products

open-webui
  • ==< 0.6.44

Matching in nixpkgs

Package maintainers

Upstream advisory: https://github.com/open-webui/open-webui/security/advisories/GHSA-vjm7-m4xh-7wrc
Upstream patch: https://github.com/open-webui/open-webui/blob/6f1486ffd0cb288d0e21f41845361924e0d742b3/src/lib/components/chat/Messages/ResponseMessage.svelte#L689-L703