CVE-2026-4751 | tmate-io tmate up to 2.3.x null pointer dereference
VulDBArchived Mar 24, 2026✓ Full text saved
A vulnerability categorized as problematic has been discovered in tmate-io tmate up to 2.3.x . This vulnerability affects unknown code. Executing a manipulation can lead to null pointer dereference. This vulnerability is handled as CVE-2026-4751 . The attack can be executed remotely. There is not any exploit available. It is advisable to upgrade the affected component.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-352697 · CVE-2026-4751 · GCVE-0-2026-4751
TMATE-IO TMATE UP TO 2.3.X NULL POINTER DEREFERENCE
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
5.2 $0-$5k 2.67+
Summaryinfo
A vulnerability identified as problematic has been detected in tmate-io tmate up to 2.3.x. This issue affects some unknown processing. The manipulation leads to null pointer dereference. This vulnerability is uniquely identified as CVE-2026-4751. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Detailsinfo
A vulnerability was found in tmate-io tmate up to 2.3.x and classified as problematic. This issue affects some unknown functionality. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. Impacted is availability. The summary by CVE is:
NULL Pointer Dereference vulnerability in tmate-io tmate.This issue affects tmate: before 2.4.0.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-4751 since 03/24/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Neither technical details nor an exploit are publicly available.
Upgrading to version 2.4.0 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
tmate-io
Name
tmate
Version
2.0
2.1
2.2
2.3
Website
Product: https://github.com/tmate-io/tmate/
CPE 2.3info
🔒
🔒
🔒
CPE 2.2info
🔒
🔒
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 5.3
VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.3
CNA Vector (GovTech CSG): 🔒
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: Null pointer dereference
CWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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: tmate 2.4.0
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-4751 (🔒)
GCVE (CVE): GCVE-0-2026-4751
GCVE (VulDB): GCVE-100-352697
Entryinfo
Created: 03/24/2026 07:37
Changes: 03/24/2026 07:37 (64)
Complete: 🔍
Cache ID: 99:F7C:101
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸