Vulnerability · NVD published 2026-10-08
CVE-2026-107383
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.
Signals
- Exploited in the wild
- Not on KEVNot in CISA's catalogue as of the last daily pull. Absence is not proof of safety.
- EPSS · 30-day forecast
- 0%Chance of exploitation in the next 30 days, 31th percentile of all CVEs. A forecast; KEV outranks it.
- CVSS · NVD · HIGH
- 7.5CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- Internet exposure
- not stated by sourcesNo exposure census on this CVE's dispatches.
Exploits
not checkedNot checked yet. Our exploit watch has not looked at this CVE, so this says nothing either way.
On the wire
1 dispatchWatch this one?
KEV additions reach Telegram and the KEV-only RSS as they land.
Check your stack
Paste what you run: the CVEs exploited in the wild against it, and who is cited as exploiting them, with the report.
Stack checkNo key. No signup.