CVE-2026-107383

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

Published Oct 8, 2026 · corrected/updated Oct 16, 2026 · evidence confidence high

### 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

Grounded briefings

Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.

Executive

CVE-2026-107383 is a high public vulnerability record for this product. It is not currently listed in the CISA Known Exploited catalog. Check the linked vendor or CERT advisories for patch status. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.

System administrator

Identify whether this product is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: mariadb (0 → 3.2.5); mariadb (3.3.0 → 3.3.4); mariadb (3.4.0 → 3.4.7); mariadb (3.5.0-rc.0 → 3.5.4). Check the linked vendor or CERT advisories for patch status. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.

Security analyst

Signals on file: CVSS 7.5, EPSS 0.4%. It is not currently listed in the CISA Known Exploited catalog. Weakness classes: CWE-200. Sources contributing to this record: cve_org, epss, github, osv. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.

Exploitation and remediation

Exploitation evidence
Not listed as known exploited in CISA KEV. Not in the CISA KEV catalog.
Patch and remediation
No required-action text is stored yet. Use the vendor or CERT links in Sources for patch availability.
Safe detection guidance
Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.

Code

The project this record applies to. Exploit listings stay in References.

Timeline

Detection, updates, and resolution for this record.

Oct 8, 2026 · GitHub Advisory Database
Detected
### 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 o
Oct 16, 2026 · GitHub Advisory Database
Fix available
mariadb fixed in 3.2.5; mariadb fixed in 3.3.4; mariadb fixed in 3.4.7; mariadb fixed in 3.5.4
Oct 16, 2026 · GitHub Advisory Database
Fix available
mariadb fixed in 3.2.5
Oct 16, 2026 · GitHub Advisory Database
Fix available
mariadb fixed in 3.3.4
Oct 16, 2026 · GitHub Advisory Database
Fix available
mariadb fixed in 3.4.7
Oct 16, 2026 · GitHub Advisory Database
Fix available
mariadb fixed in 3.5.4
Oct 16, 2026 · GitHub Advisory Database
Updated
### 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 o

Affected

npm mariadb0 → 3.2.5
npm mariadb3.3.0 → 3.3.4
npm mariadb3.4.0 → 3.4.7
npm mariadb3.5.0-rc.0 → 3.5.4

Sources

CVE.orgVulnerability recordCVE-2026-107383
Official CVE identifier
cve.org
FIRST EPSSExploitation probabilityCVE-2026-107383
30-day exploitation probability 0.4%
first.org
GitHub Advisory DatabasePackage advisoryGHSA-48qf-xh34-q73r
GitHub Advisory Database record mirrored by OSV.
github.com
OSV.devPackage advisoryGHSA-48qf-xh34-q73r
MariaDB Connector/Node.js exposes uninitialized process memory through malformed GeoJSON parameters
osv.dev