Is this vulnerability remotely exploitable?

It can be, if an attacker can upload or otherwise provide Leica XML-based metadata to a service that processes files using Bio-Formats. In such deployments, exploitation can occur remotely via crafted input files.

What level of access does an attacker need to exploit this issue?

The attacker needs the ability to influence or supply metadata files that Bio-Formats will parse—commonly through file upload, shared storage, or automated ingestion mechanisms. No direct shell or API access to the host is required beyond that capability.

What is the safest general fix pattern for this kind of vulnerability?

The safest pattern is to enforce secure XML parser configuration everywhere: disable external entities, external DTDs, and external resource loading by default, and process XML in a context with restricted privileges and minimal filesystem/network access.

Severity:

HIGH RISK

(7.1)

XML External Entity (XXE) (CWE-611) in Bio-Formats Leica Metadata Parser

CVE-2026-22186

Published:

Jan 7, 2026

Status:

Modified

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

XML External Entity (XXE)

CWE:

CWE-611

Impact:

Server-Side Request Forgery (SSRF) and Local File Disclosure

Severity:

HIGH RISK

(7.1)

CVSS Version:

3.1

Vulnerability Type

Category:

XML External Entity (XXE)

CWE:

CWE-611

Impact:

Server-Side Request Forgery (SSRF) and Local File Disclosure

Severity:

HIGH RISK

(7.1)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

XML External Entity (XXE) (CWE-611) in Bio-Formats Leica Metadata Parser

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal