TooTallNate Java-WebSocket up to 1.6.1 Fragmentation Draft_6455.java processFrameContinuousAndNonFin allocation of resources
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 2.13+ |
Summary
A vulnerability marked as problematic has been reported in TooTallNate Java-WebSocket up to 1.6.1. This affects the function processFrameContinuousAndNonFin of the file Draft_6455.java of the component Fragmentation Handler. The manipulation leads to allocation of resources.
This vulnerability is traded as CVE-2026-90584. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.
The pull request to fix this issue awaits acceptance.
Details
A vulnerability was found in TooTallNate Java-WebSocket up to 1.6.1 and classified as problematic. This issue affects the function processFrameContinuousAndNonFin of the file Draft_6455.java of the component Fragmentation Handler. The manipulation with an unknown input leads to a allocation of resources vulnerability. Using CWE to declare the problem leads to CWE-770. The product allocates a reusable resource or group of resources on behalf of an actor without imposing any restrictions on the size or number of resources that can be allocated, in violation of the intended security policy for that actor. Impacted is availability.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-90584. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details as well as a public exploit are known. MITRE ATT&CK project uses the attack technique T1499 for this issue.
The exploit is available at github.com. It is declared as proof-of-concept. The pull request to fix this issue awaits acceptance.
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
Type
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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: Allocation of resourcesCWE: CWE-770 / CWE-400 / CWE-404
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
09/12/2026 Advisory disclosed09/12/2026 VulDB entry created
09/12/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 1508
Status: Not defined
Confirmation: 🔒
CVE: CVE-2026-90584 (🔒)
GCVE (CVE): GCVE-0-2026-90584
GCVE (VulDB): GCVE-100-403169
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 09/12/2026 19:45Changes: 09/12/2026 19:45 (60)
Complete: 🔍
Submitter: emiya
Cache ID: 216::103
Submit
Accepted
- Submit #913786: TooTallNate Java-WebSocket 1.6.0 Allocation of Resources Without Limits or Throttling (by emiya)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.