CVE-2025-68280

Improper Restriction of XML External Entity Reference vulnerability in Apache SIS.

It is possible to write XML files in such a way that, when parsed by Apache SIS, an XML file reveals to the attacker the content of a local file on the server running Apache SIS. This vulnerability impacts the following SIS services:

• Reading of GeoTIFF files having the GEO_METADATA tag defined by the Defense Geospatial Information Working Group (DGIWG).

• Parsing of ISO 19115 metadata in XML format.

• Parsing of Coordinate Reference Systems defined in the GML format.

• Parsing of files in GPS Exchange Format (GPX).

This issue affects Apache SIS from versions 0.4 through 1.5 inclusive. Users are recommended to upgrade to version 1.6, which will fix the issue. In the meantime, the security vulnerability can be avoided by launching Java with the javax.xml.accessExternalDTD system property sets to a comma-separated list of authorized protocols. For example:

java -Djavax.xml.accessExternalDTD="" ...

An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs. Typical impact: local file disclosure, server-side request forgery, or denial of service.

CVE-2025-68280 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.6); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2025-68280? CVE-2025-68280 is a medium-severity XML external entity injection (XXE) vulnerability in org.apache.sis.core:sis-metadata (maven), affecting versions >= 0.4, < 1.6. It is fixed in 1.6. An XML parser processes external entity references in untrusted input, causing the server to fetch internal resources or remote URLs.
2. How severe is CVE-2025-68280? CVE-2025-68280 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of org.apache.sis.core:sis-metadata are affected by CVE-2025-68280? org.apache.sis.core:sis-metadata (maven) versions >= 0.4, < 1.6 is affected.
4. Is there a fix for CVE-2025-68280? Yes. CVE-2025-68280 is fixed in 1.6. Upgrade to this version or later.
5. Is CVE-2025-68280 exploitable, and should I be worried? Whether CVE-2025-68280 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-68280 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-68280? Upgrade org.apache.sis.core:sis-metadata to 1.6 or later.