MariaDB Connector/Node.js exposes uninitialized process memory through malformed GeoJSON parameters
### 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
- Products
- mariadb
- Affected versions
- Not specified
- Fixed versions
- 3.2.5, 3.3.4, 3.4.7, 3.5.4
- CVEs
- CVE-2026-107383
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 30 Oct 2026, 20:01 UTC · Revision 1
Source evidence
MariaDB Connector/Node.js exposes uninitialized process memory through malformed GeoJSON parameters
core-osv · Original sourcePublished 8 Oct 2026, 19:42 UTC
### 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
osv:GHSA-48qf-xh34-q73r
mariadb
Fixed versions: 3.2.5
mariadb
Fixed versions: 3.3.4
mariadb
Fixed versions: 3.4.7
mariadb
Fixed versions: 3.5.4
Complete source record
{
"id": "78c00a5e7671b0972bd741a517cd7e405bb346b9ad97ba34287924d6176b1178",
"url": "https://osv.dev/vulnerability/GHSA-48qf-xh34-q73r",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "MariaDB Connector/Node.js exposes uninitialized process memory through malformed GeoJSON parameters",
"summary": "### 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",
"evidence": "osv:GHSA-48qf-xh34-q73r",
"products": [
{
"name": {
"value": "mariadb",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "3.2.5",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
},
{
"name": {
"value": "mariadb",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "3.3.4",
"evidence": "/affected/1/ranges"
}
],
"affected_versions": []
},
{
"name": {
"value": "mariadb",
"evidence": "/affected/2/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "3.4.7",
"evidence": "/affected/2/ranges"
}
],
"affected_versions": []
},
{
"name": {
"value": "mariadb",
"evidence": "/affected/3/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "3.5.4",
"evidence": "/affected/3/ranges"
}
],
"affected_versions": []
}
],
"severity": "high",
"structured": {
"id": "GHSA-48qf-xh34-q73r",
"aliases": [
"BIT-mariadb-2026-107383",
"BIT-mariadb-min-2026-107383",
"BIT-mysql-client-2026-107383",
"CVE-2026-107383",
"GHSA-48qf-xh34-q73r"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
}
],
"affected": [
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "0"
},
{
"fixed": "3.2.5"
}
]
}
],
"package": {
"name": "mariadb",
"purl": "pkg:npm/mariadb",
"ecosystem": "npm"
},
"database_specific": {
"source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-48qf-xh34-q73r/GHSA-48qf-xh34-q73r.json"
}
},
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "3.3.0"
},
{
"fixed": "3.3.4"
}
]
}
],
"package": {
"name": "mariadb",
"purl": "pkg:npm/mariadb",
"ecosystem": "npm"
},
"database_specific": {
"source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-48qf-xh34-q73r/GHSA-48qf-xh34-q73r.json"
}
},
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "3.4.0"
},
{
"fixed": "3.4.7"
}
]
}
],
"package": {
"name": "mariadb",
"purl": "pkg:npm/mariadb",
"ecosystem": "npm"
},
"database_specific": {
"source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-48qf-xh34-q73r/GHSA-48qf-xh34-q73r.json"
}
},
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "3.5.0-rc.0"
},
{
"fixed": "3.5.4"
}
]
}
],
"package": {
"name": "mariadb",
"purl": "pkg:npm/mariadb",
"ecosystem": "npm"
},
"database_specific": {
"source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-48qf-xh34-q73r/GHSA-48qf-xh34-q73r.json"
}
}
],
"modified": "2026-10-16T09:55:42.823324858Z",
"provider": "osv",
"references": [
"https://github.com/mariadb-corporation/mariadb-connector-nodejs/security/advisories/GHSA-48qf-xh34-q73r",
"https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/2314c03b785db482599d2befd06f4992e5fc46b3",
"https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/a4aa048b57dc47309b80e5cc25a4a8eedb32fd9f",
"https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/b2ca628864b0fc2e3e94ea96910f6b693ad5bd30",
"https://github.com/mariadb-corporation/mariadb-connector-nodejs/commit/faa27d1b2b7753a54000f586d5148089b60d1284",
"https://github.com/mariadb-corporation/mariadb-connector-nodejs",
"https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.2.5",
"https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.3.4",
"https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.4.7",
"https://github.com/mariadb-corporation/mariadb-connector-nodejs/releases/tag/3.5.4",
"https://jira.mariadb.org/browse/CONJS-367"
],
"provider_metadata": {
"cwe_ids": [
"CWE-200"
],
"severity": "HIGH",
"github_reviewed": true,
"nvd_published_at": null,
"github_reviewed_at": "2026-10-08T19:42:11Z"
}
},
"related_cves": [
{
"value": "CVE-2026-107383",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/database_specific/severity"
},
"source_id": "core-osv",
"document_id": 338696,
"published_at": "2026-10-08T19:42:11+00:00"
}