Answer in brief
CVE-2026-39379 records a High severity (CVSS 7.1) vulnerability in GeoNetwork: Reflected XSS through client-side template injection. The current sources do not mark it as known exploited. The current feed maps geonetwork/core-geonetwork (generic), org.geonetwork-opensource:geonetwork (maven), org.geonetwork-opensource:geonetwork (maven), org.geonetwork-opensource:geonetwork (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps geonetwork/core-geonetwork (generic), org.geonetwork-opensource:geonetwork (maven), org.geonetwork-opensource:geonetwork (maven), org.geonetwork-opensource:geonetwork (maven) and additional mapped packages. Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| geonetwork/core-geonetworkgeneric | >=3.0.0 <=3.12.12 || >=4.0.0-alpha.1 <=4.0.6 || >=4.2.0 <4.2.15 || >=4.4.0 <4.4.10 | 4.2.15, 4.4.10 |
| org.geonetwork-opensource:geonetworkmaven | >=3.0.0,<=3.12.12 | Not reported |
| org.geonetwork-opensource:geonetworkmaven | >=4.0.0-alpha.1,<=4.0.6 | Not reported |
| org.geonetwork-opensource:geonetworkmaven | >=4.2.0,<=4.2.14 | 4.2.15 |
| org.geonetwork-opensource:geonetworkmaven | >=4.4.0,<=4.4.9 | 4.4.10 |
Published upstream
Nov 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 1, 2026
GeoNetwork is a catalog application to manage spatially referenced resources. From 3.0.0 until 4.2.15 and 4.4.10, requesting a nonexistent or unauthorized service URL can cause an error page to reflect attacker-controlled request content inside an AngularJS application without adequately neutralizing it for template evaluation. A remote attacker can induce a victim, including an administrator, to open a crafted link so the reflected value is evaluated as an AngularJS template expression. Combined with known AngularJS sandbox-escape techniques, this can execute arbitrary JavaScript in the victim's authenticated browser session, disclose information, or perform actions as the victim. This issue is fixed in versions 4.2.15 and 4.4.10.
Quoted source text, attributed separately from HOL analysis.