dbcve.org
Out-of-bounds WriteWeakness · CWE-787

CVE-2026-1301

MEDIUM · 6.8 CVSS v4.0 Published 2026-02-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In builds with PubSub and JSON enabled, a crafted JSON message can cause the decoder to write beyond a heap-allocated array before authentication, reliably crashing the process and corrupting memory.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A heap-based buffer overflow exists in the JSON decoder when PubSub and JSON features are both enabled. A crafted JSON message causes the decoder to write beyond the bounds of a heap-allocated array before authentication, resulting in reliable process crashes and memory corruption.

MitigationDisable PubSub or JSON features in builds where not required; otherwise, apply vendor patches immediately as this pre-authentication flaw allows reliable memory corruption.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm PubSub feature is enabled
    Inspect build configuration files, compile-time flags, or runtime feature detection for PubSub module. Look for build options such as --enable-pubsub, ENABLE_PUBSUB, or similar flags in configuration files.
    Affected if PubSub feature is compiled or loaded into the environment
  2. Confirm JSON feature is enabled
    Inspect build configuration files, compile-time flags, or runtime feature detection for JSON module. Look for build options such as --enable-json, ENABLE_JSON, or similar flags in configuration files.
    Affected if JSON feature is compiled or loaded into the environment
  3. Verify both features are active simultaneously
    Cross-reference the findings from steps 1 and 2 to confirm both PubSub and JSON are enabled in the same build or runtime configuration.
    Affected if Both PubSub and JSON features are enabled in the same deployment
  4. Determine installed version
    Query the installed software version using package manager, binary version flag (such as -v or --version), or inspect version header files if accessible.
    Affected if Version is unknown or falls within any affected range if later specified by vendor

Environment is affected only if both PubSub and JSON features are simultaneously enabled, regardless of version, as this is a feature-specific flaw not version-dependent.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Disable PubSub or JSON features in builds where not required; otherwise, apply vendor patches immediately as this pre-authentication flaw allows reliable memory corruption.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1301 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1301 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data