{
  "document": {
    "aggregate_severity": {
      "text": "Low"
    },
    "category": "csaf_security_advisory",
    "csaf_version": "2.0",
    "distribution": {
      "text": "TuxCare License Agreement",
      "tlp": {
        "label": "WHITE",
        "url": "https://www.first.org/tlp/"
      }
    },
    "lang": "en",
    "notes": [
      {
        "category": "legal_disclaimer",
        "text": "This content is licensed under the Creative Commons Attribution 4.0 International License (https://creativecommons.org/licenses/by/4.0/). If you distribute this content, or a modified version of it, you must provide attribution to Cloud Linux Inc. and provide a link to the original.",
        "title": "Terms of Use"
      },
      {
        "category": "details",
        "text": "* SECURITY UPDATE: HTTP/2 headers of a removed stream outlive their session --\n     RemoveStream() erased the stream without releasing current_headers_, and the\n     session destructor loop can no longer see a removed stream, so a stream kept\n     alive by a pending socket write outlived the session with nghttp2 rcbufs\n     still referenced and tripped CHECK_EQ(current_nghttp2_memory_, 0)\n     (CVE-2026-123863)\n     - debian/patches/CVE-2026-123863.patch: call stream->ClearHeaders() in\n       RemoveStream() immediately after streams_.erase(), before the accounting\n   * SECURITY UPDATE: nested HTTP parser execution from empty writes -- the\n     empty-write branch of TLSWrap::DoWrite() called ClearOut() unguarded, and\n     Parser::Execute() reset current_buffer_* to null instead of restoring the\n     caller's, with no bounds check on data callbacks (CVE-2026-123864)\n     - debian/patches/CVE-2026-123864.patch: gate ClearOut() on cycle_depth_ == 0,\n       save/restore the outer buffer, and reject out-of-buffer data with HPE_USER\n   * SECURITY UPDATE: HTTP/2 streams abandoned by nghttp2 are never cleaned up --\n     a peer GOAWAY(NO_ERROR) sets graceful close first, so a later internal\n     nghttp2 termination never set internal_goaway_sent_ and SendPendingData()\n     never errored the still-open streams, hanging the stream and socket\n     (CVE-2026-123865)\n     - debian/patches/CVE-2026-123865.patch: add HasStreamsAbandonedByNghttp2()\n       and consider it in SendPendingData()\n   * SECURITY UPDATE: HTTP/2 write buffers released while the socket write is in\n     flight -- OnSendData() pushed a partial slice holding no reference to the\n     originating write request, and DoWrite() attached req_wrap to the last writev\n     buffer only, so destroying a stream mid-write freed memory libuv was still\n     reading and disclosed it across streams (CVE-2026-123866)\n     - debian/patches/CVE-2026-123866.patch: add a non-completing buffer_owner\n       reference to NgHttp2StreamWrite and propagate it to every slice\n   * SECURITY UPDATE: HTTP/2 stream freed while writes are pending --\n     HasWritesOnSocketForStream() matched only entries carrying a req_wrap, which\n     is set on the last writev entry only, so Http2Stream::Destroy() detached the\n     stream while its DATA slices were still queued, a use-after-free reachable by\n     cancelling a respondWithFile() download (CVE-2026-123874)\n     - debian/patches/CVE-2026-123874.patch: retain the Http2Stream on every\n       outgoing entry and test that reference instead of req_wrap\n   * SECURITY UPDATE: TLS session resumption and renegotiation could change the\n     SNI name -- sessions were never bound to the server name they were issued\n     for, the SNI context was re-selected on every ClientHello so renegotiation or\n     a TLS1.3 HelloRetryRequest could swap credentials mid-connection, and mutual\n     TLS without a session id context allowed resumption to bypass client\n     certificate verification (CVE-2026-123872)\n     - debian/patches/CVE-2026-123872.patch: bind sessions to the server name, pin\n       the name for the life of the connection, and disable resumption for mTLS\n       with no session id context\n     - NOTE: the server now always answers the servername callback with\n       SSL_TLSEXT_ERR_OK, so an empty server_name extension is echoed by every\n       TLS server on this build, and a renegotiation or HelloRetryRequest that\n       changes or drops SNI is now rejected with illegal_parameter\n   * SECURITY UPDATE: the CA of an SNI context without a certificate was ignored\n     -- UseSNIContext() returns false for a certificate-less SecureContext, which\n     short-circuited SetCACerts(), so a context added with server.addContext(host,\n     {ca}) never installed its verify store or client CA list and clients for that\n     host were verified against the default context's CA (CVE-2026-123867)\n     - debian/patches/CVE-2026-123867.patch: track whether a context carries its\n       own CA and apply it even when the context has no certificate\n   * SECURITY UPDATE: inbound HTTP/2 DATA retained by undrained streams was not\n     charged against maxSessionMemory, so a peer could make a session retain\n     memory in proportion to the number of frames rather than the bytes sent\n     (CVE-2026-123868)\n     - debian/patches/CVE-2026-123868.patch: charge each retained chunk against\n       maxSessionMemory, release it on resume or destroy, and stop reading from\n       the socket while the session is over budget\n   * SECURITY UPDATE: ALTSVC frame buffers overflowed by one byte -- the scratch\n     buffers were sized at the exact string length while String::WriteOneByte()\n     null-terminates by default, writing one byte past a heap allocation for\n     origins or values longer than the 1024-byte stack buffer (CVE-2026-123828)\n     - debian/patches/CVE-2026-123828.patch: pass an explicit length and\n       String::NO_NULL_TERMINATION, as the sibling ORIGIN path already does\n   * SECURITY UPDATE: null write request on a cancelled HTTP/2 stream --\n     ReportWritesToJSStreamListener::OnStreamAfterReqFinished() dereferenced the\n     stream and the write request without checking either, and the synchronous\n     write branch of StreamPipe passes a null request (CVE-2026-123875)\n     - debian/patches/CVE-2026-123875.patch: return early when either is null\n   * SECURITY UPDATE: https.Agent pooled sockets across different TLS trust\n     policies -- getName() omitted secureContext, allowPartialTrustChain,\n     ALPNProtocols, minDHSize, pskCallback, requestOCSP and session, so a socket\n     negotiated under one trust policy could serve a request issued under another\n     (CVE-2026-123877)\n     - debian/patches/CVE-2026-123877.patch: include those options in the pool key\n   * SECURITY UPDATE: recursive fs.watch() leaked the names of denied descendants\n     -- FSEventWrap::OnEvent() passed the filename reported by libuv straight to\n     JavaScript, the permission model being consulted only once when the watch was\n     started (CVE-2026-123829)\n     - debian/patches/CVE-2026-123829.patch: re-check kFileSystemRead for the\n       reported path before delivering the event\n   * SECURITY UPDATE: zlib params() callback after destroy --\n     paramsAfterFlushCallback() asserted on the native handle, so destroying a\n     stream whose params() flush was still queued raised ERR_INTERNAL_ASSERTION\n     from a write callback and aborted the process (CVE-2026-123862)\n     - debian/patches/CVE-2026-123862.patch: propagate the write error to the\n       user callback instead of touching the closed handle",
        "title": "Details"
      }
    ],
    "publisher": {
      "category": "vendor",
      "contact_details": "https://tuxcare.com/contact/",
      "name": "TuxCare",
      "namespace": "https://tuxcare.com/"
    },
    "references": [
      {
        "category": "self",
        "summary": "https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366",
        "url": "https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366"
      },
      {
        "category": "self",
        "summary": "Canonical URL",
        "url": "https://security.tuxcare.com/csaf/v2/els_alt_nodejs/debian10/advisories/2026/clsa-2026_1794435366.json"
      }
    ],
    "tracking": {
      "current_release_date": "2026-11-11T22:17:19Z",
      "generator": {
        "date": "2026-11-11T22:17:19Z",
        "engine": {
          "name": "pyCSAF"
        }
      },
      "id": "CLSA-2026:1794435366",
      "initial_release_date": "2026-11-11T22:17:19Z",
      "revision_history": [
        {
          "date": "2026-11-11T22:17:19Z",
          "number": "1",
          "summary": "Initial version"
        }
      ],
      "status": "final",
      "version": "1"
    },
    "title": "Fix of 13 CVEs"
  },
  "product_tree": {
    "branches": [
      {
        "branches": [
          {
            "branches": [
              {
                "category": "product_name",
                "name": "Debian 10",
                "product": {
                  "name": "Debian 10",
                  "product_id": "Debian-10",
                  "product_identification_helper": {
                    "cpe": "cpe:2.3:o:debian:debian_linux:10:*:*:*:*:*:*:*"
                  }
                }
              }
            ],
            "category": "product_family",
            "name": "Debian"
          }
        ],
        "category": "vendor",
        "name": "Software in the Public Interest, Inc."
      },
      {
        "branches": [
          {
            "branches": [
              {
                "category": "product_version",
                "name": "alt-nodejs20-nodejs-0:20.20.2-15.amd64",
                "product": {
                  "name": "alt-nodejs20-nodejs-0:20.20.2-15.amd64",
                  "product_id": "alt-nodejs20-nodejs-0:20.20.2-15.amd64",
                  "product_identification_helper": {
                    "purl": "pkg:deb/tuxcare/alt-nodejs20-nodejs@20.20.2-15?arch=amd64&os_name=debian&os_version=10"
                  }
                }
              },
              {
                "category": "product_version",
                "name": "alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64",
                "product": {
                  "name": "alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64",
                  "product_id": "alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64",
                  "product_identification_helper": {
                    "purl": "pkg:deb/tuxcare/alt-nodejs20-npm@10.8.2-20.20.2-15?arch=amd64&os_name=debian&os_version=10"
                  }
                }
              },
              {
                "category": "product_version",
                "name": "alt-nodejs20-docs-0:20.20.2-15.amd64",
                "product": {
                  "name": "alt-nodejs20-docs-0:20.20.2-15.amd64",
                  "product_id": "alt-nodejs20-docs-0:20.20.2-15.amd64",
                  "product_identification_helper": {
                    "purl": "pkg:deb/tuxcare/alt-nodejs20-docs@20.20.2-15?arch=amd64&os_name=debian&os_version=10"
                  }
                }
              },
              {
                "category": "product_version",
                "name": "alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
                "product": {
                  "name": "alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
                  "product_id": "alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
                  "product_identification_helper": {
                    "purl": "pkg:deb/tuxcare/alt-nodejs20-nodejs-devel@20.20.2-15?arch=amd64&os_name=debian&os_version=10"
                  }
                }
              }
            ],
            "category": "architecture",
            "name": "amd64"
          }
        ],
        "category": "vendor",
        "name": "TuxCare"
      }
    ],
    "relationships": [
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "alt-nodejs20-nodejs-0:20.20.2-15.amd64 as a component of Debian 10",
          "product_id": "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64"
        },
        "product_reference": "alt-nodejs20-nodejs-0:20.20.2-15.amd64",
        "relates_to_product_reference": "Debian-10"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64 as a component of Debian 10",
          "product_id": "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
        },
        "product_reference": "alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64",
        "relates_to_product_reference": "Debian-10"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "alt-nodejs20-docs-0:20.20.2-15.amd64 as a component of Debian 10",
          "product_id": "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64"
        },
        "product_reference": "alt-nodejs20-docs-0:20.20.2-15.amd64",
        "relates_to_product_reference": "Debian-10"
      },
      {
        "category": "default_component_of",
        "full_product_name": {
          "name": "alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64 as a component of Debian 10",
          "product_id": "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64"
        },
        "product_reference": "alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
        "relates_to_product_reference": "Debian-10"
      }
    ]
  },
  "vulnerabilities": [
    {
      "cve": "CVE-2026-123877",
      "cwe": {
        "id": "CWE-295",
        "name": "Improper Certificate Validation"
      },
      "notes": [
        {
          "category": "description",
          "text": "A certificate validation bypass in Node.js https.Agent lets a cached TLS session authenticated under one CA policy be reused by a later request with a stricter policy. https.Agent.prototype.getName() assigns the same Agent and session-cache key to a request that omits ca and one that explicitly supplies ca: [], because an omitted value appends nothing to the key while an empty array stringifies to an empty string. The two policies differ: omitting ca uses the default trust store, while supplying ca replaces it. Since they share a key, a TLS session authenticated under the broader default policy is handed to a new connection made under the later ca: [] policy, and TLS 1.3 session resumption carries the earlier authentication forward, so the second request reports authorized === true and transmits confidential data to a server its own CA policy would reject on a fresh connection. This vulnerability affects Node.js 26.x, 24.x, and 22.x.",
          "title": "Vulnerability description"
        }
      ],
      "product_status": {
        "fixed": [
          "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
        ]
      },
      "references": [
        {
          "category": "self",
          "summary": "Canonical URL",
          "url": "https://cve.tuxcare.com/els-alt-nodejs/cve/CVE-2026-123877"
        },
        {
          "category": "external",
          "summary": "https://cna.openjsf.org/security-advisories.html",
          "url": "https://cna.openjsf.org/security-advisories.html"
        },
        {
          "category": "external",
          "summary": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases",
          "url": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases"
        }
      ],
      "release_date": "2026-11-11T19:17:00Z",
      "remediations": [
        {
          "category": "vendor_fix",
          "date": "2026-11-11T22:16:08.329889Z",
          "details": "Details on how to apply the fix are available at: https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366",
          "product_ids": [
            "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
          ],
          "url": "https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366"
        }
      ],
      "threats": [
        {
          "category": "impact",
          "details": "Low"
        }
      ]
    },
    {
      "cve": "CVE-2026-123866",
      "cwe": {
        "id": "CWE-416",
        "name": "Use After Free"
      },
      "notes": [
        {
          "category": "description",
          "text": "A use-after-free in Node.js HTTP/2 stream teardown can leak response memory, including the contents of other connections' response buffers, to a peer. When a stream is torn down while a write is still backpressured, for example by a peer RST_STREAM or by the server's own per-stream timeout destroying the stream, the stream's response buffer is freed but a reference to it is still used, so freed or unrelated heap memory is written to the socket instead of the intended response. On Node.js 26.x and 24.x the teardown can be driven purely by a remote peer once the window-size change from 26.9.0 and 24.22.0 is present, and on all supported lines the same defect is reachable through an application-initiated teardown such as a per-stream idle timeout. This vulnerability affects Node.js 26.x, 24.x, and 22.x.",
          "title": "Vulnerability description"
        }
      ],
      "product_status": {
        "fixed": [
          "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
        ]
      },
      "references": [
        {
          "category": "self",
          "summary": "Canonical URL",
          "url": "https://cve.tuxcare.com/els-alt-nodejs/cve/CVE-2026-123866"
        },
        {
          "category": "external",
          "summary": "https://cna.openjsf.org/security-advisories.html",
          "url": "https://cna.openjsf.org/security-advisories.html"
        },
        {
          "category": "external",
          "summary": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases",
          "url": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases"
        }
      ],
      "release_date": "2026-11-11T19:17:00Z",
      "remediations": [
        {
          "category": "vendor_fix",
          "date": "2026-11-11T22:16:08.329889Z",
          "details": "Details on how to apply the fix are available at: https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366",
          "product_ids": [
            "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
          ],
          "url": "https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366"
        }
      ],
      "threats": [
        {
          "category": "impact",
          "details": "Low"
        }
      ]
    },
    {
      "cve": "CVE-2026-123868",
      "cwe": {
        "id": "CWE-400",
        "name": "Uncontrolled Resource Consumption"
      },
      "notes": [
        {
          "category": "description",
          "text": "An unauthenticated HTTP/2 client can exhaust Node.js server memory because inbound DATA queued on an undrained stream is charged to no session budget. Each inbound DATA frame creates one JavaScript Buffer view in the receiving stream's readable queue, but nothing charges that queue to current_session_memory_: the socket read buffer is accounted only during parsing and released immediately, so whatever stays queued is accounted to nothing. A peer that fills a stream's receive window with one-byte DATA frames pays about 10 wire bytes per frame while the server retains about 114 bytes per frame, so a single stream on one connection can retain hundreds of megabytes from tens of megabytes sent. maxSessionMemory neither bounds the growth nor refuses new streams, because Http2Session::CanAddStream gates admission on the same counter that never sees the queue. This vulnerability affects Node.js 26.x and 24.x.",
          "title": "Vulnerability description"
        }
      ],
      "product_status": {
        "fixed": [
          "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
        ]
      },
      "references": [
        {
          "category": "self",
          "summary": "Canonical URL",
          "url": "https://cve.tuxcare.com/els-alt-nodejs/cve/CVE-2026-123868"
        },
        {
          "category": "external",
          "summary": "https://cna.openjsf.org/security-advisories.html",
          "url": "https://cna.openjsf.org/security-advisories.html"
        },
        {
          "category": "external",
          "summary": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases",
          "url": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases"
        }
      ],
      "release_date": "2026-11-11T19:17:00Z",
      "remediations": [
        {
          "category": "vendor_fix",
          "date": "2026-11-11T22:16:08.329889Z",
          "details": "Details on how to apply the fix are available at: https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366",
          "product_ids": [
            "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
          ],
          "url": "https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366"
        }
      ],
      "threats": [
        {
          "category": "impact",
          "details": "Low"
        }
      ]
    },
    {
      "cve": "CVE-2026-123865",
      "cwe": {
        "id": "CWE-400",
        "name": "Uncontrolled Resource Consumption"
      },
      "notes": [
        {
          "category": "description",
          "text": "An unauthenticated HTTP/2 client can permanently leak Node.js server memory and file descriptors. If a peer triggers a protocol error, for example an oversized frame header, while the session is already shutting down, nghttp2 tears the session down internally but Node.js never notices, leaving a dangling session: the socket stays in CLOSE_WAIT and all of Node.js's HTTP/2 state for that connection is held in memory indefinitely, with no further cost to the attacker. The attacker can start the shutdown remotely by sending GOAWAY(NO_ERROR), so it is reliable against default HTTP/2 servers. It is an incomplete-fix case of CVE-2026-48937: that fix detected nghttp2 internal terminations by watching for GOAWAY sent while not shutting down, but missed terminations that arrive while the session is already shutting down. This vulnerability affects Node.js 26.x, 24.x, and 22.x.",
          "title": "Vulnerability description"
        }
      ],
      "product_status": {
        "fixed": [
          "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
        ]
      },
      "references": [
        {
          "category": "self",
          "summary": "Canonical URL",
          "url": "https://cve.tuxcare.com/els-alt-nodejs/cve/CVE-2026-123865"
        },
        {
          "category": "external",
          "summary": "https://cna.openjsf.org/security-advisories.html",
          "url": "https://cna.openjsf.org/security-advisories.html"
        },
        {
          "category": "external",
          "summary": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases",
          "url": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases"
        }
      ],
      "release_date": "2026-11-11T19:17:00Z",
      "remediations": [
        {
          "category": "vendor_fix",
          "date": "2026-11-11T22:16:08.329889Z",
          "details": "Details on how to apply the fix are available at: https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366",
          "product_ids": [
            "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
          ],
          "url": "https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366"
        }
      ],
      "threats": [
        {
          "category": "impact",
          "details": "Low"
        }
      ]
    },
    {
      "cve": "CVE-2026-123867",
      "cwe": {
        "id": "CWE-295",
        "name": "Improper Certificate Validation"
      },
      "notes": [
        {
          "category": "description",
          "text": "A per-host mutual-TLS authorization bypass in Node.js lets a client authorized for the default hostname reach a protected hostname it is not authorized for. When a TLS server assigns a hostname a different client-certificate CA with server.addContext(host, { ca: protectedCA }) but no server certificate in that SNI context, the per-host client CA is never installed and the handshake falls back to the default client CA. In src/crypto/crypto_tls.cc, CertCbDone installs the SNI context's CA only when setSniContext succeeds, but setSniContext returns false for a context with no server certificate, so a CA-only SNI context silently keeps the default CA. A client holding a certificate trusted by the default CA, but not the protected CA, can therefore complete mTLS to the protected hostname and read its response even with requestCert and rejectUnauthorized enabled, while a client certified by the protected CA is rejected. This vulnerability affects Node.js 26.x, 24.x, and 22.x.",
          "title": "Vulnerability description"
        }
      ],
      "product_status": {
        "fixed": [
          "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
        ]
      },
      "references": [
        {
          "category": "self",
          "summary": "Canonical URL",
          "url": "https://cve.tuxcare.com/els-alt-nodejs/cve/CVE-2026-123867"
        },
        {
          "category": "external",
          "summary": "https://cna.openjsf.org/security-advisories.html",
          "url": "https://cna.openjsf.org/security-advisories.html"
        },
        {
          "category": "external",
          "summary": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases",
          "url": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases"
        }
      ],
      "release_date": "2026-11-11T19:17:00Z",
      "remediations": [
        {
          "category": "vendor_fix",
          "date": "2026-11-11T22:16:08.329889Z",
          "details": "Details on how to apply the fix are available at: https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366",
          "product_ids": [
            "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
          ],
          "url": "https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366"
        }
      ],
      "threats": [
        {
          "category": "impact",
          "details": "Low"
        }
      ]
    },
    {
      "cve": "CVE-2026-123863",
      "cwe": {
        "id": "CWE-617",
        "name": "Reachable Assertion"
      },
      "notes": [
        {
          "category": "description",
          "text": "A reachable assertion in Node.js HTTP/2 session teardown lets any unauthenticated client abort the server, over both TLS and cleartext. A client can arrange for an Http2Stream that still holds nghttp2-allocated header buffers to outlive its session: the stream is removed from the session's stream set but never detached, so when ~Http2Session() runs the memory accounting is nonzero and the CHECK_EQ(current_nghttp2_memory_, 0) assertion fails, terminating the process. The trigger needs only a default http2 server whose handler responds before the request body has ended, which is typical. It is a variant of CVE-2024-27983 that the earlier fix did not cover, because that fix only detached streams still tracked in the session. This vulnerability affects Node.js 26.x (since 26.9.0) and 24.x (since 24.22.0).",
          "title": "Vulnerability description"
        }
      ],
      "product_status": {
        "fixed": [
          "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
        ]
      },
      "references": [
        {
          "category": "self",
          "summary": "Canonical URL",
          "url": "https://cve.tuxcare.com/els-alt-nodejs/cve/CVE-2026-123863"
        },
        {
          "category": "external",
          "summary": "https://cna.openjsf.org/security-advisories.html",
          "url": "https://cna.openjsf.org/security-advisories.html"
        },
        {
          "category": "external",
          "summary": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases",
          "url": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases"
        }
      ],
      "release_date": "2026-11-11T19:17:00Z",
      "remediations": [
        {
          "category": "vendor_fix",
          "date": "2026-11-11T22:16:08.329889Z",
          "details": "Details on how to apply the fix are available at: https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366",
          "product_ids": [
            "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
          ],
          "url": "https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366"
        }
      ],
      "threats": [
        {
          "category": "impact",
          "details": "Low"
        }
      ]
    },
    {
      "cve": "CVE-2026-123862",
      "cwe": {
        "id": "CWE-248",
        "name": "Uncaught Exception"
      },
      "notes": [
        {
          "category": "description",
          "text": "An uncatchable exception in the Node.js zlib streaming API lets a peer crash a process by disconnecting while data is being compressed. zlib.params() queues a flush and completes its work in that write's callback; if the stream is destroyed first, as pipeline() does when the peer goes away, Writable still invokes the callback with an error, but the callback ignores its arguments and asserts that the native handle still exists. The handle is gone, so an ERR_INTERNAL_ASSERTION is thrown from inside stream internals and bypasses the stream's error event, the params() callback, and the pipeline() callback, terminating the process. An application is affected only if it calls deflate.params() while streaming to a peer, which is uncommon. This vulnerability affects Node.js 26.x, 24.x, and 22.x.",
          "title": "Vulnerability description"
        }
      ],
      "product_status": {
        "fixed": [
          "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
        ]
      },
      "references": [
        {
          "category": "self",
          "summary": "Canonical URL",
          "url": "https://cve.tuxcare.com/els-alt-nodejs/cve/CVE-2026-123862"
        },
        {
          "category": "external",
          "summary": "https://cna.openjsf.org/security-advisories.html",
          "url": "https://cna.openjsf.org/security-advisories.html"
        },
        {
          "category": "external",
          "summary": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases",
          "url": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases"
        }
      ],
      "release_date": "2026-11-11T19:17:00Z",
      "remediations": [
        {
          "category": "vendor_fix",
          "date": "2026-11-11T22:16:08.329889Z",
          "details": "Details on how to apply the fix are available at: https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366",
          "product_ids": [
            "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
          ],
          "url": "https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366"
        }
      ],
      "threats": [
        {
          "category": "impact",
          "details": "Low"
        }
      ]
    },
    {
      "cve": "CVE-2026-123828",
      "cwe": {
        "id": "CWE-122",
        "name": "Heap-based Buffer Overflow"
      },
      "notes": [
        {
          "category": "description",
          "text": "A one-byte heap buffer overflow in Node.js HTTP/2 Alt-Svc handling lets a remote, unauthenticated attacker corrupt process memory. When an application passes an attacker-controlled value such as a request's :authority header to Http2Session.altsvc(), the AltSvc implementation in src/node_http2.cc allocates a buffer sized to the origin length and then writes it with a null terminator, placing one byte past the end of the allocation. A single request carrying a long but syntactically valid :authority triggers the out-of-bounds write, which aborts the process and serves as a remote heap-corruption primitive. This vulnerability affects Node.js 26.x and 24.x.",
          "title": "Vulnerability description"
        }
      ],
      "product_status": {
        "fixed": [
          "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
        ]
      },
      "references": [
        {
          "category": "self",
          "summary": "Canonical URL",
          "url": "https://cve.tuxcare.com/els-alt-nodejs/cve/CVE-2026-123828"
        },
        {
          "category": "external",
          "summary": "https://cna.openjsf.org/security-advisories.html",
          "url": "https://cna.openjsf.org/security-advisories.html"
        },
        {
          "category": "external",
          "summary": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases",
          "url": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases"
        }
      ],
      "release_date": "2026-11-11T19:17:00Z",
      "remediations": [
        {
          "category": "vendor_fix",
          "date": "2026-11-11T22:16:08.329889Z",
          "details": "Details on how to apply the fix are available at: https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366",
          "product_ids": [
            "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
          ],
          "url": "https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366"
        }
      ],
      "threats": [
        {
          "category": "impact",
          "details": "Low"
        }
      ]
    },
    {
      "cve": "CVE-2026-123829",
      "cwe": {
        "id": "CWE-200",
        "name": "Exposure of Sensitive Information to an Unauthorized Actor"
      },
      "notes": [
        {
          "category": "description",
          "text": "A Permission Model bypass in Node.js recursive file watching discloses the names of files and directories the process is not permitted to read. On macOS and Windows, fs.watch() and fs.promises.watch() in recursive mode are backed by the native libuv watcher: FSEventWrap::Start checks kFileSystemRead only once, on the watched root, and FSEventWrap::OnEvent then forwards every filename libuv reports (relative paths at any depth) to the JavaScript callback without checking that each path is covered by the read grant. Code running under --permission with an exact read grant on a directory can therefore learn names such as sub/secret.txt even though readdir on that subdirectory is denied. The flaw exposes names and timing metadata, not file contents, and requires macOS or Windows plus files created under the watched directory by another actor. This vulnerability affects Node.js 26.x, 24.x, and 22.x.",
          "title": "Vulnerability description"
        }
      ],
      "product_status": {
        "fixed": [
          "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
        ]
      },
      "references": [
        {
          "category": "self",
          "summary": "Canonical URL",
          "url": "https://cve.tuxcare.com/els-alt-nodejs/cve/CVE-2026-123829"
        },
        {
          "category": "external",
          "summary": "https://cna.openjsf.org/security-advisories.html",
          "url": "https://cna.openjsf.org/security-advisories.html"
        },
        {
          "category": "external",
          "summary": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases",
          "url": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases"
        }
      ],
      "release_date": "2026-11-11T19:17:00Z",
      "remediations": [
        {
          "category": "vendor_fix",
          "date": "2026-11-11T22:16:08.329889Z",
          "details": "Details on how to apply the fix are available at: https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366",
          "product_ids": [
            "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
          ],
          "url": "https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366"
        }
      ],
      "threats": [
        {
          "category": "impact",
          "details": "Low"
        }
      ]
    },
    {
      "cve": "CVE-2026-123872",
      "cwe": {
        "id": "CWE-287",
        "name": "Improper Authentication"
      },
      "notes": [
        {
          "category": "description",
          "text": "A client certificate authentication bypass in Node.js TLS lets a client change the servername during TLS 1.2 renegotiation to reach endpoints it was not authorized for. On a server that applies different client-certificate policies per hostname, for example stricter admin-only client-cert auth on one host and ordinary client-cert auth on another, a client that authenticates for a permitted host can renegotiate the TLS 1.2 connection under a different servername and carry its existing authentication to the protected host, bypassing the stricter policy. This vulnerability affects Node.js 26.x, 24.x, and 22.x.",
          "title": "Vulnerability description"
        }
      ],
      "product_status": {
        "fixed": [
          "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
        ]
      },
      "references": [
        {
          "category": "self",
          "summary": "Canonical URL",
          "url": "https://cve.tuxcare.com/els-alt-nodejs/cve/CVE-2026-123872"
        },
        {
          "category": "external",
          "summary": "https://cna.openjsf.org/security-advisories.html",
          "url": "https://cna.openjsf.org/security-advisories.html"
        },
        {
          "category": "external",
          "summary": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases",
          "url": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases"
        }
      ],
      "release_date": "2026-11-11T19:17:00Z",
      "remediations": [
        {
          "category": "vendor_fix",
          "date": "2026-11-11T22:16:08.329889Z",
          "details": "Details on how to apply the fix are available at: https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366",
          "product_ids": [
            "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
          ],
          "url": "https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366"
        }
      ],
      "threats": [
        {
          "category": "impact",
          "details": "Low"
        }
      ]
    },
    {
      "cve": "CVE-2026-123875",
      "cwe": {
        "id": "CWE-476",
        "name": "NULL Pointer Dereference"
      },
      "notes": [
        {
          "category": "description",
          "text": "A NULL pointer dereference in Node.js HTTP/2 lets an unauthenticated client crash the server, over both TLS and cleartext, by cancelling file downloads. When the server serves a file with stream.respondWithFile() or stream.respondWithFD() and the client cancels the request, a StreamPipe used for the transfer is torn down in an order that leaves a NULL pointer which is then dereferenced, aborting the process. No crafted frames are needed, and a handful of cancelled requests against a default file-serving handler is enough. This vulnerability affects Node.js 26.x, 24.x, and 22.x.",
          "title": "Vulnerability description"
        }
      ],
      "product_status": {
        "fixed": [
          "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
        ]
      },
      "references": [
        {
          "category": "self",
          "summary": "Canonical URL",
          "url": "https://cve.tuxcare.com/els-alt-nodejs/cve/CVE-2026-123875"
        },
        {
          "category": "external",
          "summary": "https://cna.openjsf.org/security-advisories.html",
          "url": "https://cna.openjsf.org/security-advisories.html"
        },
        {
          "category": "external",
          "summary": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases",
          "url": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases"
        }
      ],
      "release_date": "2026-11-11T19:17:00Z",
      "remediations": [
        {
          "category": "vendor_fix",
          "date": "2026-11-11T22:16:08.329889Z",
          "details": "Details on how to apply the fix are available at: https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366",
          "product_ids": [
            "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
          ],
          "url": "https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366"
        }
      ],
      "threats": [
        {
          "category": "impact",
          "details": "Low"
        }
      ]
    },
    {
      "cve": "CVE-2026-123864",
      "cwe": {
        "id": "CWE-416",
        "name": "Use After Free"
      },
      "notes": [
        {
          "category": "description",
          "text": "A re-entrancy flaw in Node.js HTTPS lets an unauthenticated client read memory belonging to other connections, including TLS private keys and other users' requests. TLSWrap::DoWrite() calls ClearOut() directly when asked to write zero bytes; if that write is issued from JavaScript running inside the HTTP parser's on_body callback, ClearOut() decrypts the next TLS record while the parser is still mid-body, re-entering llhttp_execute() and causing a use-after-free and an out-of-bounds heap read. The server then copies that freed or unrelated heap memory into the response for the request body. Triggering it requires a handler that calls res.flushHeaders() before the request body ends and later calls res.end() with a non-empty chunk, and reading the leaked memory requires any ordinary route that echoes or stores a request body. Cleartext node:http is not affected. This vulnerability affects Node.js 26.x, 24.x, and 22.x.",
          "title": "Vulnerability description"
        }
      ],
      "product_status": {
        "fixed": [
          "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
        ]
      },
      "references": [
        {
          "category": "self",
          "summary": "Canonical URL",
          "url": "https://cve.tuxcare.com/els-alt-nodejs/cve/CVE-2026-123864"
        },
        {
          "category": "external",
          "summary": "https://cna.openjsf.org/security-advisories.html",
          "url": "https://cna.openjsf.org/security-advisories.html"
        },
        {
          "category": "external",
          "summary": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases",
          "url": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases"
        }
      ],
      "release_date": "2026-11-11T19:17:00Z",
      "remediations": [
        {
          "category": "vendor_fix",
          "date": "2026-11-11T22:16:08.329889Z",
          "details": "Details on how to apply the fix are available at: https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366",
          "product_ids": [
            "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
          ],
          "url": "https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366"
        }
      ],
      "threats": [
        {
          "category": "impact",
          "details": "Low"
        }
      ]
    },
    {
      "cve": "CVE-2026-123874",
      "cwe": {
        "id": "CWE-416",
        "name": "Use After Free"
      },
      "notes": [
        {
          "category": "description",
          "text": "A use-after-free in Node.js HTTP/2 lets an unauthenticated client corrupt server memory, over both TLS and cleartext, when the server serves files with respondWithFile() or respondWithFD(). A client can make the server free an Http2Stream while a write request that points to it is still queued on the socket; when that write completes, the code dereferences and makes a virtual call through the freed object. The only precondition is that the application serves a file with stream.respondWithFile() or stream.respondWithFD(), with default settings otherwise. This vulnerability affects Node.js 26.x (since 26.9.0) and 24.x (since 24.22.0).",
          "title": "Vulnerability description"
        }
      ],
      "product_status": {
        "fixed": [
          "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
          "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
        ]
      },
      "references": [
        {
          "category": "self",
          "summary": "Canonical URL",
          "url": "https://cve.tuxcare.com/els-alt-nodejs/cve/CVE-2026-123874"
        },
        {
          "category": "external",
          "summary": "https://cna.openjsf.org/security-advisories.html",
          "url": "https://cna.openjsf.org/security-advisories.html"
        },
        {
          "category": "external",
          "summary": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases",
          "url": "https://nodejs.org/en/blog/vulnerability/november-2026-security-releases"
        }
      ],
      "release_date": "2026-11-11T19:17:00Z",
      "remediations": [
        {
          "category": "vendor_fix",
          "date": "2026-11-11T22:16:08.329889Z",
          "details": "Details on how to apply the fix are available at: https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366",
          "product_ids": [
            "Debian-10:alt-nodejs20-docs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-nodejs-devel-0:20.20.2-15.amd64",
            "Debian-10:alt-nodejs20-npm-0:10.8.2-20.20.2-15.amd64"
          ],
          "url": "https://cve.tuxcare.com/els-alt-nodejs/releases/CLSA-2026:1794435366"
        }
      ],
      "threats": [
        {
          "category": "impact",
          "details": "Low"
        }
      ]
    }
  ]
}