{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-58400 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-58400 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-58400 is a critical code injection vulnerability in core-geonetwork, published on 3 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-58400 and fix it if it is affected.\n\nWhat it is: CVE-2026-58400 is a critical code injection vulnerability in core-geonetwork, published on 3 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-58400 in the wild and no public exploit code.\n\nAffected product: core-geonetwork. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-58400/ (Markdown: https://insights.sbomify.com/CVE-2026-58400/index.md)","id":"CVE-2026-58400","markdown":"https://insights.sbomify.com/CVE-2026-58400/index.md","name":"CVE-2026-58400","record":{"aliases":["GHSA-x898-729x-cc3r"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"GeoNetwork catalog application","requires_auth":"high_privilege","summary":"Privileged users can achieve remote code execution by uploading malicious XSLT stylesheets due to unsafe Saxon processor configuration.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-470","name":"Use of Externally-Controlled Input to Select Classes or Code"}],"description":"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\n`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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"GeoNetwork vulnerable to Remote Code Execution via unsafe Saxon XSLT processor configuration in formatter","id":"CVE-2026-58400","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Hugo default code block renderer XSS via unescaped code-fence language","id":"CVE-2026-58402"},"packages":[],"prev":{"headline":"@acastellon/auth has an authentication bypass via spoofable headers in validateToken()","id":"CVE-2026-58399"},"products":["core-geonetwork"],"published":"2026-09-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-09-04","vendors":["geonetwork"]},"summary":"Privileged users can achieve remote code execution by uploading malicious XSLT stylesheets due to unsafe Saxon processor configuration.","url":"https://insights.sbomify.com/CVE-2026-58400/"}