How severe is GHSA-826p-4gcg-35vw?

GHSA-826p-4gcg-35vw has a CVSS score of 9.9/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-826p-4gcg-35vw?

GHSA-826p-4gcg-35vw affects the following packages: org.geotools:gt-xsd-core (Maven), org.geotools:gt-xsd-core (Maven), org.geotools:gt-xsd-core (Maven), org.geotools:gt-wfs-ng (Maven), org.geotools:gt-wfs-ng (Maven), org.geotools:gt-wfs-ng (Maven), org.geotools:gt-xsd-core (Maven), org.geotools:gt-wfs-ng (Maven). Ecosystems affected: Maven.

How do I fix GHSA-826p-4gcg-35vw?

Update org.geotools:gt-xsd-core to 33.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-826p-4gcg-35vw is resolved across your whole dependency graph.

How do I detect GHSA-826p-4gcg-35vw in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.geotools:gt-xsd-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-826p-4gcg-35vw if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-826p-4gcg-35vw?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-826p-4gcg-35vw can be triaged on real exposure rather than presence alone.

Is GHSA-826p-4gcg-35vw actively exploited in the wild?

No public exploit code has been indexed for GHSA-826p-4gcg-35vw yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-826p-4gcg-35vw published, and has it been updated?

GHSA-826p-4gcg-35vw was published on June 9, 2025 and was last updated on February 4, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

CRITICAL severity

GHSA-826p-4gcg-35vw — gt-xsd-core

CRITICAL

GHSA-826p-4gcg-35vw is a critical-severity (CVSS 9.9) vulnerability in org.geotools:gt-xsd-core. A fix is available for org.geotools:gt-xsd-core — see the affected versions and patch details below.

GeoTools has XML External Entity (XXE) Processing Vulnerability in XSD schema handling

Published

Jun 9, 2025

Updated

Feb 4, 2026

Affected

8 pkgs

Patched

8 / 8

Exploits

None indexed

Exploitation data as of Feb 4, 2026 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

8 pkgs affected

☕org.geotools:gt-xsd-core☕org.geotools:gt-xsd-core☕org.geotools:gt-xsd-core☕org.geotools:gt-wfs-ng☕org.geotools:gt-wfs-ng☕org.geotools:gt-wfs-ng☕org.geotools:gt-xsd-core☕org.geotools:gt-wfs-ng

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

Summary

GeoTools Schema class use of Eclipse XSD library to represent schema data structure is vulnerable to XML External Entity (XXE) exploit.

Impact

This impacts whoever exposes XML processing with gt-xsd-core involved in parsing, when the documents carry a reference to an external XML schema. The gt-xsd-core Schemas class is not using the EntityResolver provided by the ParserHandler (if any was configured).

This also impacts users of gt-wfs-ng DataStore where the ENTITY_RESOLVER connection parameter was not being used as intended.

Resolution

GeoTools API change allows EntityResolver to be supplied to the following methods:

Schemas.parse( location, locators, resolvers, uriHandlers, entityResolver);
Schemas.findSchemas(Configuration configuration, EntityResolver entityResolver);

With this API change the gt-wfs-ng WFS DataStore ENTITY_RESOLVER parameter is now used.

Reference

GHSA-jj54-8f66-c5pc: Describes the impact of the gt-xsd-core vulnerability on the GeoServer WFS protocol, resulting in both Service Side Request Forgery (SSRF) and Out-of-Band (OOB) data exfiltration of local files.
GHSA-2p76-gc46-5fvc: Describes the impact of the gt-wfs-ng and gt-xsd-core vulnerability on the GeoNetwork WFS Index functionality.

Affected Packages

8 total 8 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.geotools:gt-xsd-core`	≥ 33.0&&< 33.1	33.1`org.geotools:gt-xsd-core:33.1`
☕Maven	`org.geotools:gt-xsd-core`	≥ 32.0&&< 32.3	32.3`org.geotools:gt-xsd-core:32.3`
☕Maven	`org.geotools:gt-xsd-core`	≥ 29.0&&< 31.7	31.7`org.geotools:gt-xsd-core:31.7`
☕Maven	`org.geotools:gt-wfs-ng`	≥ 33.0&&< 33.1	33.1`org.geotools:gt-wfs-ng:33.1`
☕Maven	`org.geotools:gt-wfs-ng`	≥ 32.0&&< 32.3	32.3`org.geotools:gt-wfs-ng:32.3`
☕Maven	`org.geotools:gt-wfs-ng`	≥ 29.0&&< 31.7	31.7`org.geotools:gt-wfs-ng:31.7`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.geotools:gt-xsd-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.geotools:gt-xsd-core to 33.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-826p-4gcg-35vw is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-826p-4gcg-35vw can be triaged on real exposure rather than presence alone.

Tailored to GHSA-826p-4gcg-35vw. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary GeoTools Schema class use of Eclipse XSD library to represent schema data structure is vulnerable to XML External Entity (XXE) exploit. ### Impact This impacts whoever exposes XML processing with ``gt-xsd-core`` involved in parsing, when the documents carry a reference to an external XML schema. The ``gt-xsd-core`` Schemas class is not using the EntityResolver provided by the ParserHandler (if any was configured). This also impacts users of ``gt-wfs-ng`` DataStore where the ENTITY_RESOLVER connection parameter was not being used as intended. ### Resolution GeoTools API change

O3 Security · Impact-Aware SCA

Is GHSA-826p-4gcg-35vw in your dependencies?

O3 Security finds GHSA-826p-4gcg-35vw across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works