Skip to main content

CVE-2026-133490declare-lab tango improper input validation

Low priorityLow2.1EPSS not scored yet

CVE-2026-133490 is a improper input validation in declare-lab tango, rated low (2.1 on CVSS 4.0).

Why this priority: Low severity, with no exploitation signal.

Published · Updated · NVD status: Deferred

What it is

The software trusts input it should check, so crafted values reach code that assumes they are well formed.

How it is reached

An attacker can exploit it over the network, without an account, but someone has to act first, such as opening a file or following a link.

What an attacker gains

The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker drive the component into behaviour its authors did not intend.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. No fixed version is listed yet. Find every place declare-lab tango runs, watch the references for a fix, and plan a replacement if it is no longer supported.
  2. While there is no fix, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
  3. Warn the people who use it, and filter files and links on the way in.

Description from NVD

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 this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Interfaces that accept external input. The flaw sits at the input boundary of the affected component.

Trust boundaries in play

  • Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
  • People who open files and links. Mail, chat and browsers are the delivery path.
  • At the input boundary of the affected component. An attacker who crosses it can drive the component into behaviour its authors did not intend.

Questions to answer about your own systems

  • Where does declare-lab tango run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • What can it reach once compromised: which data stores, secrets and services?

14-day free trial

Understand how your systems connect.

See your services, dependencies and trust boundaries in one place, with evidence from your connected environment.

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.