LiveActive security incident?Get immediate response
CVE Record

CVE-2026-24816: Cookie Security Vulnerabilities in datavane/tis

Loop with Unreachable Exit Condition ('Infinite Loop') vulnerability in datavane tis (tis-console/src/main/java/com/qlangtech/tis/runtime/module/action modules). This vulnerability is associated with program files ChangeDomainAction.Java. This issue affects tis: before v4.3.0.

CriticalCVSS 10Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-24816 affects Datavane TIS before v4.3.0. The reported flaw is an infinite loop in a console action module, rated critical by CVSS 4.0. If your organization runs TIS, prioritize confirming the deployed version and applying the vendor patch or upgrade path.

Executive priority

High priority if Datavane TIS is in use, especially if the console is network-accessible. The CVSS score is critical, but public evidence is sparse and does not confirm real-world exploitation. Focus first on inventory, version confirmation, and upgrade planning.

Technical view

The CVE describes CWE-835 in tis-console ChangeDomainAction.java under com.qlangtech.tis.runtime.module.action. The record says TIS versions before v4.3.0 are affected. The CVSS 4.0 vector indicates network attack, low complexity, no privileges, no user interaction, and high confidentiality/integrity impacts, though the public detail is limited.

Likely exposure

Exposure is likely limited to organizations running Datavane TIS console versions before v4.3.0. Risk increases if the console is reachable from untrusted networks. The source data does not provide package identifiers, CPEs, or a complete version matrix.

Exploitation context

No CISA KEV listing is provided, and the cited sources do not state active exploitation. The CVSS vector suggests unauthenticated network reachability, but public sources do not describe exploitation mechanics. Treat internet-exposed or broadly reachable TIS consoles as higher priority for review.

Researcher notes

The public record is thin and contains a title mismatch referencing cookies while the technical description names an infinite loop. The strongest grounded facts are CWE-835, ChangeDomainAction.java, affected versions before v4.3.0, and patch reference PR 444. Avoid assuming exploitability beyond the CVSS vector.

Mitigation direction

  • Identify all Datavane TIS deployments and their versions.
  • Upgrade affected TIS instances to v4.3.0 or later if available.
  • Review Datavane pull request 444 and related release notes.
  • Restrict TIS console access to trusted networks while patching.
  • Monitor vendor guidance for any additional remediation details.

Validation and detection

  • Confirm whether each TIS instance is below v4.3.0.
  • Verify the deployed build includes the ChangeDomainAction.java fix.
  • Check whether TIS console is exposed to untrusted networks.
  • Review application logs for repeated requests or resource exhaustion symptoms.
  • Document compensating controls until all affected instances are remediated.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-835: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-24816 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
10 (4.0)
Known Exploited
No
Published

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L/S:P/AU:Y/R:U/V:C/RE:M/U:Red

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
10CVSS 4.0CriticalCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L/S:P/AU:Y/R:U/V:C/RE:M/U:Red——Primary CVE score

Vulnerability scoring details

Base CVSS 4.0 score

10Critical
CVSS 4.0 vector shape for CVE-2026-24816Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:L/SC:H/SI:H/SA:L/S:P/AU:Y/R:U/V:C/RE:M/U:Red

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
datavanetis0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-835 · source CWE mapping

Loop with Unreachable Exit Condition ('Infinite Loop')

Loop with Unreachable Exit Condition ('Infinite Loop') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.