tango input validation flaw enables tampering in model loading
- Exploited
- Proof of concept public, per CISA
- Fix
- No fix listed
- Who is exposed
- Not reported
Summary
Improper input validation in the Tango.__init__ function of tango.py, in the Model Loading component of the declare-lab tango project, lets an attacker manipulate the scheduler_name argument. The attack can be carried out remotely and without logging in, but it requires a user to take some action.
Written by a model
Original description
A vulnerability was detected in declare-lab tango up to 34ecd38898508017ca937508a047b42817d2b070. Impacted is the function Tango.__init__ of the file tango.py of the component Model Loading. Performing a manipulation of the argument scheduler_name results in improper input validation. The attack is possible to be carried out remotely. The exploit is now public and may be used. This product adopts a rolling release strategy to maintain continuous delivery. Therefore, version details for affected or updated releases cannot be specified. The project was informed of the problem early through an issue report but has not responded yet.
What to do
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-133490 (declare-lab tango Model Loading tango.py Tango.init input validation), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-133490 (entry last updated 2026-11-20):
Affected:
- declare-lab tango: version range not reported
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-133490 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-133490 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/declare-lab/tango/issues/62
- https://vuldb.com/vuln/440908
- https://vuldb.com/vuln/440908/cti
- https://vuldb.com/cve/CVE-2026-133490
- https://vuldb.com/submit/1049346
- https://github.com/declare-lab/tango/
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-133490
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-133490"}.Affected versions
- declare-lab tangoVersion range not reported
cve.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
- Reach?/20Unknown. No tracked technology or package matched
- Severity5.3/10CVSS 5.3
- No patch5/5No patch listed yet
What would change the score
- Would score about 72 if added to CISA KEV
- Would score about 67 if CISA's SSVC rates exploitation active
- Would score about 47 if advisories confirm default setups are exposed
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: partial
- Record last updated
Evidence 9
| Kind | Source |
|---|---|
| CVE record 2Establishes: The identifier and description. | |
| Record | CVE List · CVE-2026-133490 |
| Record | NVD · CVE-2026-133490 |
| Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub). | |
| Exploit | GitHub · user-attachments/files · 33756104/poc.zip |
| Other links 6 | |
| Advisory | VulDB · Advisory #440908 |
| Advisory | VulDB · Threat intelligence #440908 |
| Advisory | VulDB · CVE-2026-133490 record |
| Advisory | VulDB · Submission #1049346 |
| Report | GitHub · declare-lab/tango · Issue #62 |
| Repository | GitHub · declare-lab/tango · Repository |
Related
- CVE-2026-77367Daptin: Unauthenticated SQL Injection via the `sort` query parameter on every entity list endpoint
- CVE-2026-115560Session serializer mismatch can lead to remote code execution
- CVE-2026-115407In `github.com/eclipse-keypont/crypto11/v2` versions `<= 2.0.0-rc8` (and the deprecated v1 module paths…
- CVE-2026-62320Netatalk: afpd unauthenticated DSI request smuggling via silent dsi_len truncation in dsi_tcp_open()
- CVE-2026-131199SPL Injection through the Risk Event Timeline REST API in Splunk Enterprise Security
- CVE-2026-104199aMQTT: Inefficient Regular Expression Complexity and Uncontrolled Resource Consumption and Improper Input Validation
No corrections so far. Something wrong on this page? Report an error.