CVE-2026-107383 mariadb-corporation CVE debrief

Who should care

Node.js developers and administrators using MariaDB Connector/Node.js should assess exposure and prioritize upgrading to fixed versions. Database administrators and security teams should monitor for suspicious database queries or unusual data access patterns.

Why it matters

CVE-2026-107383 is a high-severity vulnerability in MariaDB Connector/Node.js that exposes uninitialized process memory through malformed GeoJSON parameters. Node.js developers and administrators should assess exposure and prioritize upgrading to fixed versions to prevent data exposure.

• Discloses uninitialized Node.js heap data into a database value
• May propagate sensitive data to backups and replicas
• Requires verification of affected versions and inventory
• Prioritize upgrading to fixed versions to prevent data exposure

Technical summary

The vulnerability is caused by the GeoJSON Polygon and MultiPolygon binary encoders sizing 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, disclosing uninitialized Node.js heap data into a database value. This issue allows attackers to access sensitive data, including other users' content, session material, database credentials, or TLS key material, which may propagate to backups and replicas. The vulnerability affects versions prior to 3.2.5, 3.3.4, 3.4.7, and 3.5.4.

Defensive priority

Defenders should prioritize upgrading to fixed versions 3.2.5, 3.3.4, 3.4.7, or 3.5.4. Assess exposure by checking if your Node.js applications use affected versions of MariaDB Connector/Node.js. Verify inventory and apply compensating controls, such as monitoring for suspicious database queries or unusual data access patterns.

Recommended defensive actions

• Upgrade to MariaDB Connector/Node.js version 3.2.5, 3.3.4, 3.4.7, or 3.5.4
• Assess exposure by checking if your Node.js applications use affected versions
• Verify inventory and apply compensating controls, such as monitoring for suspicious database queries or unusual data access patterns
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE Program record and NVD vulnerability detail provide official information about the vulnerability. The source item and supplemental sources, including GitHub advisories and commits, offer additional context and fix information.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.