WaratekVRT Sign in

CVE-2026-39379

Severity7.1 High CVSS 3.1
Fixed in4.2.15, 4.4.10
WeaknessCross-site scripting (CWE-79)
Published3 Nov 2026
Updated12 Nov 2026

Published 11 days ago. NVD often adds the list of affected products days or weeks after a CVE is published, and the other sources we check lag too. The scope and status here may change.

Description

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.

CWE-1336

Exploitation status

No public exploit

No exploit has been reported in the sources we check.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment exploitation: none
  • Indexed PoC none indexed
  • EPSS 0.36% chance in 30 days

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists: geonetwork/core-geonetwork 5cacdfa.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all
Finding This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.
Candidate fix https://github.com/geonetwork/core-geonetwork/commit/5cacdfaa6db88ef6787495b496a0871c0058b7f4 : a commit: the change itself

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
org.geonetwork-opensource:geonetwork 3.0.0 none 3.12.12
org.geonetwork-opensource:geonetwork 4.0.0-alpha.1 none 4.0.6
org.geonetwork-opensource:geonetwork 4.2.0 4.2.15 unbounded
org.geonetwork-opensource:geonetwork 4.4.0 4.4.10 unbounded

Products and versions

1 product, 4 version entries
SourceVendorProductSchemeAffected versions
osv org.geonetwork-opensource geonetwork generic ≥ 3.0.0 and ≤ 3.12.12 · ≥ 4.0.0 and ≤ 4.0.6 · ≥ 4.2.0 and < 4.2.15 · ≥ 4.4.0 and < 4.4.10

References

URLTags
https://github.com/geonetwork/core-geonetwork/commit/5cacdfaa6db88ef6787495b496a0871c0058b7f4 commit
https://github.com/geonetwork/core-geonetwork/security/advisories/GHSA-2v4m-fw6c-g78f WEB
https://github.com/geonetwork/core-geonetwork PACKAGE
https://github.com/geonetwork/core-geonetwork/commit/dd99c2ffb642f89b8bf72bafd04d824c9fc0d0ef
https://github.com/geonetwork/core-geonetwork/releases/tag/4.2.15
https://github.com/geonetwork/core-geonetwork/releases/tag/4.4.10

Timeline

Published2026-11-03By the CVE Program.
NVD record modified2026-11-12NVD's own last-modified date for this record.