declare-lab tango up to 34ecd38898508017ca937508a047b42817d2b070 Model Loading tango.py Tango.__init__ scheduler_name input validation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.24+ |
Summary
A vulnerability was found in declare-lab tango up to 34ecd38898508017ca937508a047b42817d2b070. It has been declared as critical. The affected element is the function Tango.__init__ of the file tango.py of the component Model Loading. Executing a manipulation of the argument scheduler_name can lead to input validation.
This vulnerability appears as CVE-2026-133490. The attack may be performed from remote. In addition, an exploit is available.
This product utilizes a rolling release system for continuous delivery, and as such, version information for affected or updated releases is not disclosed.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability was found in declare-lab tango up to 34ecd38898508017ca937508a047b42817d2b070. It has been declared as critical. This vulnerability affects the function Tango.__init__ of the file tango.py of the component Model Loading. The manipulation of the argument scheduler_name with an unknown input leads to a input validation vulnerability. The CWE definition for the vulnerability is CWE-20. The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. As an impact it is known to affect confidentiality, integrity, and availability.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-133490. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. Technical details and also a public exploit are known.
It is possible to download the exploit 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.
Once again VulDB remains the best source for vulnerability data.
Product
Vendor
Name
Version
Website
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.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: Input validationCWE: CWE-20
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/19/2026 Advisory disclosed11/19/2026 VulDB entry created
11/19/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 62
Status: Confirmed
CNA: VulDB
CVE: CVE-2026-133490 (🔒)
GCVE (CVE): GCVE-0-2026-133490
GCVE (VulDB): GCVE-100-440908
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 11/19/2026 23:02Changes: 11/19/2026 23:02 (60)
Complete: 🔍
Submitter: Dem000
Cache ID: 216::103
Submit
Accepted
- Submit #1049346: declare-lab Tango commit 34ecd38898508017ca937508a047b42817d2b070 (master HEAD) Improper Input Validation (by Dem000)
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.