Invalid UTF-8 Database names are not handled well

ExportXMLWordPrintableJSON

    • Type: Bug
    • Resolution: Fixed
    • Priority: Critical - P2
    • 9.1.0-rc0, 9.0.2, 9.1.0-rc1024
    • Affects Version/s: 9.0 Required
    • Component/s: None
    • Storage Execution
    • Fully Compatible
    • ALL
    • v9.0
    • Storage Execution 2026-10-12, CAR Team 2026-09-14, CAR Team 2026-09-28
    • 200
    • 🟦 Shard Catalog
    • None
    • None
    • None
    • None
    • None
    • None

      Prior to 9.0, if a user performed createCollection or an implicit collection creation with an insert (perhaps any other methods like $out that create a namespace), you could do so with invalid UTF-8, and it would get stored in the catalog. This was wrong, but benign until SERVER-95530 landed in 9.0. That ticket introduces a library to validate UTF-8 names. This library will throw for invalid database names. This has impacts in various areas of the server that are unpatched.

        1. invalid_utf8_db_name_insert.js
          4 kB
        2. invalid_utf8_db_name_creation.js
          7 kB
        3. invalid_utf8_db_name_client.py
          11 kB

            Assignee:
            Matt Kneiser
            Reporter:
            Matt Kneiser
            Votes:
            0 Vote for this issue
            Watchers:
            12 Start watching this issue

              Created:
              Updated:
              Resolved: