cve.bz

CVE-2026-107383 mariadb-corporation mariadb-connector-nodejs

7.5 highEPSS 0.4%Fix available

High (7.5) in mariadb-corporation mariadb-connector-nodejs. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in mariadb 3.2.5, 3.3.4, 3.4.7.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 33rd percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-10-14. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Fix and patched versions

  • mariadb (npm): fixed in 3.2.5, 3.3.4, 3.4.7, 3.5.4

Ask an AI about this CVE

Show the promptExplain CVE-2026-107383 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-107383?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-107383?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-107383 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
mariadb-corporation mariadb-connector-nodejs< 3.2.5
mariadb-corporation mariadb-connector-nodejs>= 3.3.0, < 3.3.4
mariadb-corporation mariadb-connector-nodejs>= 3.4.0, < 3.4.7
mariadb-corporation mariadb-connector-nodejs>= 3.5.0-rc.0, < 3.5.4

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-48qf-xh34-q73rnpmmariadb<3.2.53.2.5
GHSA-48qf-xh34-q73rnpmmariadb>=3.3.0 <3.3.43.3.4
GHSA-48qf-xh34-q73rnpmmariadb>=3.4.0 <3.4.73.4.7
GHSA-48qf-xh34-q73rnpmmariadb>=3.5.0-rc.0 <3.5.43.5.4

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-200 (59).

References

Check your stackJSON