Live › vulnerability › CVE-2026-55422
Go to dashboardTwo React components on the conda-forge status website inject externally sourced strings, such as build logs and tracebacks, into the page with dangerouslySetInnerHTML and no sanitization. An attacker who can get markup into those logs, for example through a crafted upstream package or patch output, can run script in the browser of a visitor to the site.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
The exposure is to visitors of the conda-forge status website who view the affected pages, not to teams that install conda packages. Teams that only consume conda-forge packages and do not run or embed this website can skip it. The sources do not list a patched version or a workaround, and state that no public patch existed at publication.
No product ranges from the sources yet.
Unknown from the sources.
Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
conda-forge is a GitHub organization containing repositories of conda recipes. In commits 85748ad2368a and prior, two React components render externally-sourced strings directly as HTML using dangerouslySetInnerHTML, with no sanitization (the project has no DOMPurify or equivalent dependency). JSON files are produced automatically by the conda-forge autotick bot (regro/cf-scripts) while it processes every conda-forge feedstock and its upstream source artifacts. The error/status strings embed raw output captured from those processes (build logs, patch output, tracebacks). The website renders them verbatim as HTML. At time of publication, there are no publicly available patches.
This page as .md · .json · in your agent: get_signal("CVE-2026-55422")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.