org.geonetwork-opensource:geonetwork

CVE-2026-39379

CVE-2026-39379 is a high-severity cross-site scripting (XSS) vulnerability in org.geonetwork-opensource:geonetwork (maven), affecting versions >= 3.0.0, <= 3.12.12. It is fixed in 4.2.15, 4.4.10.

Key facts
CVSS score
7.1
High
Attack vector
Network
Issuing authority
GitHub Advisory Database
Affected package
org.geonetwork-opensource:geonetwork
Fixed in
4.2.15, 4.4.10
Disclosed
2026

Summary

Summary It is possible to craft a URL that causes GeoNetwork to reflect attacker-controlled content into an error page in a way that gets evaluated as a client-side template expression. Combined with known AngularJS sandbox-escape techniques, this can be used to execute arbitrary JavaScript in the victim's browser (reflected Cross-Site Scripting via client-side template injection). Details When a user requests a service URL that does not exist or that they are not authorized to access, GeoNetwork shows an error page that reflects part of the original request back to the user without adequately neutralizing it for the context it is rendered in. Because this error page is an AngularJS application, attacker-controlled content in the reflected value can be interpreted as a template expression and evaluated once the page loads in the victim's browser, rather than being displayed as inert text. Impact An attacker can trick a user (including an administrator) into visiting a crafted link. The resulting script execution runs in the context of the victim's authenticated session and can be used to exfiltrate information or perform actions on the victim's behalf. For example, an attacker could inject a fake login form that looks identical to the legitimate GeoNetwork login page to harvest credentials. GeoNetwork 3.x and 4.0.x are archived/unmaintained and will not receive a fix for this issue. Instances running those lines should upgrade to a supported release (4.2.15 or later, or 4.4.10 or later).

Impact

What is cross-site scripting (XSS)?

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

Severity and exposure

CVE-2026-39379 has a CVSS score of 7.1 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.

A fixed version is available (4.2.15, 4.4.10). Upgrading removes the vulnerable code path.

Affected versions

maven

  • org.geonetwork-opensource:geonetwork (>= 3.0.0, <= 3.12.12)
  • org.geonetwork-opensource:geonetwork (>= 4.0.0-alpha.1, <= 4.0.6)
  • org.geonetwork-opensource:geonetwork (>= 4.2.0, <= 4.2.14)
  • org.geonetwork-opensource:geonetwork (>= 4.4.0, <= 4.4.9)

Security releases

  • org.geonetwork-opensource:geonetwork → 4.2.15 (maven)
  • org.geonetwork-opensource:geonetwork → 4.4.10 (maven)
Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.

Kodem's runtime-powered SCA identifies whether CVE-2026-39379 is reachable in your applications. Explore open-source security for your team.

See if CVE-2026-39379 is reachable in your applications. Get a demo

Already deployed Kodem? See CVE-2026-39379 in your environment

Remediation advice

Upgrade the following packages to resolve this vulnerability:

  • Upgrade org.geonetwork-opensource:geonetwork to 4.2.15 or later
  • Upgrade org.geonetwork-opensource:geonetwork to 4.4.10 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently asked questions about CVE-2026-39379

What is CVE-2026-39379?

CVE-2026-39379 is a high-severity cross-site scripting (XSS) vulnerability in org.geonetwork-opensource:geonetwork (maven), affecting versions >= 3.0.0, <= 3.12.12. It is fixed in 4.2.15, 4.4.10. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.

How severe is CVE-2026-39379?

CVE-2026-39379 has a CVSS score of 7.1 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of org.geonetwork-opensource:geonetwork are affected by CVE-2026-39379?

org.geonetwork-opensource:geonetwork (maven) versions >= 3.0.0, <= 3.12.12 is affected.

Is there a fix for CVE-2026-39379?

Yes. CVE-2026-39379 is fixed in 4.2.15, 4.4.10. Upgrade to this version or later.

Is CVE-2026-39379 exploitable, and should I be worried?

Whether CVE-2026-39379 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo

What actually determines whether CVE-2026-39379 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix CVE-2026-39379?
  • Upgrade org.geonetwork-opensource:geonetwork to 4.2.15 or later
  • Upgrade org.geonetwork-opensource:geonetwork to 4.4.10 or later

Stop the waste.
Protect your environment with Kodem.