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

CVE-2026-4746

CRITICAL · 10.0 CVSS v4.0 Published 2026-03-24
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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
Out-of-bounds Write vulnerability in timeplus-io proton (base/poco/Foundation/src‎ modules). This vulnerability is associated with program files inflate.C. This issue affects proton: before 1.6.16.

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

An out-of-bounds write vulnerability exists in the inflate.C file within the base/poco/Foundation/src modules of timeplus-io proton. This file handles decompression (zlib inflate functionality), and the vulnerability allows writing beyond allocated buffer boundaries when processing compressed data. The critical CVSS score of 10 reflects the severity of memory corruption that can lead to code execution.

MitigationUpgrade proton to version 1.6.16 or later to obtain the patched inflate.C implementation. As an interim measure, avoid processing untrusted or compressed data from external sources until the upgrade is applied.

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
None
Authentication
Y
User interaction
None
Scope
N

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:A/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:N/AU:Y/R:U/V:C/RE:L/U:Amber

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. Identify proton installation and version
    Run 'proton --version' or check the installed package version using your package manager (e.g., dpkg -l | grep proton, rpm -qi proton, or brew list timeplus-io/proton/proton)
    Affected if Version is present but lower than 1.6.16
  2. Locate the inflate.C module
    Search for the inflate.C source file in the proton installation directory: find /usr -name 'inflate.C' 2>/dev/null or check the proton source code if self-compiled
    Affected if The inflate.C file exists in the proton codebase and the version is before 1.6.16
  3. Verify compression functionality is in use
    Check proton configuration files or runtime settings for compression-enabled endpoints, streams, or data ingestion paths. Look for compression-related settings in proton.yaml, config.yaml, or similar configuration files.
    Affected if Compression is enabled and the proton version is before 1.6.16
  4. Confirm version against affected range
    Compare the installed proton version number to 1.6.16. Any version starting with 1.6.15 or earlier, or any 1.5.x/1.4.x release, is in the affected range.
    Affected if Installed version is 1.6.15.x, 1.6.14.x, or any earlier minor version

The environment is affected if timeplus-io proton is installed with a version lower than 1.6.16 and the compression module (inflate.C) is actively used for decompression operations.

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.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade proton to version 1.6.16 or later to obtain the patched inflate.C implementation. As an interim measure, avoid processing untrusted or compressed data from external sources until the upgrade is applied.

Recommended fix Moderate confidence

1.6.16

  1. 1. Identify the current version of proton being used (e.g., using --version flag or checking installed package)
  2. 2. Ensure all data, configurations, and any custom scripts are backed up before upgrading
  3. 3. Upgrade proton to version 1.6.16 or later using the appropriate package manager or build system (e.g., pip install --upgrade, docker image pull, or compile from source)
  4. 4. Verify the upgrade was successful by checking the new version number
  5. 5. Restart any services or applications that use proton to ensure the patched version is loaded
Caveat No specific breaking changes mentioned in the provided vulnerability description

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,820
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4746 — 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-4746 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