dbcve.org
Data CatalogApplication · Talend

CVE-2023-26264

MEDIUM · 5.5 CVSS v3.1 Published 2023-04-13
Fix available
A fix is available. Upgrade to 8.0-20220907 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-20220907 are potentially vulnerable to XML External Entity (XXE) attacks in the license parsing code.

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

All versions of Talend Data Catalog before 8.0-20220907 contain an XML External Entity (XXE) vulnerability in the license parsing code. The application parses XML license files without properly disabling external entity references, allowing attackers to potentially access local files or perform SSRF attacks through malicious XML input.

MitigationUpgrade Talend Data Catalog to version 8.0-20220907 or later. Additionally, ensure XML parsers used in license processing are configured to disable external entities and DTD processing as a defense-in-depth measure.

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-20220907

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. Identify Talend Data Catalog installation
    Search for Talend Data Catalog installation directories or check common installation paths such as /opt/talend, C:\Program Files\Talend, or the application server webapps directory where Talend may be deployed.
    Affected if Talend Data Catalog is present in the environment
  2. Determine installed version
    Locate the version file or metadata within the Talend installation directory. Common locations include version.info, build.properties, or the META-INF/MANIFEST.MF file within the application WAR/EAR files. Alternatively, access the application's 'About' or 'System Information' page if the web interface is accessible.
    Affected if The discovered version is lower than 8.0-20220907
  3. Locate license processing component
    Identify the license management module within the Talend Data Catalog installation. Look for components handling .lic, .xml license files, or license upload/import functionality. This is typically found in the administration or system configuration interfaces.
    Affected if License parsing functionality exists and processes XML-based license files
  4. Verify XML parser configuration
    Inspect the application configuration or source code related to license XML parsing. Check if external entity processing is explicitly disabled in the XML parser settings (look for settings such as 'setFeature("http://apache.org/xml/features/disallow-doctype-decl", true)' or similar XXE protections).
    Affected if The XML parser used in license processing does not have external entity references and DTD processing disabled

The environment is affected if Talend Data Catalog is installed with a version lower than 8.0-20220907 and the license parsing feature processes XML files without XXE protections.

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-20220907 or later
Fixed in 8.0-20220907
Interim mitigation

Upgrade Talend Data Catalog to version 8.0-20220907 or later. Additionally, ensure XML parsers used in license processing are configured to disable external entities and DTD processing as a defense-in-depth measure.

Recommended fix High confidence

8.0-20220907 or later

  1. Verify current Talend Data Catalog version by checking the system administration console or using the version command
  2. Review the Talend Data Catalog 8.0-20220907 release notes for new features, deprecated functionality, and any known migration requirements
  3. Create a full backup of the existing Data Catalog installation including configuration files, metadata repository, and any custom scripts
  4. Export all metadata, data models, and business glossaries if applicable
  5. Stop all Data Catalog services and application servers
  6. Install Talend Data Catalog version 8.0-20220907 or later following the standard installation documentation
  7. Restore configuration from the backup or reconfigure as needed for the new version
  8. Start the Data Catalog services and verify the application launches successfully
Caveat Review release notes for any deprecated features or breaking changes between your current version and 8.0-20220907; plan for potential configuration adjustments and regression testing

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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