CVE-2026-58400

CRITICALPre-NVD 9.19.1
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score elevated to 9.1 because this CVE is listed on ENISA's EU Known Exploited Vulnerabilities catalogue (Source: ENISA EUVD), indicating that ENISA records real-world exploitation of it. It is not on CISA's Known Exploited Vulnerabilities catalog. A secondary CVSS source baseline 9.1 retained for reference (NVD's own analysis pending). Confidence: HIGH.

Triggered by: ENISA EU KEV (actively exploited, as ENISA records it; Source: ENISA EUVD)
Sources: EPSS, ENISA's EU Known Exploited Vulnerabilities catalogue, a secondary CVSS source

Also known asEUVD-2026-70645 (ENISA EUVD)Source: ENISA EUVD

9.1EG
EchelonGraph verdictPatch soonRemediate within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact (the SSVC decision on this page).
  • Exploited in the wild, as ENISA's EU KEV records it (Source: ENISA EUVD); CISA has not listed it
CISA-KEV: Not listedENISA EU KEV: Listed (Source: ENISA EUVD)EPSS PROB: 1.2%CVSS: 9.1Exploit: No code on recordExposed services: Not assessed

The CVE record names the fixed release — apply it.

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.

CVSS v3
9.1
EG Score
9.1CRITICALhigh confidence
EG Risk
81
EG Risk 81/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
Impact severity (EG Severity): CVSS 9.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for an ENISA EU KEV listing (CISA's catalog does not list this CVE): EchelonGraph's rule. Source: ENISA EUVD.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (ENISA EU KEV listing; Source: ENISA EUVD) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). From CISA's SSVC values (Vulnrichment): automatable and technical impact; the others come from the sources named beside them. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: The CVE record names the fixed release. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.
EPSS PROB
1.2%
EPSS %ILE
67th
KEV
Not in CISA'sENISA's EU KEV lists it (below). Source: ENISA EUVD

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.1): severity, escalated by confirmed exploitation. This CVE's 9.1 is its impact severity (EG Severity), not escalated.

EG Severity
9.1 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
1.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-01). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
ENISA EU KEV (Source: ENISA EUVD)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactTrack at low, Attend at medium and Act at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

ENISA EU KEV: listed September 2, 2026, reported by CNW; not on CISA's KEV catalog.

Source: ENISA EUVD (EU Known Exploited Vulnerabilities catalogue), reproduced with acknowledgement. How a listing moves the EG score

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

The CVE record names the fixed release. Apply it within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact.

Exploitation active (ENISA EU KEV listing; Source: ENISA EUVD) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). From CISA's SSVC values (Vulnrichment): automatable and technical impact; the others come from the sources named beside them. EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 3, 2026

Last Modified

September 9, 2026

Advisory Details (4)

Auto-updated Sep 15, 2026
Fix named in the CVE record. Sources: github.
Web page

GeoNetwork Fixes Unauthenticated RCE Chain Affecting Government Geoportal Backends

https://thehackernews.com/2026/09/geonetwork-fixes-unauthenticated-rce.html
GitHub advisoryMentions a patch (unverified)

Remote Code Execution via unsafe Saxon XSLT processor configuration in formatter · Advisory · geonetwork/core-geonetwork · GitHub

https://github.com/geonetwork/core-geonetwork/security/advisories/GHSA-x898-729x-cc3r

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 63× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 118 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 18 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 11:19 UTCEG score recompute
  2. 2026-11-01 11:45 UTCEG score recompute
  3. 2026-10-31 16:33 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  4. 2026-10-31 12:11 UTCEG score recompute
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  6. 2026-10-30 12:38 UTCEG score recompute
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  8. 2026-10-29 13:03 UTCEG score recompute
  9. 2026-10-28 16:32 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  10. 2026-10-28 13:29 UTCEG score recompute
  11. 2026-10-27 16:32 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  12. 2026-10-27 13:47 UTCEG score recompute
  13. 2026-10-26 16:31 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  14. 2026-10-26 13:40 UTCEG score recompute
  15. 2026-10-25 16:33 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  16. 2026-10-25 13:47 UTCEG score recompute
  17. 2026-10-25 13:46 UTCENISA EU KEV listingEUVD-2026-70645 · listed September 2, 2026 · reported by CNW · Source: ENISA EUVD
  18. 2026-10-25 12:50 UTCEG score recompute
  19. 2026-10-24 16:33 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  20. 2026-10-24 13:14 UTCEG score recompute
  21. 2026-10-23 16:32 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  22. 2026-10-23 13:39 UTCEG score recompute
  23. 2026-10-22 16:34 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  24. 2026-10-22 14:02 UTCEG score recompute
  25. 2026-10-21 16:33 UTCEPSS rescoreEPSS 1.2% · 67th percentile
Show 75 more
  1. 2026-10-21 14:26 UTCEG score recompute
  2. 2026-10-20 16:33 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  3. 2026-10-20 14:34 UTCEG score recompute
  4. 2026-10-19 16:32 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  5. 2026-10-19 13:39 UTCEG score recompute
  6. 2026-10-18 16:32 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  7. 2026-10-18 03:28 UTCEG score recompute
  8. 2026-10-17 16:35 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  9. 2026-10-17 13:58 UTCEG score recompute
  10. 2026-10-16 16:43 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  11. 2026-10-16 14:24 UTCEG score recompute
  12. 2026-10-15 16:32 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  13. 2026-10-15 14:35 UTCEG score recompute
  14. 2026-10-14 16:33 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  15. 2026-10-14 09:11 UTCEG score recompute
  16. 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  17. 2026-10-13 06:16 UTCEG score recompute
  18. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  19. 2026-10-12 15:53 UTCEG score recompute
  20. 2026-10-11 19:36 UTCEG score recompute
  21. 2026-10-11 16:52 UTCEG score recompute
  22. 2026-10-11 14:14 UTCEG score recompute
  23. 2026-10-11 13:49 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  24. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.2% · 67th percentile
  25. 2026-10-09 23:31 UTCEG score recompute
  26. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  27. 2026-10-09 01:26 UTCEG score recompute
  28. 2026-10-08 17:13 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  29. 2026-10-08 03:14 UTCEG score recompute
  30. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  31. 2026-10-06 16:25 UTCEG score recompute
  32. 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  33. 2026-10-05 20:28 UTCEG score recompute
  34. 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  35. 2026-10-05 01:14 UTCEG score recompute
  36. 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  37. 2026-10-03 16:31 UTCEG score recompute
  38. 2026-10-03 14:26 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  39. 2026-10-02 21:31 UTCEG score recompute
  40. 2026-10-02 17:56 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  41. 2026-10-02 00:31 UTCEG score recompute
  42. 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  43. 2026-09-30 19:08 UTCEG score recompute
  44. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  45. 2026-09-29 16:01 UTCEG score recompute
  46. 2026-09-29 15:22 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  47. 2026-09-29 00:31 UTCEG score recompute
  48. 2026-09-28 15:44 UTCEG score recompute
  49. 2026-09-28 13:51 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  50. 2026-09-27 16:52 UTCEG score recompute
  51. 2026-09-27 13:48 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  52. 2026-09-26 17:21 UTCEG score recompute
  53. 2026-09-26 15:59 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  54. 2026-09-26 03:44 UTCEG score recompute
  55. 2026-09-24 15:20 UTCEG score recompute
  56. 2026-09-24 14:04 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  57. 2026-09-23 20:19 UTCEG score recompute
  58. 2026-09-23 17:54 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  59. 2026-09-22 18:00 UTCEG score recompute
  60. 2026-09-21 22:37 UTCEG score recompute
  61. 2026-09-20 23:57 UTCEG score recompute
  62. 2026-09-20 20:16 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  63. 2026-09-19 17:51 UTCEG score recompute
  64. 2026-09-18 23:00 UTCEG score recompute
  65. 2026-09-18 19:28 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  66. 2026-09-17 20:34 UTCEG score recompute
  67. 2026-09-17 19:31 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  68. 2026-09-16 18:34 UTCEG score recompute
  69. 2026-09-16 14:08 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  70. 2026-09-16 05:37 UTCEG score recompute
  71. 2026-09-16 05:15 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  72. 2026-09-15 06:20 UTCEG score recompute
  73. 2026-09-15 03:11 UTCEPSS rescoreEPSS 1.2% · 66th percentile
  74. 2026-09-13 20:28 UTCEG score recompute
  75. 2026-09-13 16:47 UTCEPSS rescoreEPSS 1.2% · 66th percentile

Frequently asked(5)

What is CVE-2026-58400?
CVE-2026-58400 is a critical-severity vulnerability; its CVE record was published on September 3, 2026. 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…
When was the CVE record for CVE-2026-58400 published?
The CVE record for CVE-2026-58400 was published on September 3, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 9, 2026; the record at its source may have been updated since.
Is CVE-2026-58400 actively exploited?
CVE-2026-58400 is not currently on CISA's Known Exploited Vulnerabilities catalog. ENISA's EU Known Exploited Vulnerabilities catalogue lists CVE-2026-58400 (added September 2, 2026, reported by CNW): ENISA records its exploitation in the wild. Source: ENISA EUVD (EU Known Exploited Vulnerabilities catalogue), reproduced with acknowledgement. FIRST EPSS estimates a 1.2% probability of exploitation in the next 30 days (67th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-58400?
CVE-2026-58400 has a CVSS base score of 9.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-58400?
The CVE record for CVE-2026-58400 names the fix: "The issue is patched in GeoNetwork versions 4.4.12 and 4.2.17."

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-58400

Explore →

Is Your Infrastructure Affected by CVE-2026-58400?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.