critical

CVE

CVE-2026-95860, CVE-2026-112307, CVE-2026-125110, CVE-2026-125111, CVE-2026-125109, CVE-2026-125108, CVE-2026-125121, CVE-2026-125122, CVE-2026-125123, CVE-2026-125125, CVE-2026-123796, CVE-2026-123368, CVE-2026-123369, CVE-2026-123370, CVE-2026-123371, CVE-2026-123372, CVE-2026-123373, CVE-2026-102943, CVE-2026-102610, CVE-2026-87008, CVE-2026-102650, CVE-2026-115779, CVE-2026-125742, CVE-2026-124747, CVE-2026-109091, CVE-2026-109092, CVE-2026-109093, CVE-2026-109094, CVE-2026-109095, CVE-2026-109096, CVE-2026-109903, CVE-2026-109904, CVE-2026-12708

CWE

CWE-863, CWE-276, CWE-94, CWE-74, CWE-22, CWE-306, CWE-787, CWE-436, CWE-400

Affected Surface

  • npm `node-opcua`, `node-opcua-address-space`, and `node-opcua-server` versions `>= 2.42.0, < 2.180.0` (`CVE-2026-95860` / `GHSA-xggf-m53x-jc3f`, CVSS 9.1 Critical, fixed in `2.180.0`)
  • PyPI `sqlparse` versions `<= 0.6.0` (`CVE-2026-112307` / `GHSA-xmww-55xg-h3vc` CVSS 7.3 High and `GHSA-3r5h-5jcg-gmgg`, fixed in final EOL release `0.6.1`) and PyPI / GitHub Action `compose-lint` (`tmatens/compose-lint`) versions `< 0.33.0` (`CVE-2026-125121`, `CVE-2026-125122`, `CVE-2026-125123`, `CVE-2026-125125`, `CVE-2026-123796`, `CVE-2026-123368` through `CVE-2026-123373`)
  • RubyGems `rack` versions `< 2.2.25`, `>= 3.0.0, < 3.1.23`, and `>= 3.2.0, < 3.2.8` (`CVE-2026-125111` / `GHSA-5v64-555j-wjxm` High multipart scan-buffer DoS, `CVE-2026-125109` / `GHSA-2j8w-xcrc-x985` Medium `host_with_port` incomplete fix for `CVE-2026-34835`, `CVE-2026-125110` / `GHSA-wvg4-6p58-3gh3`, and `CVE-2026-125108` / `GHSA-p8x9-v4hv-2w4g`), npm `@nuxt/content` versions `>= 3.0.0, < 3.15.2` (`CVE-2026-102650` / `GHSA-xxrh-5hgg-gj4h`, CVSS 7.5 High), and npm `@effect/platform` `< 0.97.1` / `effect` `< 4.0.0-beta.103` (`CVE-2026-115779` / `GHSA-chp3-j5qr-2vfr`)
  • Go `github.com/dagu-org/dagu/v2` versions `<= 2.10.7` (`CVE-2026-102943` / `GHSA-5m6c-38r8-5w76`), PyPI `fast-agent-mcp` versions `<= 0.7.20` (`CVE-2026-102610` / `GHSA-9vhv-g5hf-m7m7`), and PyPI `code-graph-rag` versions `<= 0.0.586` (`CVE-2026-87008` / `GHSA-85gg-2gfq-q95m`)
  • 7-Zip (`ip7z/7zip`) versions `< 26.06` (`CVE-2026-125742`, CVSS 7.8 High), BusyBox `wget` (`CVE-2026-124747`, CVSS 7.5 High), X.Org Server `< 21.1.26` and Xwayland `< 24.1.15` (`CVE-2026-109091` through `CVE-2026-109096`, `CVE-2026-109903`, `CVE-2026-109904`), and crates.io `tokio-quiche` `< 0.23.0` (`CVE-2026-12708` / `GHSA-wcm9-jv39-r963`, CVSS 8.7 High)

Update, 11 November 2026 (three additional Rack 2.2.25 / 3.1.23 / 3.2.8 advisories and three compose-lint 0.32.0 advisories): Between 19:11 and 21:58 UTC on 10 November 2026, the GitHub Advisory Database published six additional advisories for rack and compose-lint:

  • Rack 2.2.25, 3.1.23, and 3.2.8 (CVE-2026-125111 High, CVE-2026-125109 Medium, and CVE-2026-125108 Low): Alongside CVE-2026-125110, the new Rack releases fix an unbounded scan-buffer growth DoS during multipart parsing (CVE-2026-125111 / GHSA-5v64-555j-wjxm), an incomplete fix for CVE-2026-34835 where Rack::Request#host_with_port (and #base_url / #url) returned the raw unvalidated Host header in Rack 3.0.x < 3.1.23 and 3.2.x < 3.2.8 (CVE-2026-125109 / GHSA-2j8w-xcrc-x985), and a Rack::Multipart::Parser boundary ambiguity bypass via quoted boundary values (CVE-2026-125108 / GHSA-p8x9-v4hv-2w4g).
  • compose-lint 0.32.0 (CVE-2026-125122, CVE-2026-125123, and CVE-2026-125125): Three companion advisories detail how compose-lint 0.31.0 still permitted GitHub Actions workflow command injection through --format json and --format sarif on stdout (CVE-2026-125122 / GHSA-hr4h-4c45-v4q4), CLI file-path error messages (CVE-2026-125123 / GHSA-8v59-qmwv-4p6q), and SARIF output-directory symlink errors (CVE-2026-125125 / GHSA-xcf7-88g6-7xr8).

TL;DR

On 10 November 2026 (12:17 to 18:50 UTC), NVD, oss-security, and the GitHub Advisory Database published a second wave of disclosures affecting industrial Node.js servers, Python SQL parsers, GitHub Actions linters, Ruby Rack middleware, Model Context Protocol (MCP) agent tooling, and archive extractors:

  1. node-opcua < 2.180.0 namespace-level RBAC fail-open (CVE-2026-95860 / GHSA-xggf-m53x-jc3f, CVSS 9.1 Critical): In node-opcua 2.42.0 through 2.179.0, namespace.setDefaultRolePermissions() stored configured role permissions on a private field (namespace._defaultRolePermissions), whereas SessionContext.checkPermission() looked up the DefaultRolePermissions child variable on the Server/Namespaces metadata node in the address space. Because programmatic namespaces lack that metadata node unless setNamespaceMetaData() is also called, the lookup returned null and fell back to PermissionFlag.All, granting unauthenticated (Anonymous) OPC UA clients Write and Call permissions on every node without explicit per-node RolePermissions. Fixed in node-opcua 2.180.0 (2.187.26 is current on npm).
  2. sqlparse 0.6.1 patches PHP output code injection (CVE-2026-112307, CVSS 7.3 High) and quadratic format() DoS (GHSA-3r5h-5jcg-gmgg), and announces end-of-life (oss-security 2026/11/10/20): OutputPHPFilter (sqlparse.format(sql, output_format='php')) escaped backslashes and double quotes when emitting $sql = "..."; statements, but did not escape $. Any SQL input containing ${expr} or {$expr} executed arbitrary PHP code when the generated snippet was evaluated. Release 0.6.1 also replaces the quadratic SPLIT_REGEX in split_unquoted_newlines() with a linear scanner, prevents sqlformat --in-place from truncating files on parse errors, and marks the final release of sqlparse as the maintainer steps down due to unsustainable automated vulnerability report volume.
  3. compose-lint (tmatens/compose-lint) < 0.33.0 GitHub Actions workflow-command injection and .env symlink secret leaks (CVE-2026-125121, CVE-2026-123796, CVE-2026-123368 through CVE-2026-123373): Seven advisories show how a Docker Compose linter running in GitHub Actions can be turned against the runner: 0.30.0 printed unescaped ##[command] and ::command:: strings from untrusted Compose files (CVE-2026-123369) and followed .env symlinks to /proc/self/environ (CVE-2026-123368); 0.31.0’s fix for workflow commands only checked ASCII spaces/tabs before ::, whereas the Actions runner’s .TrimStart() strips Unicode whitespace such as U+00A0 (CVE-2026-125121); and 0.32.0’s fix for .env variable quoting checked the 20,000-finding limit (FindingLimitError) before redacting resolved .env values back to ${NAME} (CVE-2026-123796). Fixed in compose-lint 0.33.0 (1.2.0 is current on PyPI).
  4. Ruby rack 2.2.25 / 3.1.23 / 3.2.8 Rack::Static header_rules bypass (CVE-2026-125110), @nuxt/content 3.15.2 SQLite randomblob() DoS (CVE-2026-102650), and @effect/platform 0.97.1 cookie attribute injection (CVE-2026-115779): Rack::Static normalized the file path with Utils.clean_path_info(Utils.unescape_path(path)) before serving the file, but matched header_rules against Utils.unescape_path(path) without collapsing dot segments, letting requests like /css/../admin/secret.html fetch static files without their configured security headers. @nuxt/content < 3.15.2 allowed arbitrary SQLite function calls (randomblob(100000000), zeroblob(500000000)) inside the WHERE clause of POST /__nuxt_content/:collection/query, and @effect/platform < 0.97.1 permitted ; inside makeCookie() name, domain, and path fields.
  5. MCP agent tooling (Dagu 2.11.0 CVE-2026-102943, fast-agent-mcp 0.7.21 CVE-2026-102610, code-graph-rag 0.0.587 CVE-2026-87008), 7-Zip 26.06 (CVE-2026-125742), X.Org Server 21.1.26 (CVE-2026-109091..109904), and tokio-quiche 0.23.0 (CVE-2026-12708): Dagu’s MCP dagu_read tool called the DAG store directly in-process, bypassing the HTTP middleware added for CVE-2026-33344; fast-agent serve --shell bound 0.0.0.0:8000 with auth=None; code-graph-rag’s AstGrepService (structural_search / structural_replace) checked path containment lexically without resolving symlinks; and 7-Zip < 26.06 failed to reset _pos = 0 in LzxDecoder.cpp when a continuation .cab volume shrunk the LZX dictionary window.

What to do now: Upgrade node-opcua packages to >= 2.180.0 (2.187.26), sqlparse to 0.6.1, compose-lint to >= 0.33.0 (1.2.0), rack to >= 3.2.8 (3.1.23 / 2.2.25), dagu to >= 2.11.0, fast-agent-mcp to >= 0.7.21 (0.10.53), code-graph-rag to >= 0.0.589 (0.6.30), @nuxt/content to >= 3.15.2 (3.16.2), @effect/platform to >= 0.97.1, 7-Zip to >= 26.06, xorg-server to >= 21.1.26 (xwayland >= 24.1.15), and tokio-quiche to >= 0.23.0.

Affected packages and components

EcosystemPackage / ProjectCVE / GHSASeverityAffected versionsFixed version
npmnode-opcua, node-opcua-address-space, node-opcua-serverCVE-2026-95860 (GHSA-xggf-m53x-jc3f)CVSS 9.1 Critical>= 2.42.0, < 2.180.02.180.0 (2.187.26)
PyPIsqlparse (andialbrecht/sqlparse)CVE-2026-112307 (GHSA-xmww-55xg-h3vc), GHSA-3r5h-5jcg-gmggCVSS 7.3 High / Moderate<= 0.6.00.6.1 (final EOL release)
PyPI / GitHub Actionscompose-lint (tmatens/compose-lint)CVE-2026-125121 (GHSA-r7j4-crjv-h467), CVE-2026-123796 (GHSA-rm8w-w798-g545), CVE-2026-123368..123373Medium / Low< 0.33.00.33.0 (1.2.0)
RubyGemsrack (rack/rack)CVE-2026-125110 (GHSA-wvg4-6p58-3gh3)CVSS 5.3 Medium< 2.2.25, >= 3.0.0, < 3.1.23, >= 3.2.0, < 3.2.82.2.25, 3.1.23, 3.2.8
Gogithub.com/dagu-org/dagu/v2CVE-2026-102943 (GHSA-5m6c-38r8-5w76, incomplete fix for CVE-2026-33344)CVSS 6.5 Medium<= 2.10.72.11.0
PyPIfast-agent-mcp (evalstate/fast-agent)CVE-2026-102610 (GHSA-9vhv-g5hf-m7m7)CVSS 6.4 Medium (RCE with --shell)<= 0.7.200.7.21 (0.10.53)
PyPIcode-graph-rag (vitali87/code-graph-rag)CVE-2026-87008 (GHSA-85gg-2gfq-q95m)CVSS 7.1 High<= 0.0.5860.0.587 / 0.0.589 (0.6.30)
npm@nuxt/content (nuxt/content)CVE-2026-102650 (GHSA-xxrh-5hgg-gj4h)CVSS 7.5 High>= 3.0.0, < 3.15.23.15.2 (3.16.2)
npm@effect/platform, effect (Effect-TS/effect)CVE-2026-115779 (GHSA-chp3-j5qr-2vfr)CVSS 6.3 Medium@effect/platform >= 0.1.0, < 0.97.1; effect >= 4.0.0-beta.0, < 4.0.0-beta.1030.97.1, 4.0.0-beta.103 (4.1.3)
C++ / Binary7-Zip (ip7z/7zip) and BusyBox wgetCVE-2026-125742 (7-Zip); CVE-2026-124747 (BusyBox)CVSS 7.8 High / 7.5 High7-Zip < 26.067-Zip 26.06 (commit d3296e39e1f1)
C / LinuxX.Org Server (xorg-server), Xwayland, and crates.io/tokio-quicheCVE-2026-109091..109096, CVE-2026-109903, CVE-2026-109904; CVE-2026-12708 (GHSA-wcm9-jv39-r963)High (8.7 for tokio-quiche)xorg-server < 21.1.26, xwayland < 24.1.15; tokio-quiche < 0.23.0xorg-server 21.1.26, xwayland 24.1.15; tokio-quiche 0.23.0

Technical analysis

1. node-opcua 2.180.0 (CVE-2026-95860): how setDefaultRolePermissions() was ignored by SessionContext.checkPermission()

Under the OPC UA specification (Part 3, §5.2.9 and §4.8.3), any node that does not define its own RolePermissions attribute inherits the DefaultRolePermissions of its owning namespace, and permission evaluation must default to deny (Bad_UserAccessDenied) when an operation bit is not explicitly granted.

In node-opcua 2.42.0 through 2.179.0, two implementation bugs combined in packages/node-opcua-address-space/source/session_context.ts:

  1. Disconnected storage between Namespace.setDefaultRolePermissions() and SessionContext: Calling namespace.setDefaultRolePermissions(roles) wrote to an internal field (namespace._defaultRolePermissions), which BaseNode.getRolePermissions(inherited=true) read. However, during actual request enforcement, SessionContext.checkPermission() called getDefaultRolePermissionsOnNamespace(), which ignored namespace.getDefaultRolePermissions() and instead walked the OPC UA address space (Server/Namespaces/<uri>/DefaultRolePermissions).
  2. Fail-open fallback (PermissionFlag.All): For any programmatically created namespace where the developer did not separately create a NamespaceMetadata node via setNamespaceMetaData(), getDefaultRolePermissionsOnNamespace() returned null. Even when a NamespaceMetadata node existed via ServerEngine.initialize(), server_engine.ts overwrote its value on startup. When both per-node and namespace permissions resolved to null, checkPermission() returned true (PermissionFlag.All), allowing an unauthenticated Anonymous client to write variables and invoke methods in that namespace.

Commit 0261e8739008 (PR #1580) consults namespace.getDefaultRolePermissions() inside getDefaultRolePermissionsOnNamespace() whenever the address-space NamespaceMetadata property is absent or null, and stops ServerEngine.initialize() from clobbering pre-populated DefaultRolePermissions values.

2. sqlparse 0.6.1 (CVE-2026-112307 and GHSA-3r5h-5jcg-gmgg): PHP $var / ${expr} code injection and EOL

When sqlparse.format(sql, output_format='php') converts SQL into PHP source code, OutputPHPFilter._process() in sqlparse/filters/output.py wraps each line of SQL inside a double-quoted PHP string ($sql = "...";). After an earlier advisory (GHSA-3496-9g83-7v6x) added backslashescaping before double quotes, the filter still left $ untouched (commit bb3c50a52dc2):

--- a/sqlparse/filters/output.py
+++ b/sqlparse/filters/output.py
@@ -115,9 +115,13 @@ def _process(self, stream, varname, has_nl):
-            else:
-                token.value = token.value.replace('\\', '\\\\').replace('"', '\\"')
+            # (GHSA-3496-9g83-7v6x). Dollar signs are escaped last because
+            # PHP interpolates $var, ${expr} and {$expr} inside double-quoted
+            # strings (CVE-2026-112307).
+            else:
+                token.value = (token.value.replace('\\', '\\\\')
+                               .replace('"', '\\"')
+                               .replace('$', '\\$'))

Because PHP interpolates $var, ${expr}, and {${expr}} inside double-quoted strings, passing untrusted SQL such as SELECT '{${system($_GET[cmd])}}' into sqlparse.format(..., output_format='php') produced a PHP snippet that executed arbitrary code as soon as the generated PHP file ran. Commit be3b7a68d07a (GHSA-3r5h-5jcg-gmgg) also replaces the regex in sqlparse/utils.py (split_unquoted_newlines()) that rescanned to the end of the string on every unclosed quote ("\\ repeated 20,000 times). Alongside 0.6.1, maintainer Andi Albrecht announced that 0.6.1 is the final release of sqlparse (discussions/945), citing the unsustainable volume of automated vulnerability reports.

3. compose-lint 0.33.0 (CVE-2026-125121, CVE-2026-123796, CVE-2026-123368..123373): CI workflow command injection and .env secret leaks

Seven advisories in tmatens/compose-lint illustrate the subtleties of running a static linter inside GitHub Actions on untrusted pull requests:

  1. Workflow command openers (##[ and Unicode-indented ::, CVE-2026-123369 and CVE-2026-125121): GitHub Actions and Azure Pipelines parse ##[command] anywhere in a log line and ::command:: at the start of a line after .TrimStart(). After 0.31.0 (CVE-2026-123369) escaped :: following ASCII spaces and tabs, 0.32.0 (CVE-2026-125121, commit 542e63126f79) had to close five remaining bypasses: leading Unicode whitespace (such as U+00A0 NO-BREAK SPACE) before ::, Unicode LINE SEPARATOR (U+2028) and PARAGRAPH SEPARATOR (U+2029), find stderr messages outside the ::stop-commands:: window in action.yml, and raw exception messages in CLI stderr.
  2. Symlinked .env reads and the 20,000-finding cap (CVE-2026-123368, CVE-2026-123372, and CVE-2026-123796): Prior to 0.31.0, compose-lint resolved ${VAR} from a sibling .env file without checking if .env was a symlink (CVE-2026-123368, allowing a PR to symlink .env -> /proc/self/environ) and quoted resolved .env values inside CL-0004 / CL-0019 image: findings (CVE-2026-123372). Version 0.32.0 redacted resolved .env values back to ${NAME} in run_rules(), but raised FindingLimitError(findings) when a file exceeded MAX_FINDINGS = 20,000 before calling _quote_references() (commit 31ec460399e0, CVE-2026-123796).

4. Rack 3.2.8 (CVE-2026-125110), Dagu 2.11.0 (CVE-2026-102943), fast-agent-mcp 0.7.21 (CVE-2026-102610), code-graph-rag (CVE-2026-87008), @nuxt/content (CVE-2026-102650), @effect/platform (CVE-2026-115779), and 7-Zip 26.06 (CVE-2026-125742)

  • Rack::Static header_rules dot-segment mismatch (CVE-2026-125110 / GHSA-wvg4-6p58-3gh3, commit 18a07fe553af): In lib/rack/static.rb, Rack::Static#call resolved the file to serve using Utils.clean_path_info(Utils.unescape_path(path)), but applicable_rules(path) only ran Utils.unescape_path(path):
    --- a/lib/rack/static.rb
    +++ b/lib/rack/static.rb
    @@ -168,7 +168,7 @@ def call(env)
         # Convert HTTP header rules to HTTP headers
         def applicable_rules(path)
    -      path = ::Rack::Utils.unescape_path(path)
    +      path = ::Rack::Utils.clean_path_info(::Rack::Utils.unescape_path(path))
    When an application configured path-specific security headers (such as X-Frame-Options, Content-Security-Policy, or Cache-Control: no-store on /admin/), requesting /css/../admin/secret.html or /%2e%2e/admin/secret.html served /admin/secret.html while skipping the /admin/ rule.
  • MCP path-containment and network-binding flaws (Dagu CVE-2026-102943, fast-agent-mcp CVE-2026-102610, and code-graph-rag CVE-2026-87008):
    • In Dagu (<= 2.10.7, commit c15c5406bb7b), the fix for CVE-2026-33344 validated FileName inside a chi HTTP middleware, while the MCP dagu_read tool (target: "dag_spec") invoked dagStore.GetSpec() in-process where searchPaths included "." and accepted relative traversal paths to read arbitrary .yaml/.yml files on the host.
    • In fast-agent-mcp (<= 0.7.20, GHSA-9vhv-g5hf-m7m7), running fast-agent serve --shell (or uvx fast-agent mcp@latest -x from the README quickstart) bound the HTTP MCP server to 0.0.0.0:8000 with auth=None, exposing the execute shell tool to any network client.
    • In code-graph-rag (<= 0.0.586, commit 2648c95aa550), should_skip_path() in codebase_rag/utils/path_utils.py checked path containment lexically without calling path.resolve().relative_to(repo_path.resolve()), allowing a symlink inside an analyzed repository to read or overwrite (structural_replace(dry_run=False)) arbitrary files outside the workspace.
  • @nuxt/content 3.15.2 (CVE-2026-102650, commit 847d523a48e7) and @effect/platform 0.97.1 (CVE-2026-115779, commit 4a57af24011d): In @nuxt/content 3.0.0 to 3.15.1, assertSafeQuery() in src/runtime/internal/security.ts blocked subqueries (SELECT|INSERT|...) in POST /__nuxt_content/:collection/query, but allowed SQLite functions inside WHERE clauses (WHERE (length(hex(randomblob(100000000))) > 0)), letting a single unauthenticated POST allocate hundreds of megabytes in SQLite. Version 3.15.2 rejects any SQL_FUNCTION_CALL (/(?:\b[A-Z_]\w*|["[][A-Z_]\w*[“\]])\s*\(/i) in WHERE clauses. In @effect/platform, makeCookie() validated name, domain, and path with fieldContentRegExp (/^[\u0009\u0020-\u007e\u0080-\u00ff]+$/), which permitted ; (0x3b), allowing untrusted domain or path values to inject ; Domain=.parent.tld or ; SameSite=None attributes into Set-Cookie.
  • 7-Zip 26.06 multi-volume CAB LZX window shrink heap overflow (CVE-2026-125742, commit d3296e39e1f1): In CPP/7zip/Compress/LzxDecoder.cpp, CDecoder::Set_DictBits_and_Alloc(unsigned numDictBits) freed and reallocated _win whenever a continuation .cab volume specified a smaller numDictBits than the previous volume, but did not reset _pos = 0 or _overDict = false:
    --- a/CPP/7zip/Compress/LzxDecoder.cpp
    +++ b/CPP/7zip/Compress/LzxDecoder.cpp
    @@ -1499,6 +1501,8 @@ HRESULT CDecoder::Set_DictBits_and_Alloc(unsigned numDictBits) throw()
           z7_AlignedFree
             (_win);
           _winSize = 0;
    +      _pos = 0;
    +      _overDict = false;
           const size_t alloc_size = newWinSize + k_OutBufSize_Add;
    When _pos from the first volume was already larger than the new smaller _winSize, subsequent decompression wrote directly past the end of the newly allocated _win heap buffer.

Detection and remediation

# 1. Check npm lockfiles and manifests for node-opcua, @nuxt/content, and @effect/platform / effect
npm ls node-opcua node-opcua-address-space node-opcua-server @nuxt/content @effect/platform effect 2>/dev/null || true
rg -n '"(node-opcua|node-opcua-address-space|node-opcua-server|@nuxt/content|@effect/platform|effect)"' \
  package.json package-lock.json pnpm-lock.yaml yarn.lock 2>/dev/null

# 2. Check Python, Ruby, Go, and Rust manifests for sqlparse, compose-lint, fast-agent-mcp, code-graph-rag, rack, dagu, and tokio-quiche
pip show sqlparse compose-lint fast-agent-mcp code-graph-rag 2>/dev/null || true
rg -n 'sqlparse|compose-lint|fast-agent-mcp|code-graph-rag|rack|dagu-org/dagu|tokio-quiche' \
  pyproject.toml requirements*.txt uv.lock Gemfile* go.mod Cargo.lock .github/workflows/*.yml 2>/dev/null

# 3. Audit Python codebases for sqlparse PHP output formatting (CVE-2026-112307) and check 7-Zip / Xorg versions
rg -n "output_format\s*=\s*['\"]php['\"]" --glob '*.py' 2>/dev/null
7z | head -n 3 2>/dev/null || true
Xorg -version 2>&1 | head -n 3 || true
  1. Upgrade node-opcua to >= 2.180.0 (2.187.26): Verify that any custom namespaces using namespace.setDefaultRolePermissions() deny anonymous writes (Bad_UserAccessDenied) on nodes without explicit RolePermissions.
  2. Upgrade sqlparse to 0.6.1 and plan migration off EOL sqlparse: Because 0.6.1 is the final release of sqlparse, audit callers of sqlparse.format() (especially any code using output_format='php' or passing untrusted SQL strings without length limits).
  3. Upgrade compose-lint to >= 0.33.0 (1.2.0), rack to >= 3.2.8 (3.1.23 / 2.2.25), dagu to >= 2.11.0, fast-agent-mcp to >= 0.7.21, code-graph-rag to >= 0.0.589, @nuxt/content to >= 3.15.2, @effect/platform to >= 0.97.1, and 7-Zip to >= 26.06: If compose-lint <= 0.32.0 ran on pull requests in workflows that populated a sibling .env file with secrets, rotate those CI secrets.

Timeline

  • 2026-10-20 to 2026-11-01: sqlparse commits bb3c50a52dc2 (CVE-2026-112307) and be3b7a68d07a (GHSA-3r5h-5jcg-gmgg) and tags its final EOL release 0.6.1 (2026-11-01).
  • 2026-11-06: Igor Pavlov releases 7-Zip 26.06 (d3296e39e1f1) fixing the LZX continuation-volume window shrink heap overflow (CVE-2026-125742).
  • 2026-11-09 (22:01 UTC): fast-agent-mcp publishes GHSA-9vhv-g5hf-m7m7 (CVE-2026-102610) and code-graph-rag publishes GHSA-85gg-2gfq-q95m (CVE-2026-87008).
  • 2026-11-10 (12:17 to 18:50 UTC): NVD, oss-security, and GitHub publish CVE-2026-95860 (node-opcua 2.180.0), CVE-2026-112307 (sqlparse 0.6.1 EOL announcement on oss-security 2026/11/10/20), CVE-2026-125110 (rack 2.2.25 / 3.1.23 / 3.2.8), the seven compose-lint advisories (CVE-2026-125121, CVE-2026-123796, CVE-2026-123368..123373), CVE-2026-102943 (dagu 2.11.0), CVE-2026-102650 (@nuxt/content 3.15.2), CVE-2026-115779 (@effect/platform 0.97.1), CVE-2026-125742 (7-Zip 26.06), CVE-2026-12708 (tokio-quiche 0.23.0), and the 8-CVE X.Org Server 21.1.26 / xwayland 24.1.15 advisory (oss-security 2026/11/10/13).

From research to remediation

Check whether this pattern exists in your codebase

Turn this research into a remediation workflow. Scan dependencies and package manifests for similar supply-chain risk, then prioritize fixes with reachability context.

References