MariaDB Connector/Node.js exposes uninitialized process memory through malformed GeoJSON parameters

Summary

MariaDB Connector/Node.js is used to connect applications developed on Node.js to MariaDB and MySQL databases. Prior to 3.2.5, 3.3.4, 3.4.7, and 3.5.4, the GeoJSON Polygon and MultiPolygon binary encoders size a Buffer.allocUnsafe() allocation from each ring's numeric length before confirming that the ring is an array. A malformed non-array ring can therefore reserve bytes that the writing loop skips, and the connector sends the full buffer through execute() or batch(), disclosing uninitialized Node.js heap data into a database value. The persisted data can include other users' content, session material, database credentials, or TLS key material and may propagate to backups and replicas. The text-protocol query() path is not affected. This issue is fixed in versions 3.2.5, 3.3.4, 3.4.7, and 3.5.4.

Timeline

1. Oct 8, 2026, 6:27 PM UTCCVE published
2. Oct 14, 2026, 1:11 AM UTCCISA SSVC assessment

   Exploitation: none · Automatable: yes · Technical impact: partial

3. Oct 14, 2026, 1:11 AM UTCRecord last updated

Affected versions

• mariadb-corporation mariadb-connector-nodejs

  fixed in 3.2.5; From 3.3.0 · fixed in 3.3.4; From 3.4.0 · fixed in 3.4.7; From 3.5.0-rc.0 · fixed in 3.5.4

• mariadbBitnami

  fixed in 3.2.5; From 3.3.0 · fixed in 3.3.4; From 3.4.0 · fixed in 3.4.7; From 3.5.0 · fixed in 3.5.4

• mariadb-minBitnami

  fixed in 3.2.5; From 3.3.0 · fixed in 3.3.4; From 3.4.0 · fixed in 3.4.7; From 3.5.0 · fixed in 3.5.4

• mysql-clientBitnami

  fixed in 3.2.5; From 3.3.0 · fixed in 3.3.4; From 3.4.0 · fixed in 3.4.7; From 3.5.0 · fixed in 3.5.4

• mariadbnpm

  fixed in 3.2.5

• mariadbnpm

  From 3.3.0 · fixed in 3.3.4

• mariadbnpm

  From 3.4.0 · fixed in 3.4.7

• mariadbnpm

  From 3.5.0-rc.0 · fixed in 3.5.4

References 10