CVE-2026-58400: GeoNetwork vulnerable to Remote Code Execution via unsafe Saxon XSLT processor configuration in formatter
GeoNetwork is a catalog application to manage spatially referenced resources. Prior to versions 4.4.12 and 4.2.17, the Saxon XSLT processor used to render formatters is configured without secure processing (`FEATURE_SECURE_PROCESSING`) and without disabling Java extension functions (`ALLOW_EXTERNAL_FUNCTIONS`). Any stylesheet loaded by GeoNetwork can therefore invoke
`java.lang.Runtime.exec()` or `java.lang.ProcessBuilder` directly, achieving arbitrary command execution as the GeoNetwork process user. A user with sufficient privileges to upload a formatter can deliver a `.xsl` file containing Java extension call that execute arbitrary OS commands with the privileges of the GeoNetwork process. The issue is patched in GeoNetwork versions 4.4.12 and 4.2.17.
Security readout for executives and security teams
Plain-English summary
A privileged GeoNetwork user who can upload a formatter could make the server run arbitrary operating-system commands. Successful abuse could expose or alter catalog data, disrupt service, and potentially enable broader compromise depending on the GeoNetwork process permissions.
Executive priority
Treat affected deployments as an urgent remediation priority, especially where formatter administration is delegated or privileged accounts may be exposed. The high privilege requirement reduces immediate reachability but does not limit impact after successful abuse.
Technical view
Affected GeoNetwork releases configure the Saxon XSLT processor without secure processing and without disabling Java extension functions. A malicious uploaded XSL stylesheet can consequently invoke Java process-execution functionality as the GeoNetwork process user. The assigned CVSS 3.1 score is 9.1, with high privileges required.
Likely exposure
Exposure applies to core-geonetwork versions from 4.3.0 through 4.4.11 and versions earlier than 4.2.17. Practical exposure requires an account with sufficient privileges to upload a formatter. The bundle does not establish that ordinary unauthenticated internet users can reach this capability.
Exploitation context
The supplied vulnerability description requires high privileges, needs no user interaction, and identifies a network attack vector. GeoNetwork is not listed as KEV in the bundle, and no supplied evidence confirms active exploitation. Compromise of a privileged account would make exploitation materially more plausible.
Researcher notes
The bundle contains a material discrepancy: the referenced news title calls this unauthenticated RCE, while the supplied vulnerability description requires formatter-upload privileges and the CVSS vector specifies high privileges. Until authoritative evidence establishes another path, unauthenticated exploitation should be considered unproven.
Mitigation direction
Upgrade 4.4 deployments to 4.4.12 or a later vendor-supported release.
Upgrade 4.2 deployments to 4.2.17 or a later vendor-supported release.
Until upgraded, restrict formatter-upload privileges to trusted administrators and monitor formatter changes.
Follow the GeoNetwork advisory and release notes for deployment-specific remediation guidance.
Validation and detection
Inventory every GeoNetwork deployment and compare its version with the affected ranges.
Confirm only trusted administrators can upload or modify formatters.
Review uploaded XSL stylesheets and formatter history for unexpected Java extension usage.
Review host telemetry for unexpected child processes launched by the GeoNetwork process.
After upgrading, verify the installed version and test legitimate formatter rendering.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-470: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-470 · source CWE mapping
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection')
Use of Externally-Controlled Input to Select Classes or Code ('Unsafe Reflection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Improper Control of Generation of Code ('Code Injection')
Improper Control of Generation of Code ('Code Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.