| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.87 |
Summary
A vulnerability identified as critical has been detected in Telegram rlottie. The affected element is an unknown function. Performing a manipulation results in numeric truncation error. This vulnerability was named CVE-2026-111105. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability classified as critical has been found in Telegram rlottie (affected version not known). This affects some unknown functionality. The manipulation with an unknown input leads to a numeric truncation error vulnerability. CWE is classifying the issue as CWE-197. Truncation errors occur when a primitive is cast to a primitive of a smaller size and data is lost in the conversion. This is going to have an impact on confidentiality, integrity, and availability.
This vulnerability is uniquely identified as CVE-2026-111105. The exploitability is told to be easy. It is possible to initiate the attack remotely. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/15/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 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: 🔍
Exploiting
Class: Numeric truncation errorCWE: CWE-197 / CWE-189
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 Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
10/15/2026 Advisory disclosed10/15/2026 VulDB entry created
10/15/2026 VulDB entry last update
Sources
Status: Not definedCVE: CVE-2026-111105 (🔒)
GCVE (CVE): GCVE-0-2026-111105
GCVE (VulDB): GCVE-100-420723
Entry
Created: 10/15/2026 18:50Changes: 10/15/2026 18:50 (46)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.