CVE-2026-107383: Mariadb MariaDB Connector/Node.js Exposes Uninitialized Process Vulnerability

HIGH
Advisory Identifier: GHSA-48qf-xh34-q73r
CVSS 7.5
CWE-200
Published
Advisory Summary

CVE-2026-107383 is a HIGH (CVSS 7.5) mariadb connector/node.js exposes uninitialized process vulnerability (CWE-200: Exposure of Sensitive Information to an Unauthorized Actor) affecting Mariadb libraries in the npm ecosystem. The issue involves mariadb connector/node.js exposes uninitialized process memory through malformed geojson parameters. Remediation is available by upgrading affected packages to version 3.2.5, 3.3.4, 3.4.7, 3.5.4.

CVE-2026-107383 at a Glance

CVE Identifier CVE-2026-107383
GHSA Identifier GHSA-48qf-xh34-q73r
Severity HIGH
CVSS v3.1 Base Score 7.5
CWE Classification CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Affected Product Mariadb
Package Ecosystem npm
Published Date
Last Updated

Security Impact

CVSS: 7.5

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required None (PR:N)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality High (C:H)
Integrity None (I:N)
Availability None (A:N)

How to Fix CVE-2026-107383

To remediate this vulnerability, upgrade all affected Mariadb dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

mariadb fixed: 3.2.5
npm install mariadb@3.2.5
mariadb fixed: 3.3.4
npm install mariadb@3.3.4
mariadb fixed: 3.4.7
npm install mariadb@3.4.7
mariadb fixed: 3.5.4
npm install mariadb@3.5.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

npm ls mariadb

How to Check if You Are Affected

To determine whether your Node.js application is affected by CVE-2026-107383, inspect your project dependencies using npm:

npm ls mariadb

Analyze the terminal output to locate any version of Mariadb in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.2.5), your application is affected.

Note: The npm ls mariadb command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor, where the product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. In Mariadb, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Description When encoding a GeoJSON Polygon or MultiPolygon parameter for the binary protocol, the connector sized its output buffer from the length property of each ring, then wrote each ring only if it was a real array. The two loops disagreed: any non-array ring carrying a numeric length (a string, or an object such as {"length": 4000}) still reserved 4 + 16 * length bytes, but wrote none of them. The buffer came from Buffer.allocUnsafe() and was returned in full regardless of how far the write position had advanced, so every reserved-but-unwritten byte was uninitialized Node.js heap. The sibling LineString case handled this correctly, aborting with null on the first malformed point, so no reserved byte could escape unwritten. The only gate on this path is value.type naming a GeoJSON type, so any object shaped like {"type": "Polygon", ...} reached the encoder. ### Impact An application that passes an attacker-influenced object as a parameter to execute() or batch() writes uninitialized process memory into the database, where it is readable by anyone who can read that row and persists into backups and replicas. Applications accepting GeoJSON for map or location features are the natural case, as the attacker controls coordinates directly. The disclosed memory is not scoped to the requesting user: in a shared Node.js process the heap may hold other users' request and response bodies, session tokens and cookies, database credentials and TLS key material. The leak is silent — the insert succeeds and the column simply holds more bytes than it should. No non-default connector option and no particular server configuration are required. query() is not affected: the text encoder builds geometry as strings rather than through Buffer.allocUnsafe(). ### Resolution Both the Polygon and MultiPolygon encoders now reject a non-array ring before reserving space for it, so no byte of the allocation can be left uninitialized by the writing loop, matching the existing LineString behaviour. ### Workarounds Validate that GeoJSON coordinates are properly nested arrays of numbers before passing the object as a parameter, or use query(), until upgraded.

CVE-2026-107383 Affected Mariadb Versions

4 component(s)
Fixed Versions:
3.2.53.3.43.4.73.5.4
Product / Package Ecosystem Affected Versions Fixed Version
mariadb
npm
< 3.2.5
3.2.5
mariadb
npm
≥ 3.3.0
< 3.3.4
3.3.4
mariadb
npm
≥ 3.4.0
< 3.4.7
3.4.7
mariadb
npm
≥ 3.5.0-rc.0
< 3.5.4
3.5.4

References

Frequently Asked Questions

What is CVE-2026-107383?
CVE-2026-107383 is a security vulnerability in Mariadb involving MariaDB Connector/Node.js exposes uninitialized process memory through malformed GeoJSON parameters under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor.
Which Mariadb versions are affected?
Affected versions include releases prior to 3.2.5, 3.3.4, 3.4.7, 3.5.4 across affected packages: mariadb.
What version fixes CVE-2026-107383?
Upgrading to 3.2.5, 3.3.4, 3.4.7, 3.5.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is mariadb affected?
Yes, mariadb is affected in releases prior to 3.2.5, 3.3.4, 3.4.7, 3.5.4. Upgrade your dependency to 3.2.5, 3.3.4, 3.4.7, 3.5.4 or later.
What is the CVSS score of CVE-2026-107383?
CVE-2026-107383 has a CVSS v3.1 base score of 7.5 (HIGH) with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N.
What CWE is associated with CVE-2026-107383?
CVE-2026-107383 is classified under CWE-200: Exposure of Sensitive Information to an Unauthorized Actor (The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.).
How can I check npm dependencies for CVE-2026-107383?
Run the dependency tree command: 'npm ls mariadb'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-48qf-xh34-q73r",
  "modified" : "2026-10-08T19:42:11Z",
  "published" : "2026-10-08T19:42:11Z",
  "aliases" : [ "CVE-2026-107383" ],
  "summary" : "MariaDB Connector/Node.js exposes uninitialized process memory through malformed GeoJSON parameters",
  "details" : "### Description\nWhen encoding a GeoJSON Polygon or MultiPolygon parameter for the binary protocol, the connector sized its output buffer from the length property of each ring, then wrote each ring only if it was a real array. The two loops disagreed: any non-array ring carrying a numeric length (a string, or an object such as {\"length\": 4000}) still reserved 4 + 16 * length bytes, but wrote none of them. The buffer came from Buffer.allocUnsafe() and was returned in full regardless of how far the write position had advanced, so every reserved-but-unwritten byte was uninitialized Node.js heap.\n\nThe sibling LineString case handled this correctly, aborting with null on the first malformed point, so no reserved byte could escape unwritten.\n\nThe only gate on this path is value.type naming a GeoJSON type, so any object shaped like {\"type\": \"Polygon\", ...} reached the encoder.\n\n### Impact\nAn application that passes an attacker-influenced object as a parameter to execute() or batch() writes uninitialized process memory into the database, where it is readable by anyone who can read that row and persists into backups and replicas. Applications accepting GeoJSON for map or location features are the natural case, as the attacker controls coordinates directly.\n\nThe disclosed memory is not scoped to the requesting user: in a shared Node.js process the heap may hold other users' request and response bodies, session tokens and cookies, database credentials and TLS key material. The leak is silent — the insert succeeds and the column simply holds more bytes than it should.\n\nNo non-default connector option and no particular server configuration are required. query() is not affected: the text encoder builds geometry as strings rather than through Buffer.allocUnsafe().\n\n### Resolution\nBoth the Polygon and MultiPolygon encoders now reject a non-array ring before reserving space for it, so no byte of the allocation can be left uninitialized by the writing loop, matching the existing LineString behaviour.\n\n### \nWorkarounds\nValidate that GeoJSON coordinates are properly nested arrays of numbers before passing the object as a parameter, or use query(), until upgraded.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "npm",
      "name" : "mariadb"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.2.5"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "mariadb"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.3.0"
      }, {
        "fixed" : "3.3.4"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "mariadb"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.4.0"
      }, {
        "fixed" : "3.4.7"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "npm",
      "name" : "mariadb"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "3.5.0-rc.0"
      }, {
        "fixed" : "3.5.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/mariadb-corporation/mariadb-connector-nodejs/security/advisories/GHSA-48qf-xh34-q73r"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/2314c03b785db482599d2befd06f4992e5fc46b3"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/a4aa048b57dc47309b80e5cc25a4a8eedb32fd9f"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/b2ca628864b0fc2e3e94ea96910f6b693ad5bd30"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/faa27d1b2b7753a54000f586d5148089b60d1284"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/mariadb-corporation/mariadb-connector-nodejs"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.2.5"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.3.4"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.4.7"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.5.4"
  }, {
    "type" : "WEB",
    "url" : "https://jira.mariadb.org/browse/CONJS-367"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-200" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-08T19:42:11Z",
    "nvd_published_at" : null
  }
}