CVE Intelligence
High Info disclosure

CVE-2026-107383 — MariaDB Connector/Node.js exposes uninitialized process memory through malformed GeoJSON parameters

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.

Published Oct 8, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.4% (30-day exploitation probability)+5
  • Technical severity (high)+6
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.39%
ahead of 31% of scored CVEs · Oct 15, 2026
Affects
Mariadb-corporation
Mariadb-connector-nodejs and 1 more
CVSS base
7.5
High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Npm Mariadb: fixed in version 3.2.5 — github.com (GitHub Security Advisories)
  • Npm Mariadb: fixed in version 3.3.4 — github.com (GitHub Security Advisories)
  • Npm Mariadb: fixed in version 3.4.7 — github.com (GitHub Security Advisories)
  • Npm Mariadb: fixed in version 3.5.4 — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Mariadb-corporation Mariadb-connector-nodejs, Npm Mariadb).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. Search available logs for exploit probes matching the vulnerability class (info disclosure), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Mariadb-corporation Mariadb-connector-nodejs version < 3.2.5version >= 3.3.0, < 3.3.4version >= 3.4.0, < 3.4.7version >= 3.5.0-rc.0, < 3.5.4 Vulnerable CVE Program (cve.org) e CISA ADP
Npm Mariadb < 3.2.5≥ 3.3.0 and < 3.3.4≥ 3.4.0 and < 3.4.7≥ 3.5.0-rc.0 and < 3.5.4 Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
7.5 CVSS 3.1 High 3.9 3.6 security-advisories@github.com via NIST National Vulnerability Database
7.5 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.5 CVSS 3.1 High — — GitHub_M via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N (score shown at the top: security-advisories@github.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-200 · Exposure of Sensitive Information

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.39%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Look for anomalous data read/export volumes and access to sensitive records.
web/proxy/WAF logsnetwork IDS/IPSapplication logsauthentication logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 13, 2026 · GitHub Security Advisories
  • Affected products added · npm/mariadb
    Oct 13, 2026 · GitHub Security Advisories
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · Undergoing Analysis → Awaiting Analysis
    Oct 13, 2026 · NIST National Vulnerability Database
  • Affected products added · mariadb-corporation/mariadb-connector-nodejs
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 7.5
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Undergoing Analysis
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Oct 8, 2026 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

11 on the record

Elsewhere on this site

Mariadb-corporation
every CVE for this vendor
Info disclosure
same class
CWE-200
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-107385 MariaDB Connector/Node.js: SQL injection in the text protocol when the session uses NO_BACKSLASH_ESCAPES 7d
  • CVE-2026-107384 MariaDB Connector/Node.js: SQL injection through object keys in SET expansion (permitSetMultiParamEntries) 7d
  • CVE-2026-107382 MariaDB Connector/Node.js: Uncaught exception crashes the client during ed25519 authentication with zero-configuration TLS 7d
  • CVE-2026-55855 MariaDB Connector/Node.js: Possible SQL injection in Buffer parameter escaping under big5/gbk/sjis/cp932/gb18030 client charsets Aug 28, 2026
  • CVE-2026-55854 MariaDB Connector/Node.js: Cleartext Transmission of Sensitive Information and Insufficiently Protected Credentials in mariadb Aug 28, 2026
  • CVE-2026-55215 MariaDB Connector/Node.js: Connector leaks the cleartext password to an MitM despite `ssl: true` Aug 28, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-107383 is "MariaDB Connector/Node.js exposes uninitialized process memory through malformed GeoJSON parameters", rated High. It affects Mariadb-connector-nodejs (Mariadb-corporation); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.5 describes technical severity. EPSS 0.39% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.