dbcve.org
Data CatalogApplication · Talend

CVE-2023-26263

MEDIUM · 5.5 CVSS v3.1 Published 2023-04-13
Fix available
A fix is available. Upgrade to 8.0-20230110 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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
All versions of Talend Data Catalog before 8.0-20230110 are potentially vulnerable to XML External Entity (XXE) attacks in the /MIMBWebServices/license endpoint of the remote harvesting server.

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 · high confidence

Talend Data Catalog versions before 8.0-20230110 contain an XML External Entity (XXE) vulnerability in the /MIMBWebServices/license endpoint of the remote harvesting server. This allows attackers to inject malicious external entity references into XML input, potentially exposing internal files, causing denial of service, or performing server-side requests.

MitigationUpgrade to Talend Data Catalog version 8.0-20230110 or later. If immediate upgrade is not feasible, disable external entity processing in the XML parser configuration or temporarily block the vulnerable endpoint.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Data CatalogApplication
Affected:< 8.0-20230110

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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. Confirm Talend Data Catalog installation
    Locate the Talend Data Catalog installation directory or query the system inventory for this application
    Affected if Talend Data Catalog is installed on the system
  2. Determine the installed version
    Check the version metadata in the installation directory, about dialog, or system configuration files
    Affected if The installed version is earlier than 8.0-20230110
  3. Identify if the harvesting server is running
    Locate the remote harvesting server process and its exposed network ports (commonly port 8080 or configured custom port)
    Affected if The harvesting server is active and listening on a network interface
  4. Verify the vulnerable endpoint is accessible
    Confirm the /MIMBWebServices/license endpoint is reachable over HTTP/HTTPS
    Affected if The endpoint is exposed without proper access controls
  5. Inspect XML parser configuration
    Review the XML parser settings in the application configuration to check whether external entity processing is disabled
    Affected if External entity processing is enabled or not explicitly disabled in the XML parser configuration

A system is affected if it runs Talend Data Catalog version before 8.0-20230110 with the /MIMBWebServices/license endpoint accessible and external entity processing enabled in the XML parser.

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
Upgrade available Upgrade to 8.0-20230110 or later
Fixed in 8.0-20230110
Interim mitigation

Upgrade to Talend Data Catalog version 8.0-20230110 or later. If immediate upgrade is not feasible, disable external entity processing in the XML parser configuration or temporarily block the vulnerable endpoint.

Recommended fix Moderate confidence

8.0-20230110 or later

  1. 1. Identify the current Talend Data Catalog version installed in your environment
  2. 2. Download Talend Data Catalog version 8.0-20230110 or later from the official Talend download portal
  3. 3. Create a complete backup of your current Data Catalog installation, including database and configuration files
  4. 4. Follow Talend's standard upgrade documentation to apply the update to version 8.0-20230110
  5. 5. After upgrading, verify the /MIMBWebServices/license endpoint is accessible and functioning correctly
  6. 6. Confirm the XXE vulnerability is remediated by testing XML input processing in the license endpoint

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

Fix this in Data Catalog Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,480
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-26263 — 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-2023-26263 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