3.6.7 — Security fixes
For the live, searchable view of all CVE advisories with remediation status, see the Security Advisories.
Fixes provided in 3.6.7
13 CVE(s) fixed compared to the previous release.
| Service | CVE | Severity | Package | Previously affected |
|---|---|---|---|---|
| ai-service | CVE-2026-69247 | HIGH | cryptography | 3.6.2 |
| analysis-node | CVE-2026-54291 | HIGH | postgresql | 3.6.2 |
| analysis-node | CVE-2026-62901 | HIGH | Microsoft.NETCore.App.Runtime.linux-x64 | 3.6.2 |
| auth-service | CVE-2026-54399 | HIGH | httpcore5 | 3.6.2 |
| auth-service | CVE-2026-54428 | HIGH | httpcore5-h2 | 3.6.2 |
| etl-service | CVE-2026-39821 | HIGH | stdlib | 3.6.2 |
| etl-service | CVE-2026-46600 | HIGH | stdlib | 3.6.3 |
| imaging-apis | CVE-2026-39821 | HIGH | stdlib | 3.6.6 |
| imaging-apis | CVE-2026-46600 | HIGH | stdlib | 3.6.6 |
| neo4j | CVE-2026-39821 | HIGH | stdlib | 3.6.2 |
| neo4j | CVE-2026-46600 | HIGH | stdlib | 3.6.3 |
| viewer | CVE-2026-39821 | HIGH | stdlib | 3.6.6 |
| viewer | CVE-2026-46600 | HIGH | stdlib | 3.6.6 |
Pre-existing — assessed
The following CVEs were present in this release and assessed as not requiring an immediate fix. See Security Advisories for up-to-date status.
| Service | CVE | Severity | Package | Status | Justification |
|---|---|---|---|---|---|
| extend-proxy | CVE-2024-10491 | HIGH | express | Not Affected | Version-range false positive. The authoritative advisory (GitHub Advisory Database GHSA-cm5g-3pgc-8rg4, and Snyk SNYK-JS-EXPRESS-8310337) scopes this vulnerability to express 3.0.0-alpha1 through 3.21.4 inclusive, with the fix released in express 4.0.0-rc1. The image ships express 5.2.1, which is two major versions beyond the patched release, so the vulnerable revision of the response.links implementation is not present in the product. Independently corroborated by this image’s own scan results: Trivy indexed every npm package in /opt/cast_extend_proxy/app and raised no finding against express, as did Grype. |
| extend-proxy | sonatype-2016-0121 | HIGH | multer | Not Affected | RESOLVED BY RISK ACCEPTANCE - not suppressed; residual gaps are disclosed below. multer 2.2.0 is present and on the execute path of both upload endpoints, and the underlying behaviour the advisory describes (multer consuming the full stream before enforcing a fileSize limit) is unchanged in this version - no upgrade exists or would change it, 2.2.0 is the latest published release. CAST product ownership judges the vulnerability class adequately mitigated in this product by the combination of: (1) both the primary upload endpoint (package-controller.js, POST /upload) and the bundle upload endpoint (bundle-controller.js) require a valid proxy API key, so neither is anonymously reachable; (2) the primary endpoint sets limits.fileSize to 1 GB, comfortably above the largest legitimate extension package published to date (192 MB), bounding the heap-exhaustion vector on that path; (3) custom-extension upload is a low-usage feature exercised by a small minority of customers, materially reducing real-world exposure versus a default, high-traffic endpoint. Two gaps remain open and are disclosed rather than hidden: the bundle upload endpoint (bundle-controller.js) still sets no fileSize limit of its own - it is disk-backed rather than memory-backed, so its exposure is disk consumption, not heap exhaustion; and multer’s abortWithError does not unpipe or destroy the request stream on the LIMIT_FILE_SIZE path, so bytes up to the configured cap are still read and discarded rather than the connection being torn down early. If either gap is later judged material - for example if bundle upload usage increases - this statement should be revisited. Tracked in EXTPROXY-198. |
| extend-proxy | sonatype-2019-0159 | HIGH | lunr | Not Affected | RESOLVED - same attribution conflict as sonatype-2021-1683, resolved the same way. CAST confirmed directly with Sonatype that this identifier also matches ‘mocha’, not ’lunr’. Sonatype’s own published advisory page already described this as a ReDoS in mocha (issue 3416 / PR 3686) with a matching CVSS score and vector. mocha is a devDependency removed from the runtime artifact by ’npm prune –production’; there is no node_modules/mocha in the shipped image. See the sonatype-2021-1683 statement for the full reasoning. Tracked in EXTPROXY-198. |
| extend-proxy | sonatype-2021-0078 | HIGH | express | Not Affected | Per Sonatype’s own published advisory text (guide.sonatype.com/vulnerability/sonatype-2021-0078), this is a component-combination vulnerability that requires the ‘hbs’ Handlebars templating engine to be used alongside express. Neither ‘hbs’ nor ‘handlebars’ appears in the extend-proxy dependency manifest, in package-lock.json, or anywhere in the shipped image: a path scan of the exported filesystem for node_modules/hbs and node_modules/handlebars returns no match. The proxy renders no server-side templates. The required co-component is absent, so the vulnerable combination cannot exist in this product. |
| extend-proxy | sonatype-2021-1683 | HIGH | lunr | Not Affected | RESOLVED - CAST queried Sonatype directly on the component-coordinate conflict described in the prior revision of this statement and confirmed the identifier matches ‘mocha’, not ’lunr’. Sonatype’s own published advisory page already described this as a ReDoS in mocha (issue 4766 / PR 4770) with a CVSS score and vector matching this finding exactly; the customer-supplied Nexus IQ report’s attribution to ’lunr : 2.3.9’ is a component mis-attribution in the IQ match result. mocha is declared solely in devDependencies and is removed from the runtime artifact by ’npm prune –production’: a path scan of the exported filesystem of castimaging/extend-proxy confirms there is no node_modules/mocha in the shipped image. The component the advisory defines is therefore not present in this product. Tracked in EXTPROXY-198. |
| imaging-mcp-server | CVE-2013-7445 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2019-19449 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2019-19814 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2021-3847 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2021-3864 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2024-21803 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2024-58015 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2025-22104 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2025-38137 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2025-38187 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2025-38204 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2025-38206 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2025-38421 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2025-38636 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2025-39859 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2025-39862 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2025-39958 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2025-69720 | HIGH | libncursesw6 | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-11822 | HIGH | libsqlite3-0 | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-11824 | HIGH | libsqlite3-0 | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-23102 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-23208 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-23327 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-31493 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-31536 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-31568 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-43185 | CRITICAL | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-43198 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-43263 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-46130 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-46181 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-46279 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-52991 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-53000 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-53010 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-53089 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-53091 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-53109 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| imaging-mcp-server | CVE-2026-53118 | HIGH | linux-libc-dev | OS Vendor | OS package from DHI base image. Fix depends on OS vendor (Debian security team). |
| init-util | CVE-2025-69720 | HIGH | libtinfo6 | OS Vendor | Debian NODSA. Debian Security Team does not require an immediate fix. |