CVE-2025-30220

CRITICALNVD 9.99.9
EchelonGraph scoreMEDIUM confidence

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

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 42% (98th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 8.2 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2025-06-10) is not newer than that change (2025-08-26), so it does not.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekElevated

Also known asEUVD-2025-17683 (ENISA EUVD) · GHSA-jj54-8f66-c5pc (GitHub Security Advisories)Source: ENISA EUVD

9.9EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 42%CVSS: 9.9Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

GeoServer is an open source server that allows users to share and edit geospatial data. GeoTools Schema class use of Eclipse XSD library to represent schema data structure is vulnerable to XML External Entity (XXE) exploit. 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. This vulnerability is fixed in GeoTools 33.1, 32.3, 31.7, and 28.6.1, GeoServer 2.27.1, 2.26.3, and 2.25.7, and GeoNetwork 4.4.8 and 4.2.13.

CVSS v3
9.9
EG Score
9.9CRITICALmedium confidence
EG Risk
76
EG Risk 76/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)
Severity99% × 45%
Impact severity (EG Severity): CVSS 9.9 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation42% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
42%
EPSS %ILE
98th
KEV
Not listed

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.9): severity, escalated by confirmed exploitation. This CVE's 9.9 is its impact severity (EG Severity), not escalated.

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

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). 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; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

June 10, 2025

Last Modified

August 26, 2025

Advisory Details (6)

Auto-updated Oct 27, 2026
Patch available. Sources: github_pr, github.
GitHub advisoryMentions a patch (unverified)

XML External Entity (XXE) Processing Vulnerability in XSD schema handling · Advisory · geotools/geotools · GitHub

https://github.com/geotools/geotools/security/advisories/GHSA-826p-4gcg-35vw
GitHub advisoryMentions a patch (unverified)

XML External Entity (XXE) Processing Vulnerability in GeoServer WFS Service · Advisory · geoserver/geoserver · GitHub

https://github.com/geoserver/geoserver/security/advisories/GHSA-jj54-8f66-c5pc
GitHub advisoryMentions a patch (unverified)

XML External Entity (XXE) processing vulnerability in WFS indexing REST API endpoint · Advisory · geonetwork/core-geonetwork · GitHub

https://github.com/geonetwork/core-geonetwork/security/advisories/GHSA-2p76-gc46-5fvc
GitHub pull request Patch Available

Update to GeoTools 28.6.1

Patch available: geonetwork/core-geonetwork 4.2.14 (PR #8812 merged 2025-05-21)

https://github.com/geonetwork/core-geonetwork/pull/8812
GitHub pull request Patch Available

Update to GeoTools 32.3

Patch available: geonetwork/core-geonetwork 4.4.8 (PR #8803 merged 2025-05-16)

https://github.com/geonetwork/core-geonetwork/pull/8803
GitHub pull request Patch Available

API / WFSHarvesterApi / Restrict to Editor

Patch available: geonetwork/core-geonetwork 4.4.8 (PR #8757 merged 2025-04-25)

https://github.com/geonetwork/core-geonetwork/pull/8757

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
mavenorg.geoserver:gs-wfs @ 2.27.1 (fixes = 2.27.0)—ghsa
mavenorg.geoserver:gs-wfs @ 2.26.3 (fixes >= 2.26.0, <= 2.26.2)—ghsa
mavenorg.geoserver:gs-wfs @ 2.25.7 (fixes <= 2.25.6)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFix by version rangeDependents
org.geoserver:gs-wfs2.27.0
  • 2.27.0 up to 2.27.1: fixed in 2.27.1
  • 2.26.0 up to 2.26.3: fixed in 2.26.3
  • every version up to 2.25.7: fixed in 2.25.7
—
org.geoserver.web:gs-web-app2.27.0
  • 2.27.0 up to 2.27.1: fixed in 2.27.1
  • 2.26.0 up to 2.26.3: fixed in 2.26.3
  • every version up to 2.25.7: fixed in 2.25.7
—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 52× 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 96 of 186 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. 4 repeat rows among the latest 100 are merged into the row they repeat. The 90 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-02 10:14 UTCEG score recompute
  2. 2026-11-02 10:13 UTCGHSA enrichmentGHSA-jj54-8f66-c5pc · GitHub severity HIGH · GitHub CVSS 8.2
  3. 2026-11-01 10:53 UTCGHSA enrichmentGHSA-jj54-8f66-c5pc · GitHub severity HIGH · GitHub CVSS 8.2
  4. 2026-11-01 08:07 UTCGHSA enrichmentGHSA-jj54-8f66-c5pc · GitHub severity HIGH · GitHub CVSS 8.2
  5. 2026-11-01 08:07 UTCEG score recompute
  6. 2026-10-31 16:31 UTCEPSS rescoreEPSS 42% · 98th percentile
  7. 2026-10-31 11:37 UTCEG score recompute
  8. 2026-10-30 16:32 UTCEPSS rescoreEPSS 42% · 98th percentile
  9. 2026-10-30 12:19 UTCEG score recompute
  10. 2026-10-29 16:31 UTCEPSS rescoreEPSS 42% · 98th percentile
  11. 2026-10-29 13:03 UTCEG score recompute
  12. 2026-10-28 16:30 UTCEPSS rescoreEPSS 42% · 98th percentile
  13. 2026-10-28 13:46 UTCEG score recompute
  14. 2026-10-27 16:30 UTCEPSS rescoreEPSS 42% · 98th percentile
  15. 2026-10-27 14:16 UTCEG score recompute
  16. 2026-10-26 14:27 UTCEG score recompute
  17. 2026-10-25 16:31 UTCEPSS rescoreEPSS 42% · 98th percentile
  18. 2026-10-25 14:39 UTCEG score recompute
  19. 2026-10-24 16:31 UTCEPSS rescoreEPSS 42% · 98th percentile
  20. 2026-10-24 15:22 UTCEG score recompute
  21. 2026-10-23 16:30 UTCEPSS rescoreEPSS 42% · 98th percentile
  22. 2026-10-22 16:45 UTCEG score recompute
  23. 2026-10-22 16:32 UTCEPSS rescoreEPSS 42% · 98th percentile
  24. 2026-10-21 17:24 UTCEG score recompute
  25. 2026-10-21 16:31 UTCEPSS rescoreEPSS 42% · 98th percentile
Show 71 more
  1. 2026-10-20 17:58 UTCEG score recompute
  2. 2026-10-20 16:31 UTCEPSS rescoreEPSS 42% · 98th percentile
  3. 2026-10-19 18:41 UTCEG score recompute
  4. 2026-10-19 16:30 UTCEPSS rescoreEPSS 42% · 98th percentile
  5. 2026-10-18 19:13 UTCEG score recompute
  6. 2026-10-18 16:30 UTCEPSS rescoreEPSS 42% · 98th percentile
  7. 2026-10-18 05:40 UTCEG score recompute
  8. 2026-10-17 19:55 UTCEG score recompute
  9. 2026-10-17 16:32 UTCEPSS rescoreEPSS 42% · 98th percentile
  10. 2026-10-16 20:36 UTCEG score recompute
  11. 2026-10-16 16:38 UTCEPSS rescoreEPSS 42% · 98th percentile
  12. 2026-10-15 17:58 UTCEG score recompute
  13. 2026-10-15 16:30 UTCEPSS rescoreEPSS 42% · 98th percentile
  14. 2026-10-14 16:31 UTCEPSS rescoreEPSS 42% · 98th percentile
  15. 2026-10-14 11:48 UTCEG score recompute
  16. 2026-10-13 16:32 UTCEPSS rescoreEPSS 42% · 98th percentile
  17. 2026-10-12 17:13 UTCEG score recompute
  18. 2026-10-11 20:44 UTCEG score recompute
  19. 2026-10-11 18:55 UTCEG score recompute
  20. 2026-10-11 15:33 UTCEG score recompute
  21. 2026-10-11 13:47 UTCEPSS rescoreEPSS 42% · 98th percentile
  22. 2026-10-09 20:06 UTCEPSS rescoreEPSS 42% · 98th percentile
  23. 2026-10-08 17:09 UTCEPSS rescoreEPSS 42% · 98th percentile
  24. 2026-10-07 23:46 UTCEPSS rescoreEPSS 42% · 98th percentile
  25. 2026-10-06 15:16 UTCEPSS rescoreEPSS 42% · 98th percentile
  26. 2026-10-05 17:42 UTCEPSS rescoreEPSS 42% · 98th percentile
  27. 2026-10-03 14:24 UTCEPSS rescoreEPSS 42% · 98th percentile
  28. 2026-10-02 12:11 UTCOSV refresh
  29. 2026-10-01 19:49 UTCEPSS rescoreEPSS 42% · 98th percentile
  30. 2026-09-30 15:02 UTCEPSS rescoreEPSS 42% · 98th percentile
  31. 2026-09-29 15:19 UTCEPSS rescoreEPSS 42% · 98th percentile
  32. 2026-09-26 15:58 UTCEPSS rescoreEPSS 42% · 98th percentile
  33. 2026-09-26 00:24 UTCEPSS rescoreEPSS 42% · 98th percentile
  34. 2026-09-24 14:02 UTCEPSS rescoreEPSS 42% · 98th percentile
  35. 2026-09-23 13:47 UTCEPSS rescoreEPSS 42% · 98th percentile
  36. 2026-09-18 19:27 UTCEPSS rescoreEPSS 41% · 98th percentile
  37. 2026-09-16 14:07 UTCEPSS rescoreEPSS 41% · 98th percentile
  38. 2026-09-16 05:13 UTCEPSS rescoreEPSS 41% · 98th percentile
  39. 2026-09-13 10:24 UTCOSV refresh
  40. 2026-09-12 15:00 UTCEPSS rescoreEPSS 41% · 98th percentile
  41. 2026-09-11 14:52 UTCEPSS rescoreEPSS 41% · 98th percentile
  42. 2026-09-11 09:35 UTCEPSS rescoreEPSS 46% · 98th percentile
  43. 2026-09-10 09:33 UTCEPSS rescoreEPSS 46% · 98th percentile
  44. 2026-09-08 21:59 UTCEPSS rescoreEPSS 46% · 98th percentile
  45. 2026-09-06 13:46 UTCEPSS rescoreEPSS 46% · 98th percentile
  46. 2026-09-04 05:05 UTCEPSS rescoreEPSS 46% · 98th percentile
  47. 2026-09-02 14:11 UTCEPSS rescoreEPSS 46% · 98th percentile
  48. 2026-09-01 13:53 UTCEPSS rescoreEPSS 46% · 98th percentile
  49. 2026-08-30 19:16 UTCEPSS rescoreEPSS 57% · 98th percentile
  50. 2026-08-30 01:21 UTCEPSS rescoreEPSS 57% · 99th percentile
  51. 2026-08-28 21:40 UTCEPSS rescoreEPSS 57% · 99th percentile
  52. 2026-08-27 14:24 UTCEPSS rescoreEPSS 57% · 98th percentile
  53. 2026-08-26 14:45 UTCEPSS rescoreEPSS 57% · 98th percentile
  54. 2026-08-25 13:48 UTCEPSS rescoreEPSS 57% · 98th percentile
  55. 2026-08-25 11:11 UTCOSV refresh
  56. 2026-08-24 14:16 UTCEPSS rescoreEPSS 57% · 98th percentile
  57. 2026-08-21 23:48 UTCEPSS rescoreEPSS 57% · 98th percentile
  58. 2026-08-19 17:03 UTCEPSS rescoreEPSS 57% · 98th percentile
  59. 2026-08-18 13:47 UTCEPSS rescoreEPSS 57% · 98th percentile
  60. 2026-08-17 13:46 UTCEPSS rescoreEPSS 57% · 98th percentile
  61. 2026-08-16 14:55 UTCEPSS rescoreEPSS 57% · 98th percentile
  62. 2026-08-16 02:13 UTCEPSS rescoreEPSS 57% · 98th percentile
  63. 2026-08-15 01:29 UTCEPSS rescoreEPSS 57% · 98th percentile
  64. 2026-08-13 21:59 UTCEPSS rescoreEPSS 57% · 98th percentile
  65. 2026-08-12 13:50 UTCEPSS rescoreEPSS 57% · 98th percentile
  66. 2026-08-10 23:59 UTCEPSS rescoreEPSS 57% · 98th percentile
  67. 2026-08-09 03:57 UTCOSV refresh
  68. 2026-08-07 16:26 UTCEPSS rescoreEPSS 54% · 98th percentile
  69. 2026-08-06 13:46 UTCEPSS rescoreEPSS 54% · 98th percentile
  70. 2026-08-05 19:16 UTCEPSS rescoreEPSS 54% · 98th percentile
  71. 2026-08-04 10:37 UTCEPSS rescoreEPSS 54% · 98th percentile

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2025/CVE-2025-30220.yaml
    Published Jun 17, 2025

    GeoServer WFS - XXE Processing Vulnerability

    Open source ↗

Frequently asked(5)

What is CVE-2025-30220?
CVE-2025-30220 is a critical-severity vulnerability; its CVE record was published on June 10, 2025. GeoServer is an open source server that allows users to share and edit geospatial data. GeoTools Schema class use of Eclipse XSD library to represent schema data structure is vulnerable to XML External Entity (XXE) exploit. This impacts whoever exposes XML processing with gt-xsd-core involved in…
When was the CVE record for CVE-2025-30220 published?
The CVE record for CVE-2025-30220 was published on June 10, 2025. 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 August 26, 2025; the record at its source may have been updated since.
Is CVE-2025-30220 actively exploited?
CVE-2025-30220 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 42% probability of exploitation in the next 30 days (98th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-30220?
CVE-2025-30220 has a CVSS v3 base score of 9.9 (NVD).
How do I remediate CVE-2025-30220?
A fix for CVE-2025-30220 is available: update to the fixed version the vendor names in its advisory.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2025-30220

Explore →

Is Your Infrastructure Affected by CVE-2025-30220?

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