dbcve.org
Unrestricted File UploadWeakness · CWE-434

CVE-2026-24815

CRITICAL · 10.0 CVSS v4.0 Published 2026-01-27
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Unrestricted Upload of File with Dangerous Type, Deserialization of Untrusted Data vulnerability in datavane tis (tis-plugin/src/main/java/com/qlangtech/tis/extension/impl modules). This vulnerability is associated with program files XmlFile.Java. This issue affects tis: before v4.3.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

File upload and XML deserialization vulnerability in tis-plugin's XmlFile.java allows attackers to upload malicious files and potentially execute arbitrary code through unsafe deserialization of untrusted XML data.

MitigationUpgrade to tis v4.3.0 or later which implements proper file type validation and secure XML deserialization; restrict or disable the file upload functionality until patched.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
Authentication
Y
User interaction
None
Scope
P

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:P/AU:Y/R:U/V:C/RE:M/U:Red

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if datavane tis platform is installed
    Locate tis installation directories, look for tis-plugin or tis-core JAR files, or check for tis configuration directories on the system
    Affected if The datavane tis platform software is found on the system
  2. Determine the installed tis platform version
    Check the tis platform version file, JAR manifest, or version metadata within the tis installation directory; compare against v4.3.0
    Affected if The installed version is any version prior to v4.3.0
  3. Verify the XmlFile handler is present
    Inspect the tis-plugin module for XmlFile.java or compiled XmlFile class; check if the XmlFile handler is deployed in the plugins directory
    Affected if The XmlFile.java handler exists in the tis-plugin module
  4. Confirm file upload functionality is enabled for XmlFile
    Review tis configuration files for XmlFile upload settings; check if upload endpoints are not disabled or restricted
    Affected if XmlFile upload capability is enabled and accessible without strong restrictions
  5. Check deserialization controls for the XmlFile handler
    Inspect tis security configuration for deserialization allowlists or safelist settings related to XmlFile processing
    Affected if No strict allowlist-based deserialization controls are configured for the XmlFile handler

A system is affected if it runs datavane tis platform version prior to v4.3.0 with the XmlFile handler enabled and accessible without strict deserialization controls.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Patch available Apply the vendor patch
Vendor patch github.com →
Interim mitigation

Upgrade to tis v4.3.0 or later which implements proper file type validation and secure XML deserialization; restrict or disable the file upload functionality until patched.

Recommended fix High confidence

tis v4.3.0

  1. 1. Back up the current tis installation including all configuration files and any custom plugins
  2. 2. Review the tis v4.3.0 release notes and changelog to understand all changes in this release
  3. 3. Upgrade tis to version v4.3.0 or later using your deployment method (e.g., package manager, Docker, or manual installation)
  4. 4. After upgrade, verify that the tis service starts successfully and all dependent services are operational
  5. 5. Test the file upload functionality (specifically XmlFile operations) to ensure legitimate uploads still work correctly
  6. 6. Verify that the vulnerability is patched by attempting to upload files with dangerous extensions/types - these should now be blocked
Caveat Review release notes for v4.3.0 as minor configuration or API changes may exist; test in staging before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the patch applied

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-24815 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-24815 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data