Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious GML/WKT/Landsat file
-
DeliveryEmbed reference to local file path
-
ExploitVictim app parses file in Apache SIS
-
ExecutionSIS opens referenced out-of-scope file
-
ImpactLimited read before parse error halts
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Path canonicalization, traversal prevention
MITRE ATT&CK
2 techniques across 2 tactics: Discovery, Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires a victim to process an attacker-controlled data file using Apache SIS 0.7-1.6 in one of the affected parsing paths: GML containing xlink:href attributes referencing other GML files, WKT containing parameter elements for NADCON/NTv2/RGF93 datum-shift grids, or a Landsat scene referencing per-band GeoTIFF files. The crafted file must embed a reference to an out-of-scope local path. Exploitation is strongly limited because the referenced target must be in the expected geospatial format and reading stops at the first parsing error, so Apache rates sensitive-data leakage as unlikely; it also depends on the application ingesting untrusted geospatial data, which does not occur in default/trusted-input workflows. |
| Impact | This is a low-priority issue despite the absence of a vendor CVSS score. The input provides no CVSS vector, no EPSS probability, no CISA KEV listing, and no public exploit reference, and the vuln.today Decision label is 'monitor' - a consistent set of signals all pointing to low real-world urgency. The flaw is a path-traversal / external-file-reference issue (CWE-22) in which Apache SIS (0.7 through 1.6) follows file references embedded in geospatial data files without restricting their location, allowing a crafted data file to point to a local file path. Critically, Apache itself notes the impact is self-limiting: a referenced file must conform to a specific expected format (GML, NADCON/NTv2/RGF93 grids, or GeoTIFF) and parsing stops at the first error, so the vendor assesses sensitive-information leakage as 'unlikely.' Because no CVSS vector is supplied, authentication requirements are not confirmed from available data and must not be inferred from the description text. Exploitation is also not autonomous - it requires a victim application to process an attacker-supplied data file. No signals conflict here; all available data agrees this is a defense-in-depth fix rather than an actively pressing threat. |
| Exploit ScenarioDerived | An attacker crafts a malicious GML, WKT, or Landsat scene file whose embedded references (xlink:href, datum-shift grid parameters, or GeoTIFF band paths) point to a local file path outside the intended directory, then gets a victim application using Apache SIS to open it. SIS follows the reference and attempts to read the targeted file, though parsing halts at the first format error, limiting what can be extracted. No public exploit identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 26, 2026
Path traversal in Apache SIS 0.7 through 1.6 allows a crafted geospatial data file to make the library open local files referenced through embedded links, regardless of where those files reside. Victims are affected only when they feed untrusted data into one of three parsing paths - GML with xlink:href attributes, WKT with NADCON/NTv2/RGF93 datum-shift grid parameters, or a Landsat scene pointing at per-band GeoTIFF files - and the exposed impact is limited to low confidentiality loss because the target must still match an expected geospatial format and parsing aborts at the first error. No CISA KEV listing or public exploit code was identified at time of analysis, and the vendor rates sensitive-information leakage as unlikely; the fix is Apache SIS 1.7, which confines references to the referencing file's directory or a predetermined grid directory.
RemediationAI
Upgrade to Apache SIS 1.7, which fixes the issue by restricting referenced paths to the same directory as the file containing the references, or to a predetermined directory for datum shift grids; the vendor advisory at https://lists.apache.org/thread.html/j43dd1okv97o0qygbox381l01rsszsln should be consulted for the release details. Until the upgrade is deployed, the practical compensating control is to avoid processing geospatial files from untrusted or third-party sources - GML, WKT with datum-shift parameters, and Landsat scenes in particular - with an SIS 0.7-1.6 based application; the trade-off is that this breaks any legitimate workflow that ingests externally supplied geospatial data, so it is best scoped to ingestion endpoints rather than applied library-wide. Note that upgrading is the complete fix; partial input screening does not restore the directory-containment guarantee that 1.7 provides.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Apache SIS is a Java library for geospatial data, and the flaw is a CWE-22 path traversal in its file-reference resolution: when a data file names other files, the library opened the resolved path without checking that it stayed inside an allowed directory. Three formats are implicated - Geographic Markup Language documents whose xlink:href attributes point to other GML files, Well Known Text records carrying parameter elements for datum-shift grids in NADCON, NTv2 or RGF93 formats, and Landsat scenes whose metadata lists a file per band in GeoTIFF. The root cause is missing canonicalization and containment validation of the resolved path; version 1.7 adds the restriction, limiting references to the same directory as the file containing the link or, for datum-shift grids, a predetermined directory. The trigger path is described by the vendor, but practical leakage is strongly constrained because the referenced target must parse as one of the expected geospatial formats and reading halts at the first parsing error, so an attacker cannot simply exfiltrate arbitrary text. Our assessed vector, CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N, reflects that a user must open or process the attacker-supplied file through an application built on Apache SIS; default or trusted-input workflows are not exposed.
Know when Apache Sis gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
A crafted data file must be supplied and opened (UI:R), the traversal itself is simple (AC:L), and confidentiality impact is only low because the target must match an expected format and parsing stops at the first error (C:L, I/A:N).
Primary rating from Vendor (apache).
DescriptionCVE.org
This issue affects Apache SIS from version 0.7 through 1.6 inclusive. When a data file contains links to other files, Apache SIS opened these files regardless their paths. It was possible, for example, to specify a path to a local file. However, these files were always expected to be in some specific formats and the reading stops at the first parsing error, which makes this vulnerability unlikely to leak sensitive information. The impacted formats are:
- Geographic Markup Language (GML) with
xlink:hrefattributes for other files in GML format. - Well Known Text (WKT) with parameter elements for datum shift grids in NADCON, NTv2 or RGF93 formats.
- Landsat scene with paths to files for each band in the GeoTIFF format.
Users are recommended to upgrade to version 1.7, which fixes the issue by restricting the paths to the same directory as the file containing the references to other files, or to a predetermined directory for datum shift grids.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
Attack Technique
Path traversal exploits occur when applications use user-controlled input to construct file system paths without proper validation.
EUVD-2026-109943
GHSA-rqv2-hw62-wr72
CVE.org
EPSS
Exploit-DB