Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5amended

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

CVE-2026-107383GHSA-48qf-xh34-q73r

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (mariadb 3.5.4, 3.4.7, 3.3.4, 3.2.5), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • npm mariadb

    Affected
    < 3.2.5>= 3.3.0, < 3.3.4>= 3.4.0, < 3.4.7>= 3.5.0-rc.0, < 3.5.4
    Fixed in
    3.4.7, 3.5.4, 3.2.5, 3.3.4

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
  • CVE-2026-107383: 0.39% estimated exploitation activity in the next 30 days; percentile 32.99 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-48qf-xh34-q73r

  2. Revision 2 · amended ·

    Amended from osv record GHSA-48qf-xh34-q73r

  3. Revision 1 · created ·

    Published from ghsa record GHSA-48qf-xh34-q73r

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-107383

Advisory: MariaDB Connector/Node.js exposes uninitialized process memory through malformed GeoJSON parameters
IDs: CVE-2026-107383, GHSA-48qf-xh34-q73r
Record: https://patchnext.com/advisories/cve-2026-107383 (revision 3, source checked 26 Oct 2026, 13:07 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: mariadb 3.5.4, 3.4.7, 3.3.4, 3.2.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm mariadb: affected < 3.2.5; >= 3.3.0, < 3.3.4; >= 3.4.0, < 3.4.7; >= 3.5.0-rc.0, < 3.5.4; fixed in 3.4.7, 3.5.4, 3.2.5, 3.3.4

## Suggested inspection (read-only)
- `npm ls mariadb --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on mariadb.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-48qf-xh34-q73r (GitHub-reviewed advisory GHSA-48qf-xh34-q73r lists affected ranges: npm mariadb >=0 =3.3.0 =3.4.0 =3.5.0-rc.0 <3.5.4)
- Verified: https://osv.dev/vulnerability/GHSA-48qf-xh34-q73r (OSV record GHSA-48qf-xh34-q73r lists affected ranges: npm mariadb >=0 =3.3.0 =3.4.0 =3.5.0-rc.0 <3.5.4 (fixed))

Commands are suggestions: review each one before running it.

Loading voting…