ExportXMLWordPrintableJSON

    • Type: Bug
    • Resolution: Done
    • Priority: High
    • None
    • Affects Version/s: None
    • Component/s: None
    • Environment:
      AWS Lambda ZIP; Linux x86_64; .NET 10 host. MongoDB Database Tools 100.19.1, Go 1.26.8, golang.org/x/net v0.59.0. Scanner: Amazon Inspector Lambda standard scanning.
    • Tools and Replicator
    • 0
    • Not Needed

      Summary

      Amazon Inspector reports 14 active vulnerability findings against both mongodump and mongorestore from MongoDB Database Tools 100.19.1 in our UAT deployment: 2 critical, 9 high, 2 medium and 1 untriaged. Our production deployment policy blocks critical findings, so these findings prevent promotion of this package.

      We are requesting a patched official release or supported remediation, an estimated release date, and an assessment of which findings affect executable code paths in these tools. This report concerns already-public upstream CVEs; it does not claim a newly discovered exploit in MongoDB Database Tools.

      Verified environment and evidence

      • Evidence collected: 26 October 2026.
      • Deployment: AWS Lambda ZIP, Linux x86_64, managed .NET 10 host; MongoDB binaries run as child processes.
      • Database Tools version embedded in both deployed binaries: 100.19.1.
      • Go build version embedded in both deployed binaries: go1.26.8.
      • Embedded module build metadata in both binaries: golang.org/x/net v0.59.0.
      • Downloaded the deployed Lambda ZIP and compared both executables byte-for-byte with our repository copies: identical. Version evidence was read from binary metadata/strings; the Linux binaries were not executed locally.
      • Inspector observations shown below were refreshed on 26 October 2026 after the deployed Lambda's latest modification. These are current active findings, rather than findings against an earlier package.
      • Each of the 14 findings identifies both executable paths. Counts refer to Inspector finding records, not 28 separate CVEs.

      Binary SHA-256 values:

      • mongodump: 78a125c17ff1ff15f78369762c47e49009fd5f34b5e79038423cede074616cba
      • mongorestore: b6664d4e5467192e6c5e8b168d1ac6e5ff3a49e8642ddb41d248c93654cd9ff2

      Scanner findings

      Severity and fixed-in versions below are reproduced from Amazon Inspector. They are scanner classifications, not our independent exploitability assessment. Every row affects both mongodump and mongorestore.

      CVE Inspector severity Package Detected version Inspector fixed-in version
      CVE-2026-56857 CRITICAL go/stdlib 1.26.8 1.27.2
      CVE-2026-78663 CRITICAL golang.org/x/net v0.59.0 0.60.0
      CVE-2026-56866 HIGH go/stdlib 1.26.8 1.27.2
      CVE-2026-78659 HIGH golang.org/x/net v0.59.0 0.60.0
      CVE-2026-78660 HIGH golang.org/x/net v0.59.0 0.60.0
      CVE-2026-78667 HIGH go/stdlib 1.26.8 1.27.2
      CVE-2026-78669 HIGH golang.org/x/net v0.59.0 0.60.0
      CVE-2026-94439 HIGH go/stdlib 1.26.8 1.27.2
      CVE-2026-94440 HIGH go/stdlib 1.26.8 1.27.2
      CVE-2026-97031 HIGH go/stdlib 1.26.8 1.27.2
      CVE-2026-97032 HIGH golang.org/x/net v0.59.0 0.60.0
      CVE-2026-94448 MEDIUM go/stdlib 1.26.8 1.27.2
      CVE-2026-97030 MEDIUM go/stdlib 1.26.8 1.27.2
      CVE-2026-111943 UNTRIAGED go/stdlib 1.26.8 1.27.3

      Inspector reports Go 1.27.2 for the October 8 standard-library fixes and Go 1.27.3 for CVE-2026-111943. The Go release history also documents security updates on the 1.26 branch in 1.26.9 and 1.26.10 respectively. Please confirm the appropriate supported toolchain; the scanner's selected fixed-in version should not be interpreted as requiring a Go major/minor branch upgrade.

      The separate golang.org/x/net findings identify 0.60.0 as the fixed version. Recompiling with a newer Go toolchain while retaining x/net v0.59.0 would not address those module-version findings.

      Applicability and operational context

      These executables are invoked on demand to export and restore compressed BSON archives over TLS. The restore workflow uses namespace remapping and --drop. Our database target is Amazon DocumentDB; this report requests remediation of the distributed tools and does not assume MongoDB support for DocumentDB.

      We have not demonstrated exploitation or performed a complete reachability analysis. In particular:

      • CVE-2026-56857 is described by Inspector as a Windows os.Root junction issue. This deployment runs Linux, so the stated Windows-specific attack does not apply here, although Inspector reports it as critical.
      • CVE-2026-78663 concerns HTTP/2 server flow control. We have not established whether an affected server path is reachable in either CLI executable.
      • Other findings concern HTTP servers, clients, templates or TLS. Inclusion of a package/version does not by itself prove those vulnerable paths are exercised by these tools. TLS-related findings merit assessment against the tools' client connections.

      The policy impact remains even where findings may be inapplicable. A vendor-authored applicability statement or VEX document would help us assess exceptions accurately.

      Reproduction / evidence collection

      1. Package the 100.19.1 Linux x86_64 mongodump and mongorestore binaries in an AWS Lambda ZIP with Amazon Inspector Lambda standard scanning enabled in a supported region.
      2. Allow Inspector to inventory and scan the deployment.
      3. Filter active findings to package file paths mongodump and mongorestore.
      4. Compare reported Go and x/net versions and CVEs with the table above.

      This describes our observed collection workflow, not a separately tested minimal reproduction. The scanner descriptions and observation timestamps are included below; sanitized JSON and CSV exports can be supplied on request. AWS account identifiers, function names, ARNs, network configuration and signed URLs are omitted.

      Requested response

      1. Is a post-100.19.1 release planned that updates the Go toolchain and golang.org/x/net to address these CVEs? Please provide the tracking ticket, intended release version and ETA if available.
      2. Is a patched official Linux x86_64 build available before that release?
      3. Which findings are applicable to mongodump and mongorestore? Please provide a security advisory, VEX or equivalent statement for findings whose vulnerable code is absent or unreachable.
      4. If an official build is not imminent, is rebuilding the 100.19.1 tag using patched Go and x/net an acceptable interim approach, and what build flags or regression checks do you recommend?

      Public references

      Inspector descriptions and observations

      CVE-2026-56857 (CRITICAL)

      On Windows, when the target of Root.Mkdir or Root.MkdirAll is a junction pointing to an empty location, the operation can create a directory at the junction target even when that target is located outside the root. This only applies to operations where the last path component is a junction (path/to/junction, but not path/junction/target).

      First observed: 2026-10-10T01:48:30.945000+01:00; last observed: 2026-10-26T09:44:40.466000+00:00.

      CVE-2026-78663 (CRITICAL)

      The HTTP/2 server can refund connection-level flow control twice for the same data: Once when a client resets a stream (refunding data for any sent-but-unread portion of the stream), and again when a request handler reads the buffered data. A malicious client can exploit this to bypass the configured connection-level flow control limit (MaxReceiveBufferPerConnection). Total buffered data is still limited by the concurrent stream limit and stream-level flow control.

      First observed: 2026-10-10T01:48:30.946000+01:00; last observed: 2026-10-26T09:44:40.411000+00:00.

      CVE-2026-56866 (HIGH)

      When http.Transport sends an HTTP/1 CONNECT request with a non-empty Request.Body, it writes the body directly to the connection without framing after the request headers. If the server rejects the CONNECT request with a non-2xx keep-alive response, Transport returns the connection to the idle pool. Because CONNECT requests do not have a request body, the server may interpret the trailing body bytes as a subsequent pipelined HTTP/1.1 request on the connection, leaving the pooled connection desynchronized and causing the next caller that reuses it to read the response to the injected request. In reverse proxies (including httputil.ReverseProxy) that forward CONNECT requests through a shared Transport, this can lead to cross-user response poisoning.

      First observed: 2026-10-10T01:48:30.940000+01:00; last observed: 2026-10-26T09:44:40.468000+00:00.

      CVE-2026-78659 (HIGH)

      When "Trailer" headers are sent by a client, the HTTP server internally uses the header values to populate the Request.Trailer map passed to the server handler. Because Request.Trailer is a map, each entry incurs memory overhead. For HTTP/2 servers, a malicious client can exploit this by sending a "Trailer" header that declares a large number of fields, causing the server to allocate a disproportionate amount of memory while bypassing Server.MaxHeaderValueCount and Server.MaxHeaderBytes limits. This exploit is not applicable for HTTP/1 servers, which do not support multiplexing a large number of requests over one TCP connection, and whose Server.MaxHeaderBytes are calculated differently.

      First observed: 2026-10-10T01:48:30.937000+01:00; last observed: 2026-10-26T09:44:40.410000+00:00.

      CVE-2026-78660 (HIGH)

      Historically, we have been rather lax about malformed framing-related headers in our HTTP/2 implementation, as they cannot interfere with HTTP/2 framing. However, this makes it possible for our HTTP/2 implementation to forward responses containing such headers to an HTTP/1 client when acting as a reverse proxy. If the HTTP/1 client also does not behave strictly enough, this can result in response smuggling.

      First observed: 2026-10-10T01:48:30.944000+01:00; last observed: 2026-10-26T09:44:40.411000+00:00.

      CVE-2026-78667 (HIGH)

      When parsing a Range header containing a large number of small ranges, FileServer(FS), ServeContent, and ServeFile(FS) can consume an excessive amount of CPU.

      First observed: 2026-10-10T01:48:30.947000+01:00; last observed: 2026-10-26T09:44:40.468000+00:00.

      CVE-2026-78669 (HIGH)

      A malicious HTTP/2 peer can cause excessive CPU consumption in the client or server by opening a large number of streams and then sending many small SETTINGS frames containing SETTINGS_INITIAL_WINDOW_SIZE values.

      First observed: 2026-10-10T01:48:30.944000+01:00; last observed: 2026-10-26T09:44:40.409000+00:00.

      CVE-2026-94439 (HIGH)

      When an HTTP server handler sends a 2xx response to an HTTP/1 CONNECT request and returns without hijacking the connection, the server improperly continues to read and serve requests from the connection. Since a 2xx response to an HTTP/1 CONNECT converts the connection into a tunnel, the server should not treat the connection as continuing to contain HTTP. The impact of this misbehavior is mostly limited to potential request smuggling, where an intermediate proxy considers the data on the connection to be tunneled and the server considers it to be HTTP.

      First observed: 2026-10-10T01:48:30.947000+01:00; last observed: 2026-10-26T09:44:40.468000+00:00.

      CVE-2026-94440 (HIGH)

      Parsing a multipart form can bypass memory limits and read an arbitrarily long line into memory when the remaining limit at the start of a part is less than 400 bytes.

      First observed: 2026-10-10T01:48:30.939000+01:00; last observed: 2026-10-26T09:44:40.467000+00:00.

      CVE-2026-97031 (HIGH)

      Multiple ECH outer extension references are not permitted under RFC 9849; previously, a client could send a well-crafted packet that could trigger memory exhaustion in the server process by specifying multiple references. We now reject these as malformed and curb the memory amplification vector as a result.

      First observed: 2026-10-10T01:48:30.938000+01:00; last observed: 2026-10-26T09:44:40.467000+00:00.

      CVE-2026-97032 (HIGH)

      HTTP/2 servers could end up crashing due to inadvertently modifying its HPACK encoder concurrently. This happens because the server modifies the HPACK encoder from two goroutines without synchronization: one uses the encoder to encode a HEADERS frame as part of a response sent to a client and the other modifies the encoder's table size when handling a SETTINGS frame containing SETTINGS_HEADER_TABLE_SIZE that a client sends. A malicious client can repeatedly send a request while changing the header table size to crash the server.

      First observed: 2026-10-10T01:48:30.939000+01:00; last observed: 2026-10-26T09:44:40.410000+00:00.

      CVE-2026-94448 (MEDIUM)

      When a JavaScript template literal contains consecutive expressions, the context tracking state was not properly reset upon entering a new expression. We now ensure that template-literal expression entries correctly reset context variables so all subsequent regular expression literals are accurately recognized and escaped.

      First observed: 2026-10-10T01:48:30.941000+01:00; last observed: 2026-10-26T09:44:40.468000+00:00.

      CVE-2026-97030 (MEDIUM)

      A trusted template author may have previously written a valid template wherein the use of the 'yield' keyword would not be correctly escaped. We now ensure that valid keyword uses are escaped and non-keyword uses are not escaped.

      First observed: 2026-10-10T01:48:30.948000+01:00; last observed: 2026-10-26T09:44:40.469000+00:00.

      CVE-2026-111943 (UNTRIAGED)

      On most platforms, Go uses the given system root certificates. However, in some narrower cases, the system trust stores may not be updated without further action. To defend against the narrower set of cases that may remain affected, a denylist was added in crypto/x509 to return an error when calling Verify with any of the known intermediate certificates that are no longer considered to be trustworthy.

      First observed: 2026-10-21T21:40:09.442000+01:00; last observed: 2026-10-26T09:44:40.469000+00:00.

            Assignee:
            Dave Rolsky
            Reporter:
            Mark Hopper (EXT)
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              Resolved: