kronosnet Encryption Key cleartext storage in memory

CVSS Meta Temp Score
CVSS is a standardized scoring system to determine possibilities of attacks. The Temp Score considers temporal factors like disclosure, exploit and countermeasures. The unique Meta Score calculates the average score of different sources to provide a normalized scoring system.
Current Exploit Price (≈)
Our analysts are monitoring exploit markets and are in contact with vulnerability brokers. The range indicates the observed or calculated exploit price to be seen on exploit markets. A good indicator to understand the monetary effort required for and the popularity of an attack.
CTI Interest Score
Our Cyber Threat Intelligence team is monitoring different web sites, mailing lists, exploit markets and social media networks. The CTI Interest Score identifies the interest of attackers and the security community for this specific vulnerability in real-time. A high score indicates an elevated risk to be targeted for this vulnerability.
2.5$0-$5k4.17

Summaryinfo

A vulnerability marked as problematic has been reported in kronosnet. Affected by this vulnerability is an unknown functionality of the component Encryption Key Handler. The manipulation leads to cleartext storage in memory. This vulnerability is traded as CVE-2026-15811. An attack has to be approached locally. There is no exploit available.

Detailsinfo

A vulnerability was found in kronosnet (the affected version is unknown). It has been rated as problematic. This issue affects an unknown code of the component Encryption Key Handler. The manipulation with an unknown input leads to a cleartext storage in memory vulnerability. Using CWE to declare the problem leads to CWE-316. The product stores sensitive information in cleartext in memory. Impacted is confidentiality.

It is possible to read the advisory at bugzilla.redhat.com. The identification of this vulnerability is CVE-2026-15811. The exploitation is known to be difficult. Attacking locally is a requirement. The technical details are unknown and an exploit is not publicly available. The attack technique deployed by this issue is T1555 according to MITRE ATT&CK.

There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.

The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-46153). Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Name

CPE 2.3info

CPE 2.2info

CVSSv4info

VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv3info

VulDB Meta Base Score: 2.5
VulDB Meta Temp Score: 2.5

VulDB Base Score: 2.5
VulDB Temp Score: 2.5
VulDB Vector: 🔒
VulDB Reliability: 🔍

CVSSv2info

AVACAuCIA
💳💳💳💳💳💳
💳💳💳💳💳💳
💳💳💳💳💳💳
VectorComplexityAuthenticationConfidentialityIntegrityAvailability
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock
UnlockUnlockUnlockUnlockUnlockUnlock

VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍

Exploitinginfo

Class: Cleartext storage in memory
CWE: CWE-316 / CWE-312 / CWE-310
CAPEC: 🔒
ATT&CK: 🔒

Physical: Partially
Local: Yes
Remote: No

Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒

0-DayUnlockUnlockUnlockUnlock
TodayUnlockUnlockUnlockUnlock

Threat Intelligenceinfo

Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍

Countermeasuresinfo

Recommended: no mitigation known
Status: 🔍

0-Day Time: 🔒

Timelineinfo

07/20/2026 Advisory disclosed
07/20/2026 +0 days VulDB entry created
07/21/2026 +1 days VulDB entry last update

Sourcesinfo

Advisory: bugzilla.redhat.com
Status: Not defined

CVE: CVE-2026-15811 (🔒)
GCVE (CVE): GCVE-0-2026-15811
GCVE (VulDB): GCVE-100-380699
EUVD: 🔒

Entryinfo

Created: 07/20/2026 19:59
Updated: 07/21/2026 10:43
Changes: 07/20/2026 19:59 (48), 07/21/2026 10:43 (1)
Complete: 🔍
Cache ID: 216::103

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion

No comments yet. Languages: en.

Please log in to comment.

◂ PreviousOverviewNext ▸

Want to know what is going to be exploited?

We predict KEV entries!