client-java-24.0.0.jar: 1 vulnerabilities (highest severity is: 2.4)

[mend-for-github-com]

Vulnerable Library - client-java-24.0.0.jar

Path to dependency file: /openmetadata-service/pom.xml

Path to vulnerable library: /openmetadata-service/pom.xml

Found in HEAD commit: 9d91325af8d6b6836292c4bb0ba361ab2cdf10e0

Vulnerabilities

Vulnerability	Severity	CVSS	Dependency	Type	Fixed in (client-java version)	Remediation Possible**
CVE-2026-15687	Low	2.4	client-java-24.0.0.jar	Direct	26.0.1	✅

**In some cases, Remediation PR cannot be created automatically for a vulnerability despite the availability of remediation

Details

CVE-2026-15687

Vulnerable Library - client-java-24.0.0.jar

Path to dependency file: /openmetadata-service/pom.xml

Path to vulnerable library: /openmetadata-service/pom.xml

Dependency Hierarchy:

• ❌ client-java-24.0.0.jar (Vulnerable Library)

Found in HEAD commit: 9d91325af8d6b6836292c4bb0ba361ab2cdf10e0

Found in base branch: main

Vulnerability Details

A security issue was discovered in the Kubernetes Java client library where a compromised pod may be able to create new files in arbitrary locations on the client machine executing copy operations via non-tar copyDirectoryFromPod when enableTarCompressing is false.

Publish Date: 2026-07-23

URL: CVE-2026-15687

CVSS 3 Score Details (2.4)

Base Score Metrics:

• Exploitability Metrics:
  • Attack Vector: Network
  • Attack Complexity: Low
  • Privileges Required: High
  • User Interaction: Required
  • Scope: Unchanged
• Impact Metrics:
  • Confidentiality Impact: None
  • Integrity Impact: Low
  • Availability Impact: None

For more information on CVSS3 Scores, click here.

Suggested Fix

Type: Upgrade version

Release Date: 2026-07-23

Fix Resolution: 26.0.1

In order to enable automatic remediation, please create workflow rules

---

In order to enable automatic remediation for this issue, please create workflow rules

[mend-for-github-com]

✔️ This issue was automatically closed by Mend because the vulnerable library in the specific branch(es) was either marked as ignored or it is no longer part of the Mend inventory.

[mend-for-github-com]

ℹ️ This issue was automatically re-opened by Mend because the vulnerable library in the specific branch(es) has been detected in the Mend inventory.