CVE-2026-4746 | timeplus-io proton up to 1.6.15 src out-of-bounds write
VulDBArchived Mar 24, 2026✓ Full text saved
A vulnerability has been found in timeplus-io proton up to 1.6.15 and classified as critical . The affected element is an unknown function of the file base/poco/Foundation/src . Performing a manipulation results in out-of-bounds write. This vulnerability is reported as CVE-2026-4746 . The attack is possible to be carried out remotely. No exploit exists. The affected component should be upgraded.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-352678 · CVE-2026-4746 · GCVE-0-2026-4746
TIMEPLUS-IO PROTON UP TO 1.6.15 SRC OUT-OF-BOUNDS WRITE
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
7.0 $0-$5k 2.10+
Summaryinfo
A vulnerability was found in timeplus-io proton up to 1.6.15 and classified as critical. The impacted element is an unknown function of the file base/poco/Foundation/src. Executing a manipulation can lead to out-of-bounds write. This vulnerability appears as CVE-2026-4746. The attack may be performed from remote. There is no available exploit. It is suggested to upgrade the affected component.
Detailsinfo
A vulnerability has been found in timeplus-io proton up to 1.6.15 and classified as critical. This vulnerability affects an unknown code of the file base/poco/Foundation/src. The manipulation with an unknown input leads to a out-of-bounds write vulnerability. The CWE definition for the vulnerability is CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
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.
The advisory is available at github.com. This vulnerability was named CVE-2026-4746 since 03/24/2026. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Technical details are known, but there is no available exploit.
It is declared as attacked.
Upgrading to version 1.6.16 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Productinfo
Vendor
timeplus-io
Name
proton
Version
1.6.0
1.6.1
1.6.2
1.6.3
1.6.4
1.6.5
1.6.6
1.6.7
1.6.8
1.6.9
1.6.10
1.6.11
1.6.12
1.6.13
1.6.14
1.6.15
Website
Product: https://github.com/timeplus-io/proton/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3info
VulDB Meta Base Score: 7.3
VulDB Meta Temp Score: 7.0
VulDB Base Score: 7.3
VulDB Temp Score: 7.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
Vector Complexity Authentication Confidentiality Integrity Availability
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
Unlock Unlock Unlock Unlock Unlock Unlock
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploitinginfo
Class: Out-of-bounds write
CWE: CWE-787 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Attacked
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: Upgrade
Status: 🔍
0-Day Time: 🔒
Upgrade: proton 1.6.16
Patch: github.com
Timelineinfo
03/24/2026 Advisory disclosed
03/24/2026 +0 days CVE reserved
03/24/2026 +0 days VulDB entry created
03/24/2026 +0 days VulDB entry last update
Sourcesinfo
Product: github.com
Advisory: github.com
Status: Confirmed
CVE: CVE-2026-4746 (🔒)
GCVE (CVE): GCVE-0-2026-4746
GCVE (VulDB): GCVE-100-352678
Entryinfo
Created: 03/24/2026 07:27
Changes: 03/24/2026 07:27 (75)
Complete: 🔍
Cache ID: 99:760:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸