Skip to content
QuenchWorks

Roadmap

What is shipped, what is next

433 datastores and tools are hardened and shipping today. Below is what is on deck, OSI-clean options first. Every entry is built from source on Wolfi, scanned to zero fixable CVEs, signed, and pinned by digest before it moves to available.

433/496
87% shipped
43387%
Shipped
6113%
On the roadmap
20%
Blocked

Update queue

0 open

Newer upstream releases of apps already in the catalog, from the version check on. Each one ships only after its image passes the 0-CVE gate and its boot test, and its chart is re-pinned to the new digest.

AppFromToStatus
aspnet10.0.113shipped
authentik2026.8.32026.8.4shipped
backdrop1.34.5, 1.35.11.34.6, 1.35.2shipped
buildkite-agent4.4.04.6.0, 4.5.0shipped
cilium1.18.14, 1.19.8, 1.20.21.18.15, 1.19.9, 1.20.3shipped
cilium-operator1.18.14, 1.19.8, 1.20.21.18.15, 1.19.9, 1.20.3shipped
clickhouse26.7.29.12, 26.9.18.1126.7.34.3, 26.9.21.9shipped
connaisseur3.13.03.13.1shipped
coroot1.27.31.27.4shipped
documentdb0.117.01.0.RC2, 1.0.RC1, 1.0.0shipped
dotnet10.0.113shipped
dotnet-runtime10.0.113shipped
drupal11.4.911.4.10shipped
emqx6.3.16.3.2shipped
erlang27.3.4.19, 28.5.0.8, 29.1.2shipped
external-secrets2.12.02.13.0shipped
floci2.2.02.3.0shipped
floci-full2.2.02.3.0shipped
fluent-bit5.1.35.1.4shipped
flyway13.10.013.10.3shipped
ghost6.70.06.71.0shipped
gitea28.1.028.2.0shipped
gitlab-runner19.4.119.5.0shipped
homepage2.5.02.6.0shipped
hubble-relay1.18.14, 1.19.8, 1.20.21.18.15, 1.19.9, 1.20.3shipped
istio-cni1.29.8, 1.30.5, 1.31.11.29.9, 1.30.6, 1.31.2shipped
istio-proxyv21.31.11.31.2shipped
istiod1.29.8, 1.30.5, 1.31.11.29.9, 1.30.6, 1.31.2shipped
jupyterhub6.0.16.1.0, 5.5.3shipped
kgateway2.4.62.4.7, 2.3.11shipped
kgateway-envoy2.4.62.4.7, 2.3.11shipped
kubescape4.0.154.0.16shipped
kubescape-node-agent0.3.2750.3.280shipped
kubescape-operator0.2.1810.2.190shipped
kubescape-synchronizer0.0.1670.0.169shipped
kubevuln0.3.5460.3.561shipped
kuma2.14.63.0.0shipped
litellm1.105.11.106.0, 1.103.5shipped
livekit1.13.91.13.10shipped
mailpit1.31.51.31.6shipped
mattermost11.11.112.0.0shipped
nextcloud34.0.434.0.5shipped
nginx1.30.51.30.6shipped
nginx-gateway-fabric2.7.22.8.0shipped
nginx-gateway-fabric-nginx2.7.22.8.0shipped
node24.22.0, 26.12.0shipped
ntfy2.30.02.32.0shipped
odoo19.0.2026101419.0.20261018shipped
ollama0.40.40.40.6, 0.40.5shipped
oras1.3.41.3.5shipped
otel-collector0.162.00.163.1shipped
pgbouncer1.26.01.26.1shipped
policy-reporter3.11.03.11.1shipped
pulumi3.268.03.270.0shipped
redis-exporter1.93.01.94.0shipped
rqlite10.6.010.6.2shipped
rust1.99.1shipped
spire1.15.31.15.4shipped
tempo3.1.03.0.4shipped
traefik3.7.143.7.15shipped
trivy0.75.00.76.0shipped
trivy-scanner0.75.00.76.0shipped
uv0.13.00.13.1shipped
vllm0.31.00.32.0shipped
xyops1.1.71.1.8shipped
zitadel4.19.44.19.5shipped
ztunnel1.29.8, 1.30.5, 1.31.11.29.9, 1.30.6, 1.31.2shipped
cockroachdb26.2.726.2.8held

26.2.8 is built with go1.25.13; the stdlib fixes need go 1.26.9 or later.

coolify-app4.3.234.4.6held

4.4 replaces coolify-realtime with Reverb and coolify-terminal: a stack redesign.

gotenberg8.37.08.38.1held

Wolfi chromium is still 149.0.7827.53.

grafana13.1.713.2.4held

13.2 bundles prebuilt gpx_* plugin binaries.

jellyfin12.112.2held

12.2 still ships the prebuilt SkiaSharp blob.

opensearch-dashboards3.8.03.9.0held

3.9.0 bundles DOMPurify 3.4.13 and maplibre-gl 4.5.2.

pnpm11.28.4, 12.9.111.28.6, 12.14.0held

npm 12 cooldown: 2026-10-20 and 2026-10-25.

quickwit0.9.10.9.2held

0.9.2 still locks thrift 0.17.0 (CVE-2026-43868, no 0.17.x fix); held on 0.9.1.

renovate44.148.144.167.5held

npm 12 cooldown, published 2026-10-12.

tigera-operator1.42.21.44.0held

Deploys Calico 3.33.0: every calico image and the chart move together.

trino483484held

484 bundles parquet-jackson 1.18.1 with a renamed jackson 2.22.2 (4 HIGH); held on 483.

xwiki17.10.1317.10.14held

17.10.14 still pins solr 9.4.1 and the jetty 10 client.

support-bundle-kit1.0.01.0.1, 0.0.97skipped

The checker proposes a downgrade to 0.0.97; skipped.

Available now

433

AI gateway

2

Analytical

4

Apps & productivity

32

Base image

1

Build tool

7

CI

2

CI/CD & registry

29

Cache

7

Coordination

15

Coordination & mesh

24

Database

1

Databases & engines

14

Developer tools / IDE

1

Document

5

Gateway

30

Git

4

GitOps

3

Graph

2

Identity

13

Language runtime

13

Machine learning & AI

14

Media & streaming

3

Messaging

20

Metrics/Exporter

6

Networking

9

Object storage

5

Observability

33

PaaS

3

Registry

10

Relational

10

Runtime base

4

Search

8

Search & vector

1

Secrets

3

Secrets & identity

2

Security & supply chain

50

Storage & platform

21

Time series

4

Vector

1

Wide-column

2

Workflow

15

Held — built, not shipped

2

These build and test clean but can't reach 0 fixable CVEs yet — the app or its base pins a dependency below the version that fixes a known CVE, so we hold it rather than ship a vulnerable image. Each re-lists automatically the moment upstream ships the fix. Tapwhy blocked? for the exact pin.

Apps & productivity

1
  • Apache Supersetblocked

    Data exploration and business-intelligence dashboard platform backed by a metadata database and Redis. Measured 2026-09-26: 6.1.0 (and 6.0.0) have no advisories, 5.0 does. It pins pyarrow<19, whose wheel statically embeds OpenSSL 3.3.0 and libcurl 8.7.0 (Wolfi packages pyarrow 23 and newer only), and a loose PyPI resolve pulls a flask-caching that breaks its metastore cache. Needs a build from the tag's pinned requirements, a module float, and a pyarrow swap tested against result_set.py.

    Apps & productivityApache-2.0

Observability

1
  • OpenSearch Dashboardsblocked

    Visualization UI for OpenSearch. Measured 2026-09-26 at 3.8.0: the full bundle has 12 vulnerable npm packages, among them maplibre-gl 5.2.0 (CRITICAL, fixed only in 6.x) compiled into the maps, observability and anomaly-detection plugin bundles. The min distribution drops those plugins, leaving 7 patch-level fixes, but dompurify 3.4.11 is compiled into the Discover and chat UI bundles, so swapping node_modules would clear the scan and still ship the vulnerable code. Needs a from-source UI build (yarn build of OSD) to ship honestly. Re-measured 2026-10-07: an image that swaps node_modules scans 0 but still carries dompurify 3.4.11/3.4.12 in 8 browser bundles and maplibre-gl 5.2.0 in 3, so it is held. Upstream main has dompurify ^3.4.13 and maplibre-gl 6.4.1; Dashboards 3.9.0 (unreleased) is the next build to measure.

    ObservabilityApache-2.0

On the roadmap

61

Candidates, not commitments. next = strongest near-term picks;planned and exploring follow. Items marked caution are source-available (not OSI) and would ship only with a loud license note and the clean alternative called out. (Apps that build but can't hit 0 fixable CVEs yet are in Held, above.) Each card also shows how it will ship: image + chart for a deployable service, orimage only for a base/CLI/sidecar utility (like busybox).

Search & vector

1
  • Milvusplanned

    Scalable vector database for AI workloads. Measured 2026-09-30: releases ship only compose files and Wolfi has no package, so it is a from-source build: the C++ core through conan (about a hundred packages, often fetched as prebuilt binaries the scanner cannot see) plus a Rust component, a multi-hour build. Held until Wolfi packages it or a scanned from-source conan build is scoped.

    image + chartApache-2.0

Messaging & streaming

2
  • Apicurio Registryplanned

    API and schema registry for Kafka, Avro, and Protobuf. Measured 2026-09-25: the 3.3.3 app distribution carries 467 findings; 26 in-place jar swaps clear all but opentelemetry-api 1.57.0 (CVE-2026-45292, fixed only in 1.62.0), which adds packages the prebuilt Quarkus index cannot load. Needs a source build that regenerates the index.

    image + chartApache-2.0
  • Redpandaplanned

    Kafka-compatible streaming. Source-available, not OSI.

    clean alt: Kafka or Pulsar (Apache-2.0), both already shipped.

    image + chartBSL-1.1caution

Coordination & mesh

6
  • Cilium Envoyplanned

    Cilium's own patched Envoy; not reusable from our stock envoy image. Measured 2026-10-19: Wolfi packages only cilium-envoy-1.19 at 1.19.3, behind our cilium lines (1.18.15, 1.19.9, 1.20.3), and cilium/proxy builds Envoy with Bazel (hours per arch, past the CI budget). Hold until Wolfi tracks each cilium line; the cilium chart keeps L7 proxy off until then.

    image + chartApache-2.0
  • Consulplanned

    HashiCorp Consul. BUSL-1.1: source-available, NOT OSI. Recommendation is to skip -- the mesh slot is already covered by Kuma (shipped) plus Linkerd and Istio in this wave, all OSI-licensed. Revisit on explicit demand.

    clean alt: Kuma (Apache-2.0) -- already shipped; or Linkerd / Istio.

    image + chartBUSL-1.1caution
  • Consul Dataplaneplanned

    Envoy-based sidecar for Consul. MPL, so cleaner than the BUSL server.

    image + chartMPL-2.0
  • Consul K8s Control Planeplanned

    The operator that makes Consul work on Kubernetes.

    image + chartMPL-2.0
  • Istioplanned

    Service mesh built on Envoy. Ambient mode SHIPPED 2026-10-08: istiod, istio-cni and ztunnel charts on 1.30.5, gated on mTLS (HBONE) traffic between two pods. Still held: L7 waypoints and sidecar mode, which need the Istio proxyv2 image, which has no melange-buildable path.

    image + chartApache-2.0
  • Nomadplanned

    Workload scheduler. Source-available, not OSI.

    image + chartBUSL-1.1caution

Databases & engines

10
  • Percona XtraDB Cluster Operatornext

    Operator for Percona XtraDB Cluster (MySQL): synchronous multi-primary HA via Galera, with automated backups and point-in-time recovery. Image SHIPPED 2026-09-27 (1.18.0, 1.19.1, 1.20.0; it is also the pods' init image). Chart HELD: in the kind gate the operator creates the cluster and its init containers complete, but the Percona 8.4.8 database pod starts mysqld with wsrep provider none and never becomes ready, and it does the same with upstream's init image and with the 8.0 database image. Percona's forum reports the same failure in kind and minikube on Linux; the chart waits for a gate on a non-kind cluster.

    image + chartApache-2.0
  • ArangoDBplanned

    Multi-model database for documents, graphs, and key-value. Checked 2026-09-27: the repository LICENSE is the Business Source License 1.1, not Apache-2.0.

    image + chartBSL-1.1caution
  • Liquibaseplanned

    Database schema change and migration management. Relicensed: 5.x is under the Functional Source License 1.1 (source-available, Apache-2.0 two years after each release, competing use restricted); the last Apache-2.0 release is 4.33.0 and its line is no longer patched. Flyway (Apache-2.0) covers the same job.

    image + chartFSL-1.1caution
  • MongoDB Community Operatorplanned

    MongoDB Community Kubernetes Operator: replica-set HA, automated failover, and TLS via CRDs. The operator is Apache-2.0; note the MongoDB server it deploys is SSPL (not OSI). Held 2026-10-07: the community operator repo is archived; its successor mongodb/mongodb-kubernetes (1.13.0, Apache-2.0 for Community clusters) runs every member beside mongodb-agent, a closed-source binary its Dockerfile downloads prebuilt (agent 109.0.1.9310-1), which cannot be built or scanned.

    image + chartApache-2.0
  • SurrealDBplanned

    Multi-model database. Source-available, not OSI.

    image + chartBUSL-1.1caution
  • Aerospikeexploring

    Real-time key-value database; community edition is AGPL.

    image + chartAGPL-3.0agpl
  • Couchbaseexploring

    Distributed document database. Source-available, not OSI.

    clean alt: CouchDB (Apache-2.0), already shipped.

    image + chartBSL-1.1caution
  • JanusGraphexploring

    Distributed graph database over pluggable storage backends. Measured 2026-09-26: the newest release (1.1.0, 2024-11) carries 57 vulnerable packages (4 CRITICAL, 35 HIGH) in its dist. The project is active but has not released since; shipping at 0 CVEs needs a from-source Maven build with dependency management across the tree.

    image + chartApache-2.0
  • KeyDBexploring

    Multi-threaded Redis fork; BSD-licensed and Redis-protocol compatible. Held 2026-09-25: upstream is dormant (last release 6.3.4 in October 2023, last push May 2024) on a Redis 6.2 base, so it misses the Lua and protocol fixes Redis and Valkey shipped since. Valkey covers the slot.

    image + chartBSD-3-Clause
  • Tiny RDMexploring

    Modern Redis/Valkey desktop GUI (Wails/Go+Vue). A desktop client, not a deployable server, so it falls outside the hardened in-cluster image model — a web Redis UI (e.g. redis-commander) would be the cache-stack UI instead.

    image + chartGPL-3.0agpl

Storage & platform

4
  • Apache Ozoneplanned

    Scalable distributed object store (S3 + HDFS). Measured 2026-09-28: the 2.2.1 distribution carries 143 fixable findings in 22 jars. Most swap on their own line (netty 4.1.137, jackson 2.21.5, log4j 2.26.1), but jetty-server 9.4 is fixed only in 12.1, spring-core 5.3.39 only in 7.0 and aircompressor 0.27 only in 2.x. Needs an upstream move off those lines.

    image + chartApache-2.0
  • Dokployplanned

    Self-hostable PaaS on Docker Swarm. Open-core: most is Apache-2.0, the /proprietary parts are source-available (DSAL-1.0). Not a fit for the hardened catalog: it requires root, the Docker socket, and an initialized Swarm, so it cannot run nonroot or read-only.

    clean alt: Coolify (Apache-2.0), already shipped.

    image + chartApache-2.0 + DSAL-1.0caution
  • MinIOplanned

    S3-compatible object storage; relicensed to AGPL-3.0. Held 2026-10-08: minio/minio is archived (README: no longer maintained; the alternatives are the proprietary AIStor editions), last release RELEASE.2025-10-15T17-29-55Z. An archived server gets no CVE fixes. SeaweedFS, Garage, RustFS and Ceph (RGW) are the S3 options in the catalog.

    clean alt: SeaweedFS / Garage / RustFS (Apache-2.0), all already shipped.

    image + chartAGPL-3.0agpl
  • SonarQubeplanned

    Continuous code-quality and security inspection. Measured 2026-09-28: the 26.9 Community distribution carries 72 findings (4 critical), most inside its bundled Elasticsearch 9.4.3 (x-pack modules, transport-netty4) and in fat jars (sonar-application, the scanner engine). Needs the embedded Elasticsearch rebuilt or swapped before it can gate clean.

    image + chartLGPL-3.0

Apps & productivity

8
  • Appsmithplanned

    Low-code internal-tools and admin-panel builder backed by PostgreSQL and Redis. Measured 2026-09-30 (v2.4.2, no release binaries, no Wolfi package): the upstream image is all-in-one under supervisor (Java server, React editor, Node RTS and MCP, Caddy, Redis, PostgreSQL and MongoDB). Appsmith has since removed PostgreSQL support (scripts/prepare_server_artifacts.sh builds only the MongoDB server), so the server needs MongoDB, which is SSPL. A clean image would run against an external MongoDB, or FerretDB/DocumentDB if Appsmith's use of transactions works there, which is unverified. Maven and yarn builds exceed the local gate, so it is gated in CI.

    image + chartApache-2.0
  • Discourseplanned

    Ruby discussion and forum platform backed by PostgreSQL and Redis. Measured 2026-09-29 at 2026.9.0: the Gemfile.lock and pnpm-lock.yaml scan clean and Wolfi has ruby-3.4, ImageMagick 7, pngquant and oxipng, but two native gems ship only prebuilt binaries the scanner cannot see into: libv8-node (V8 for mini_racer, which PrettyText needs; a source build is a multi-hour Node V8 compile per arch) and sass-embedded (a bundled dart-sass, needed at runtime for theme CSS; Wolfi has the Dart SDK, so that half is buildable). Held on the V8 build.

    image + chartGPL-2.0-or-lateragpl
  • Gotenbergplanned

    Stateless HTML and URL to PDF conversion API. Recipe committed 2026-09-26 (Chromium variant; Wolfi has no LibreOffice): everything gates clean except chromium CVE-2026-13032, fixed in 149.0.7827.200, which Wolfi has not published yet. Ships when it does.

    image + chartMIT
  • Moodleplanned

    PHP learning management system backed by MySQL, MariaDB, or PostgreSQL. Measured 2026-09-29 at 5.2.3: the PHP side is fixable (5.2 runs composer install at build, so guzzle, psr7, aws-sdk-php, php-jwt, slim and jmespath float like mediawiki), but the H5P editor ships a prebuilt CKEditor 5 43.0.0 bundle (CVE-2024-45613, CVE-2026-28343 fixed only in 47.6.0; lodash-es CVE-2026-4800 HIGH). The fix is a four-major rebuild of a custom H5P build nothing would test, so the image is held until Moodle updates that bundle.

    image + chartGPL-3.0-or-lateragpl
  • Rocket.Chatplanned

    Self-hosted team chat platform backed by MongoDB. Measured 2026-10-20 at 8.9.0: the official build compiles apps/meteor/ee/ and ee/ (Rocket.Chat Enterprise license, not OSI) into the same Meteor bundle, so a clean MIT-only image means a source build with the ee packages removed; the upstream image also scans 160 fixable npm findings in 44 packages. Hold until a source build without ee/ is sized.

    image + chartMIT
  • SuiteCRMplanned

    PHP customer relationship management application backed by MySQL or MariaDB. Measured 2026-10-04 on 8.10.2: the shipped frontend is Angular 18 (203 yarn.lock findings, fixed only in Angular 19 and later) and api-platform/core v3.4.17 is fixed only in v4, so both need major ports upstream; guzzle and flysystem would float. Held until SuiteCRM moves to Angular 19+ and api-platform 4.

    image + chartAGPL-3.0-onlyagpl
  • Chromiumexploring

    Headless browser for rendering, scraping, and PDF export.

    image + chartBSD-3-Clause
  • XWikiexploring

    Enterprise wiki and structured collaboration platform. Measured 2026-10-14 (17.10.13 LTS and 18.8.0): recipe written, held before CI. After safe jar swaps 8 fixable findings remain on both lines: bundled solr-core 9.4.1 (fixes need Solr 9.8 to 9.10.1, a whole Solr and Lucene jar set), the Jetty 10.0.26 client (fixes only on Jetty 11/12, no 10.x release) and opennlp-tools (fix only in 2.x). XWiki master still pins Solr 9.4.1. Unblocks with an XWiki release on Solr 9.10.1 or newer and a fixed Jetty client.

    image + chartLGPL-2.1

Media & streaming

1
  • Jellyfinplanned

    Self-hosted media server for movies, music, and live TV. Built 2026-09-29 from Wolfi's jellyfin 12.1 apks and it gates clean (0 fixable CVEs, boot test passes), but it is held: libSkiaSharp.so, a prebuilt NuGet binary from a Debian 10 clang 13 build, statically links libjpeg-turbo 2.1.5.1 (behind several upstream security fixes), libpng and other image libraries the scanner cannot see. Needs Skia built against the system libraries. The recipe is committed as blocked.

    image + chartGPL-2.0-onlyagpl

Workflow & data

4
  • Apache Pinotplanned

    Real-time distributed OLAP datastore for low-latency analytics. Measured 2026-09-28: the 1.5.1 distribution carries 444 fixable findings (11 critical) in 31 packages, much of it netty 4.1.134 and jackson-databind 2.21.1 repeated across plugin jars. Measure again after the next release.

    image + chartApache-2.0
  • Camundaplanned

    Process automation and BPMN orchestration including the Zeebe engine. Checked 2026-09-27: the repository is under the Camunda License 1.0, not Apache-2.0.

    image + chartCamunda-License-1.0caution
  • Apache Druidexploring

    Real-time analytics database for high-concurrency OLAP queries. Held 2026-09-26: the 37.0.0 distribution carries 137 findings. Two sit in the core lib/ and cannot be swapped: netty 3.10.6 (8 findings, end of life, fixes only exist in netty 4; Druid's HTTP client is built on it) and calcite-core 1.37.0 (the SQL planner, fixed in 1.42). Shipping needs Druid itself to move off both.

    image + chartApache-2.0
  • Cubeexploring

    Semantic layer and analytics API over your data. Held 2026-10-20 (images apps/cube): the server needs the Rust addon @cubejs-backend/native, and a from-source build of 1.8.8 compiles flatbuffers 2.1.2 (CRITICAL), thrift 0.13.0 and lexical-core 0.8.5 from Cube's pinned 2022 arrow/datafusion forks. Unblock: a release that moves cubesql off those forks.

    image + chartApache-2.0

Machine learning

6
  • Langflowplanned

    Visual builder for LLM applications and agent workflows. Measured 2026-09-28: 1.12.3 resolves to 457 packages (2.3 GB). The scanner reports only chromadb 1.5.9 (no fix), but the wheels carry what it cannot see: OpenSSL 3.5.1 (ibm_db.libs), OpenSSL 3.6.2 and libcurl 8.20.0 inside pyarrow, BoringSSL in grpcio and hf_xet, and 7 bundled .libs directories (numpy, scipy, pillow, cassandra-driver). Wolfi has py3.13 pyarrow, grpcio, numpy, tokenizers and orjson, but no onnxruntime, chromadb or ibm_db, so an honest 0-CVE build needs those built from source or dropped.

    image + chartMIT
  • Langfuseplanned

    LLM observability and tracing platform backed by PostgreSQL, ClickHouse, Redis and S3. Held 2026-09-27: the core is MIT, but ee/, web/src/ee and worker/src/ee are under the Langfuse Enterprise License, which forbids distributing them, and 80 core files import from those 120 files. An image needs a build with the ee paths removed and stubbed.

    image + chartMIT
  • Open WebUIplanned

    Self-hosted web UI for chatting with local and remote LLMs. Checked 2026-09-27: the license is BSD-3-Clause plus a branding clause (the Open WebUI branding may not be altered for deployments above 50 users without permission), so it is not OSI. 0.11.4 also pins sentence-transformers, transformers, onnxruntime and opencv.

    image + chartOpen WebUI Licensecaution
  • AnythingLLMexploring

    Self-hosted chat-with-your-documents LLM application. Measured 2026-10-20 at v1.18.0: the upstream image scans 445 fixable npm findings in 61 packages, ships 24 native .node addons, and runs on Prisma's prebuilt Rust query engine (libquery_engine .so.node), which the scanner cannot read. Hold until a build with prisma-engines from source (cargo auditable) is sized.

    image + chartMIT
  • Kubeflow Pipelinesexploring

    ML pipeline orchestration on Kubernetes. Partly built 2026-10-20 (2.17.2): api-server, persistence agent, scheduled workflow controller, driver, launcher and frontend images ship 0-CVE (images 405e86c8). The chart is held: v2 runs need the ML Metadata store server, whose binary (Wolfi 1.17.1, upstream 1.21.0) statically links sqlite 3.39.2, zlib 1.2.12, gRPC 1.46.3, MariaDB Connector/C 3.0.8 and libpq 12.1, invisible to the scanner. Unblock: an MLMD release on current libraries, or our own Bazel build against Wolfi system libraries.

    image + chartApache-2.0
  • TensorFlow Servingexploring

    High-performance serving system for TensorFlow models. Measured 2026-10-20 at 2.21.0: tensorflow_model_server is a Bazel build of all of TensorFlow (hours per arch, past the CI budget), and the official binary links TensorFlow, gRPC, protobuf and absl statically, so the scanner cannot read what is inside. Hold until a source build fits the CI budget.

    image + chartApache-2.0

Observability

4
  • Kibanaplanned

    Visualization and dashboards for Elasticsearch. Default distribution is Elastic-2.0, not OSI.

    clean alt: OpenSearch Dashboards (Apache-2.0) over OpenSearch, both open.

    image + chartElastic-2.0caution
  • Logstashplanned

    Server-side log and event processing pipeline. Default distribution is Elastic-2.0, not OSI.

    clean alt: Vector (MPL-2.0) or Fluentd (Apache-2.0), both open pipelines.

    image + chartElastic-2.0caution
  • Percona PMMplanned

    Percona Monitoring and Management — deep MySQL/PostgreSQL/MongoDB observability (query analytics) built on Prometheus, Grafana and VictoriaMetrics. AGPL, OSI-approved. Sized 2026-10-08 at v3.9.1 (no release binaries): pmm-server is one container that an Ansible playbook assembles on Oracle Linux 9 from eight RPMs built in the repo (pmm-managed, qan-api2, vmproxy, pmm-dump, pmm-ui, percona-dashboards) plus Percona forks of Grafana (12.4.5, frontend changes, so a full Node build unlike our grafana image) and VictoriaMetrics (pmm-6401-v1.149.0), with ClickHouse, PostgreSQL 14, nginx and supervisord in the same image. Several images of work plus a multi-process supervisor design; it waits for local gates (the btrfs metadata hold).

    image + chartAGPL-3.0
  • Cortexexploring

    Horizontally scalable, multi-tenant Prometheus storage. Held 2026-10-05: four prometheus/prometheus CVEs (two HIGH) are fixed only in 0.311.3 (Prometheus 3.11.3), but Cortex 1.21.1 is on 0.308.1 and imports tsdb/errors, removed in Prometheus 3.10; Cortex master is on 0.309.1 and still imports it. Unblocks when a Cortex release moves to Prometheus 3.11.

    image + chartApache-2.0

Secrets & identity

2
  • EJBCAplanned

    Enterprise PKI certificate authority (Community Edition) backed by a relational database. Measured 2026-10-04 on r9.6.3 (source only, no release assets): 167 vendored jars in lib/ that Trivy identifies none of, so its scan is blind there; by filename bcprov 1.84 (CVE-2026-8763, fixed 1.85) and freemarker 2.3.34 (CVE-2026-84939, fixed 2.3.35) need swaps. Buildable with Gradle on our WildFly image; a multi-session job, not a hold.

    image + chartLGPL-2.1-or-later
  • Teleportplanned

    Access plane providing identity-based SSH, Kubernetes, and database access. Community edition is AGPL-3.0.

    image + chartAGPL-3.0-onlyagpl

Security & supply chain

3
  • Daggerplanned

    Programmable CI/CD engine that runs pipelines in containers. Sized 2026-09-27: the CLI is plain Go, but the engine image bundles runc, CNI plugins and the Go, Python and TypeScript SDK runtimes as builtin content that upstream builds with Dagger itself. A multi-day build; not started.

    image + chartApache-2.0
  • Wazuhplanned

    SIEM and XDR platform with manager, indexer, and dashboard components.

    image + chartGPL-2.0-onlyagpl
  • Kanikoexploring

    Build container images inside Kubernetes without a daemon. Held 2026-09-25: Google archived it in June 2025 (continued as osscontainertools/kaniko 1.28 and chainguard-dev/kaniko 1.25), and the executor unpacks image layers over its own root filesystem, so it must run as root, against the nonroot rule. BuildKit rootless is the likelier fit.

    image + chartApache-2.0

Stacks

4
  • ai-stackexploring

    Ollama (or vLLM) + Open WebUI + Qdrant — self-hosted LLM serving, a chat UI, and a vector DB for retrieval-augmented generation. Qdrant is built; needs Ollama/vLLM + Open WebUI images.

    image + chartApache-2.0
  • analytics-stackexploring

    Apache Superset + Trino + PostgreSQL — federated SQL analytics with self-service BI dashboards. PostgreSQL is built; needs Superset + Trino.

    image + chartApache-2.0
  • mongodb-ha-stackexploring

    Operator-based HA MongoDB: MongoDB Community Operator + a metrics exporter — replica-set failover. CRD-driven. The operator is Apache-2.0, but MongoDB itself is SSPL (not OSI), so the stack inherits that caution.

    clean alt: FerretDB (Apache-2.0) on the pg-ha-stack — a MongoDB-compatible, fully-open document database over PostgreSQL.

    image + chartSSPL-1.0caution
  • search-stackexploring

    Umbrella: OpenSearch + OpenSearch Dashboards — search with a UI. Held 2026-10-07: chart built and gated (OpenSearch document found through Dashboards), but it bundles the opensearch-dashboards image, which is held (see that entry).

    image + chartApache-2.0

CI/CD & registry

3
  • GitLab CEexploring

    Full DevOps platform (Git forge + CI/CD + registry). Heavy fit: a large Ruby monolith that bundles PostgreSQL, Redis, Gitaly, Sidekiq and Workhorse, and the gitlab-org/gitlab repo is mostly EE-proprietary — only the CE-flagged code is MIT. Far from the minimal one-purpose hardened model.

    clean alt: Gitea or Forgejo — lightweight, fully-open Git forges that drop straight into the gitops-stack.

    image + chartMITcaution
  • KubeVirtexploring

    Run virtual machines as Kubernetes workloads. Sized 2026-10-08 at v1.9.0: upstream assembles its images with Bazel from CentOS Stream 9 RPMs (libvirt, qemu-kvm, passt). Wolfi has qemu 11.1.2 but no libvirt or passt package, so virt-launcher needs both built from source alongside the Go components (virt-operator, virt-api, virt-controller, virt-handler); it waits for local gates.

    image + chartApache-2.0
  • OneDevexploring

    Self-hosted Git server with built-in CI/CD, issues and kanban (Java). Heavier than Gitea/Gogs but far lighter than GitLab; an all-in-one gitops-stack backend option. Measured 2026-10-07 at 16.8.5 (47 findings): jackson-databind/core 2.22.2 in lib/ swap cleanly, but Hazelcast 5.7.0 (its newest release) relocates jackson 2.21.2 and tools.jackson 3.1.2 under com/hazelcast/shaded/, which needs a bytecode relocation rewrite or a Hazelcast release; logback 1.4.14 needs the 1.5 line; boot/ ships prebuilt Tanuki wrapper binaries.

    image + chartMIT

Gateways & proxies

3
  • Apache ShenYuplanned

    Java API gateway. shenyu-bootstrap + shenyu-admin; admin needs a database. Held 2026-10-19: the 2.7.1 dists (trivy rootfs) carry 234 (admin) and 309 (bootstrap) fixable findings, 27 CRITICAL, on Spring Boot 3.3.1 / Spring 6.1.10 whose fixes sit in Boot 4 and Spring 7, plus Shiro 1.13 (fix 2.x), Tomcat 10.1.25 and fastjson 1.2.76; not jar-swappable. Unblock: an upstream release on a current Spring line.

    image + chartApache-2.0
  • Higressplanned

    Alibaba's Istio+Envoy-based gateway. Two components (higress-core, higress-console) and it inherits Istio/Envoy build weight. Measured 2026-10-20 at v2.2.5: the gateway image runs Higress's own patched Envoy (a Bazel build, hours per arch, past the CI budget; same wall as Cilium Envoy) plus pilot-agent, and scans 163 Go findings; the controller scans 85 Go findings on top of 446 Ubuntu ones. The Go parts are buildable; the patched Envoy is the hold.

    image + chartApache-2.0
  • Skipperplanned

    Zalando's HTTP router. BLOCKING: GitHub reports NOASSERTION and the LICENSE fetch came back empty -- resolve the license before writing a recipe.

    image + chartUNVERIFIEDcaution
blocked

Why some apps are held

QuenchWorks ships nothing that carries a fixable CVE. A few apps build cleanly but can't reach that bar yet: the app itself pins a dependency below the version that fixes a known CVE, so patching it would break the app's own declared constraints. Those are marked blocked: built and tested, held (not shipped) until upstream relaxes the pin or backports the fix. They go live the moment that lands. Nothing already in the catalog carries a known fixable CVE to get there faster.

Held in the image factory (10)

Each hold, as written in its recipe, with the date it was last re-measured.

  • actions-runner
    actions-runner: GitHub's self-hosted Actions runner, from the official release
    tarball (a self-contained .NET app), per arch. FROM_SOURCE=0. Latest only: GitHub
    stops accepting old runner versions after about 30 days. Each sha256 is from a
    download that matched the digest in the release notes.
  • cockroachdbmeasured
    STATUS 2026-10-11 (later): FROM-SOURCE BUILD MEASURED, NOT FEASIBLE; stays BLOCKED.
      2026-10-12 re-measured: 26.3.2 is out and still built with go1.26.6 (go version on the official
      linux-amd64 binary); the stdlib fixes need go >= 1.26.9. Hold unchanged.
      2026-10-14 re-measured: cockroachdb/go now has a cockroach-go1.26.9 branch (2026-10-13), so the
      next release should be built on a fixed toolchain. No release built on it yet.
      Next tick: check the next tag's binary with `go version` and unblock if it reports >= go1.26.9.
      2026-10-19 re-measured: 26.2.8 (tarball sha256 8f3fa5b5...) is built with go1.25.13; hold unchanged.
      User approved a source build on Go >= 1.26.9. Measured via the GitHub API, no clone:
      1) No plain `go build`: generated code is not committed (v26.2.7 pkg/roachpb has 0
         *.pb.go, pkg/sql/opt/memo no *.og.go); only `./dev generate` (Bazel 7.6.0 fork) makes it.
      2) Bazel builds with `--define gotags=bazel,gss`, and the bazel tag needs the
         cockroachdb/go runtime fork (pkg/util/grunning/enabled.go calls
         runtime.Grunningnanos; the fork carries 20 runtime patches: grunningnanos,
         PropagateCancel, CurrentP, Yield, SetGCAssistEnabled, NumRunnableGoroutines, ...).
         Wolfi go-1.26 lacks them. The fork's newest branch is cockroach-go1.26.6; there is
         no 1.26.9 fork, so we would have to rebase and maintain 20 runtime patches ourselves.
      3) Only 26.2.x source is public: no v26.3.x tag and no release-26.3 branch on GitHub
         (master pins go 1.26.2). v26.2.7 targets the go1.25.13 fork API.
      4) Upstream builds on self-hosted big/huge runners with prebuilt cross toolchains
         that run on x86_64 hosts only; not a 4 vCPU / 14 GB-disk native arm64 runner.
      Also checked: 26.3.2 (published, sha256 amd64 1b618025..., arm64 0d529bc2...) is still
      built with go1.26.6 on both arches. No CI round was spent.
      Unblock: a release whose `go version` reports >= go1.26.9 (or 1.27.2), or a
      cockroachdb/go fork branch on >= 1.26.9 plus public source for that line.
    STATUS 2026-10-11: BLOCKED (BLOCKED=0 -> 1), upstream-gated on the Go toolchain.
      The 26.2.7 gate fails on stdlib in usr/bin/cockroach: upstream built it with go1.25.13,
      and CVE-2026-78667 (HIGH) and its siblings are fixed only in Go 1.26.9 / 1.27.2; the
      go1.25 line gets no fix. The newest release, 26.3.1, was checked the same day
      (`go version` on the binary from binaries.cockroachdb.com, tarball sha256
      92b4ca97...): go1.26.6, still below 1.26.9. No published CockroachDB binary clears
      the gate, and this recipe ships upstream's binary rather than a Bazel source build.
      Unblock when a release is built with Go >= 1.26.9 (check `go version` on its binary),
      then add it to VERSIONS with both arch sha256s.
    cockroachdb: ships upstream's OWN official per-arch self-contained binary tarball
    (sha256-verified against binaries.cockroachdb.com's published .sha256sum), hardened
    on a minimal apko base. Single version: the newest stable patch, full X.Y.Z, used
    as-is.
      __VER__     = version (rendered quoted into melange version:)
      __SHA_AMD__ = linux-amd64 tarball sha256   __SHA_ARM__ = linux-arm64 tarball sha256
  • cube
    cube: Cube (cube-js/cube, Apache-2.0 core), the semantic layer and REST/GraphQL/SQL API,
    from the @cubejs-backend/server npm packages on Wolfi nodejs. No recipe yet: held below.
  • denomeasured
    FROZEN 2026-10-14 (user decision): keep the published 2.9.7, take NO further updates.
      On 2026-10-09 Deno announced its team is joining Cloudflare: Deno Deploy shuts down about six
      months later, and the runtime gets one more year of monthly bug-fix and security releases, then
      its own development ends (no successor maintainer named). scripts/check/deno.py caps candidates
      at 2.9.7 so the daily update check never offers a bump. Sources:
      https://alternativeto.net/news/2026/10/deno-team-joins-cloudflare-as-runtime-development-winds-down/
      https://www.beri.net/article/cloudflare-deno-acquisition-deno-deploy-shutdown-six-months-runtime-one-year-workers-migration
      https://www.highcircl.com/en/blog/deno-joins-cloudflare-runtime-end (2026-10-10; counts both clocks
      from 2026-10-09: Deploy off around April 2027, runtime development ends around October 2027; neither
      date is official, and Deno says the code stays open source for anyone who continues it.)
      The 2026-10-13 hold below still describes the 7 hidden crate findings in 2.9.7.
    STATUS: BLOCKED 2026-10-13 on deno's own Cargo.lock. The release binary carries no
    cargo-auditable data (no .dep-v0 section), so Trivy never saw its crates and the
    published 2.9.7 passed the gate blind. The v2.9.7 Cargo.lock, scanned with the gate's
    flags, holds 7 fixable findings, and the crate-version strings inside the binary
    confirm all 7 ship:
      hickory-resolver 0.25.2  GHSA-5j98-2g5x-46v6 HIGH, GHSA-6f2x-v7q7-m7m5 MEDIUM  (fix 0.26.2)
      hickory-proto 0.25.2     GHSA-q2qq-hmj6-3wpp MEDIUM                            (fix 0.26.1)
      rustls 0.23.40           GHSA-2mjx-qc3c-rqvc MEDIUM                            (fix 0.23.45)
      rand 0.8.5, 0.9.2        GHSA-cq8v-f236-94qc LOW                               (fix 0.8.6/0.9.3)
      xxhash-rust 0.8.15       GHSA-6g2r-675j-hx59 LOW                               (fix 0.8.16)
    Not a VEX: only three are provably absent. cargo tree on v2.9.7 resolves hickory-resolver
    to [default,serde,system-config,tokio] with no __dnssec feature, so hickory-resolver-0.25.2
    src/resolver.rs:91-104 never builds the DnssecDnsHandle (GHSA-5j98); rand has no `log`
    feature and xxhash-rust only `xxh64`. The CNAME and name-compression bugs (Deno.resolveDns,
    ext/net/ops.rs:1187-1191) and the rustls one (every fetch and TLS connection) are
    reachable in a general runtime.
    Not a source build: hickory 0.25 to 0.26 is a breaking API change (deno PR #36322, open
    and conflicting), so a cargo update cannot take it.
    UNBLOCK when a deno release pins hickory-resolver >= 0.26.2, hickory-proto >= 0.26.1 and
    rustls >= 0.23.45 (main still had 0.25.2 and 0.23.40 on 2026-10-13): add the version with
    its zip and Cargo.lock sha256s, set BLOCKED=0, dispatch. The recipe installs that
    Cargo.lock in the image, so the gate scans every crate; VEX what is left only with the
    feature evidence above.
  • gotenbergmeasured
    STATUS: BLOCKED 2026-09-26 on Wolfi's chromium. The only gate finding is
      chromium CVE-2026-13032 (CRITICAL, use after free in WebGL)
      installed 149.0.7827.53-r0, fixed in 149.0.7827.200-r0
    and Wolfi's live APKINDEX tops out at 149.0.7827.53-r0: the fix is not published.
    Everything else gates clean (gotenberg and pdfcpu from source, floated). Unblock
    when `chromium` >= 149.0.7827.200 is in the index: set BLOCKED=0, run the local
    gate, dispatch. Chromium ships CVE fixes often, so expect this app to wait on Wolfi
    again between releases.
    Re-measured 2026-09-30: Wolfi still tops out at chromium 149.0.7827.53-r0 on x86_64 and
    aarch64, so the fix is still unpublished.
    Re-measured 2026-10-01: unchanged, chromium 149.0.7827.53-r0 on both arches.
    Re-measured 2026-10-04: unchanged, chromium 149.0.7827.53-r0 on both arches, no other
    chromium package; gotenberg is still 8.37.0.
    Re-measured 2026-10-05: unchanged, chromium 149.0.7827.53-r0 on both arches.
    Re-measured 2026-10-07: unchanged, chromium 149.0.7827.53-r0 on both arches; gotenberg 8.37.0.
    Re-measured 2026-10-12: unchanged, chromium 149.0.7827.53-r0 on both arches (no other chromium
    Re-measured 2026-10-19: unchanged, Wolfi chromium still 149.0.7827.53-r0; gotenberg upstream is 8.38.1.
      package in the index); gotenberg still 8.37.0.
    2026-10-20 re-measured: Wolfi chromium still tops out at 149.0.7827.53-r0 (gotenberg 8.38.1 is out); hold unchanged.
  • jellyfinmeasured
    2026-10-12 re-check: 12.2 (2026-10-05) still pins SkiaSharp.NativeAssets.Linux 3.119.4
    (Directory.Packages.props), the same prebuilt libSkiaSharp.so; hold unchanged.
    STATUS: BLOCKED 2026-09-29 on SkiaSharp's prebuilt native library. Everything gates
    clean (0 fixable CVEs, and the boot test passes: health, version 12.1.0, first-run
    wizard, login, ffmpeg), but /usr/lib/jellyfin/libSkiaSharp.so is a 10 MB binary from
    the SkiaSharp NuGet package, built on Debian 10 with clang 13, that statically links
    its own image libraries. It embeds libjpeg-turbo 2.1.5.1 (libjpeg-turbo has shipped
    security fixes since, among them CVE-2026-75466 in 3.2.1) and libpng 1.6.58, plus
    freetype, harfbuzz, webp and zlib at versions it does not print. The scanner cannot
    see any of it, and this catalog does not ship code that hides from its own gate
    (the same class as the wheel-bundled OpenSSL found on 2026-09-28). Unblock by
    building Skia against the system libraries, or by an upstream Jellyfin that does.
    Wolfi's jellyfin apk carries the same NuGet blob.
    RE-MEASURED 2026-09-30: unchanged. Wolfi has no Skia package and jellyfin is still
    12.1-r0; upstream's latest is v12.1.
    RE-MEASURED 2026-10-01: unchanged (no Skia apk, jellyfin 12.1-r0, upstream v12.1).
    RE-MEASURED 2026-10-04: unchanged (no Skia apk, jellyfin 12.1-r0, upstream v12.1).
    RE-MEASURED 2026-10-05: unchanged (no Skia apk, jellyfin 12.1-r0 on both arches).
    RE-MEASURED 2026-10-07: jellyfin 12.2 is out (Wolfi 12.2-r0, upstream v12.2) and its apk
    still ships the same libSkiaSharp.so (libjpeg-turbo 2.1.5.1, libpng 1.6.58); no Skia apk.
    jellyfin: Jellyfin (GPL-2.0), the self-hosted media server, from Wolfi's pinned jellyfin
    and jellyfin-web apks (FROM_SOURCE=0), which build it from source on Wolfi's .NET runtime
    and system ffmpeg. Upstream ships the same version (12.1, 2026-09-15); the checker
    tracks Wolfi. NEWEST LINE ONLY: Wolfi's index still lists 10.11.x revisions, and 12.x
    is the line upstream maintains.
  • ml-metadata-store-servermeasured
    STATUS: BLOCKED 2026-10-20 on C/C++ libraries statically linked into the server, which the
    scanner cannot see. The Kubeflow Pipelines v2 driver records every execution in ML Metadata
    (backend/src/v2/cmd/driver/main.go newMlmdClient), so no KFP v2 run works without this
    server, and the kubeflow-pipelines chart is held on it too.
    Measured on Wolfi's ml-metadata-store-server 1.17.1-r0 (the only build, both arches; its
    embedded .melange.yaml is a stock `bazel build` of google/ml-metadata v1.17.1) with
    `strings` and the v1.17.1 WORKSPACE:
      sqlite 3.39.2 (2022-07-21 source id), zlib 1.2.12, gRPC 1.46.3, protobuf 3.21.9,
      mariadb-connector-c v3.0.8-release (ml_metadata/mysql_configure.bzl) and libpq from
      PostgreSQL 12.1, all compiled in by bazel http_archive / new_git_repository.
    Those carry published fixes the gate would never report (among them zlib CVE-2022-37434,
    sqlite CVE-2025-6965, connector/C CVE-2020-13249, gRPC CVE-2023-32731), the same class as
    jellyfin's SkiaSharp blob. Upstream v1.21.0 (2026-06-09, newest) still pins
    connector-c v3.0.8 and PostgreSQL 12.1 (EOL), with sqlite 3.47.2, zlib 1.3.1, gRPC 1.70.1.
    Unblock by EITHER an ml-metadata release that moves those dependencies to fixed versions,
    OR our own bazel build that links Wolfi's system zlib, sqlite-libs, mariadb-connector-c
    and libpq (new_local_repository in place of the http_archive / git repos) so they become
    scanned apks; the PostgreSQL 12.1 BUILD (1413 hand-listed sources) and the connector-c
    3.0.8 source list cannot simply be re-pointed at newer tarballs.
    The CVE gate itself passes (the scanner sees one Wolfi apk), so recheck-blocked skips it.
  • opensearch-dashboardsmeasured
    2026-10-19 re-check: no release after 3.9.0. Upstream main yarn.lock now resolves dompurify 3.4.16
    and handlebars 4.7.10 (both fixes); maplibre-gl appears in no main lockfile (core or the AD and
    observability plugins), so only the 3.10 dist can show whether the 4.5.2 bundles are gone. Hold.
    2026-10-12 re-check: 3.9.0 (GitHub release 2026-10-12) is the build measured 2026-10-11:
    still bundles DOMPurify 3.4.13 in 8 browser bundles plus maplibre-gl 4.5.2; hold unchanged.
    STATUS 2026-10-07: BLOCKED. The node_modules swaps below clear the scanner but not the
    code that runs: the browser bundles under */target/public are compiled at upstream's
    build and still carry dompurify 3.4.11/3.4.12 (8 bundles: data, discover, explore, chat,
    vis_type_table, agent_traces, reportsDashboards, investigationDashboards) and maplibre-gl
    5.2.0 (CVE-2026-85061, CRITICAL; customImportMapDashboards, observabilityDashboards,
    anomalyDetectionDashboards). Trivy reads package.json only, so the image scanned 0 while
    shipping that code. The 2026-09-26 roadmap measurement had already said so. Unblock: a
    from-source build of OSD 3.8.0 and its plugins (yarn build with the fixed versions
    resolved, bundles rebuilt), or an upstream release whose bundles carry the fixes. Check:
    grep the built image's target/public bundles for each library's version string.
    Upstream main (2026-10-07): core dompurify ^3.4.13 (yarn.lock 3.4.13, still below the 3.4.16
    LOW fix), dashboards-maps maplibre-gl 6.4.1. Dashboards 3.9.0 is unreleased (OpenSearch 3.9.0
    shipped 2026-09-29), so its release is the first upstream build to re-measure.
    Re-measured 2026-10-11 on the 3.9.0 dist (artifacts.opensearch.org, linux-x64, streamed
    and grepped in memory): dompurify 3.4.13 in the same 8 bundles (below the 3.4.16 fix) and
    maplibre-gl 4.5.2 in anomalyDetectionDashboards + observabilityDashboards (fix only in 6.x).
    3.9.0 does not unblock. Also open since 2026-10-05: core node_modules/handlebars 4.7.9
    (CVE-2026-106444/106445/106446, fixed 4.7.10), a plain swap once the bundles are fixed.
  • quickwitmeasured
    STATUS: BLOCKED 2026-10-13 on thrift 0.17.0 (CVE-2026-43868, MEDIUM, fixed only in 0.23.0).
    Measured: run 38373558044 built 0.9.1 with cargo auditable on both arches; the gate now sees
    the binary crates and its ONLY finding is thrift 0.17.0 (rustls floored to 0.23.45; rustls-webpki
    0.101.7 and rand 0.7.3 VEXed with build guards, see vex.openvex.json). thrift comes from
    parquet 58.3.0 (pins thrift "0.17") and quickwit-parquet-engine itself, whose
    src/storage/streaming_reader.rs decodes parquet page headers with thrift TCompactInputProtocol,
    the allocation path the CVE fixes: reachable, so no VEX. 0.17 -> 0.23 is API-breaking and needs
    parquet and quickwit to move. The published 0.9.1 predates auditable and is blind to this.
    UNBLOCK when a quickwit release drops thrift 0.17 (parquet 59 removes parquet::format) or
    thrift ships a 0.17.x fix: set BLOCKED=0, bump VERSIONS, dispatch; recipe is ready.
    2026-10-19 re-measured: 0.9.2 tag Cargo.lock still has parquet 58.3.0 + thrift 0.17.0, and crates.io
    has no 0.17.x fix (0.17.0 then 0.23.0). Still held; VERSIONS stays 0.9.1.
  • xwikimeasured
    STATUS: BLOCKED 2026-10-14 on Solr 9.4.1 and Jetty 10.0.26, both bundled in the XWiki WAR.
    2026-10-19 re-measured: 17.10.14 still pins solr 9.4.1 and the jetty 10.0.26 client (xwiki-commons pom); hold unchanged.
    Measured: trivy rootfs --scanners vuln --ignore-unfixed --detection-priority comprehensive on the
    extracted 17.10.13 and 18.8.0 WARs, before and after the jar swaps in melange.yaml. The swaps close
    jackson-core/databind, netty epoll, opennlp (2 CRITICAL), and on 17.10 jsoup, junrar, logback.
    Left on BOTH lines, no safe swap:
      solr-core 9.4.1: CVE-2025-24814, CVE-2026-22022, CVE-2026-22444 (HIGH), CVE-2024-52012 (MEDIUM);
        fixed in 9.8.0/9.10.1, which moves solr-* and every lucene-* 9.8.0 jar plus their transitive
        deps across six minor releases. Not a same-API swap.
      jetty-http 10.0.26: CVE-2026-2332 (HIGH), CVE-2024-6763 (MEDIUM), CVE-2025-11143 (LOW). 10.0.26 is
        the last 10.x on Maven Central; fixes exist only on 11/12. solrj 9.4 Http2SolrClient is built on
        the Jetty 10 client, and Solr CoreContainer creates it at startup, so the jars cannot be dropped.
      opennlp-tools 1.9.5: CVE-2026-42440 (HIGH), fixed only in 2.5.9 (major, via solr-analysis-extras).
    xwiki-platform master and stable-18.8.x/17.10.x still pin solr 9.4.1, lucene 9.8.0, jetty client 10.0.26.
    The recipe has not been built yet: the first dispatch after unblocking is its first CI round.
    UNBLOCK when an XWiki release ships Solr >= 9.10.1 (or 10.x) with a fixed Jetty client, then set
    BLOCKED=0, bump VERSIONS and the WAR shas, re-scan, dispatch.

Want something prioritized? Request an app and we will slot it into the roadmap.

blocked

Tested and held: cannot reach 0 fixable CVEs