vthibault tga-js up to 1.1.1 TgaLoader src/tga.js _decodeRLE memory allocation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.0 | $0-$5k | 0.89+ |
Summary
A vulnerability classified as problematic has been found in vthibault tga-js up to 1.1.1. Impacted is the function _decodeRLE of the file src/tga.js of the component TgaLoader. Performing a manipulation results in memory allocation.
This vulnerability is identified as CVE-2026-134853. The attack can be initiated remotely. Additionally, an exploit exists.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability classified as problematic has been found in vthibault tga-js up to 1.1.1. This affects the function _decodeRLE of the file src/tga.js of the component TgaLoader. The manipulation with an unknown input leads to a memory allocation vulnerability. CWE is classifying the issue as CWE-789. The product allocates memory based on an untrusted, large size value, but it does not ensure that the size is within expected limits, allowing arbitrary amounts of memory to be allocated. This is going to have an impact on availability.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-134853. The exploitability is told to be easy. It is possible to initiate the attack remotely. No form of authentication is needed for exploitation. Technical details and a public exploit are known.
The exploit is shared for download at github.com. It is declared as proof-of-concept. The project was informed of the problem early through an issue report but has not responded yet.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 5.0
VulDB Base Score: 5.3
VulDB Temp Score: 5.0
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: Memory allocationCWE: CWE-789 / CWE-770 / CWE-400
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
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
11/22/2026 Advisory disclosed11/22/2026 VulDB entry created
11/22/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CNA: VulDB
CVE: CVE-2026-134853 (🔒)
GCVE (CVE): GCVE-0-2026-134853
GCVE (VulDB): GCVE-100-442161
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 11/22/2026 19:56Changes: 11/22/2026 19:56 (57)
Complete: 🔍
Submitter: saidkarimov_16
Cache ID: 216::103
Submit
Accepted
- Submit #1054621: vthibault tga-js 1.1.1 Resource Consumption (by saidkarimov_16)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.