Is CVE-2026-55649 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-55649 being exploited in the wild.

How severe is CVE-2026-55649?

Medium severity, with a CVSS score of 6.3, published 6 November 2026.

Which products and versions are affected?

GeoNode < 5.0.3; geonode (PyPI) < 5.0.3, ECOSYSTEM:introduced=0,fixed=5.0.3.

Is there a fix for CVE-2026-55649?

Yes. geonode (PyPI): upgrade to 5.0.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-55649 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-55649?

Check whether you run GeoNode or geonode (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55649: GeoNode stored XSS in documents metadata abstract field

Q: Which products and versions are affected?

GeoNode < 5.0.3; geonode (PyPI) < 5.0.3, ECOSYSTEM:introduced=0,fixed=5.0.3.

Q: Is there a fix for CVE-2026-55649?

Yes. geonode (PyPI): upgrade to 5.0.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-55649 attacked?

It is attacked over the network, in a web application.

Q: Am I affected by CVE-2026-55649?

Check whether you run GeoNode or geonode (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55649 · Severity: medium · CVSS 6.3 · Published 2026-11-06

GeoNode is a web platform for managing and sharing geospatial data and documents. An attacker with low-level user privileges can inject malicious JavaScript code into document metadata that will execute in the browsers of other users who view those documents, potentially stealing sensitive information or performing unauthorized actions on their behalf.

Technologies: GeoNode, geonode (PyPI). Vendors: GeoNode, PyPI.

Quick answers

Is CVE-2026-55649 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-55649 being exploited in the wild.
How severe is CVE-2026-55649?: Medium severity, with a CVSS score of 6.3, published 6 November 2026.
Which products and versions are affected?: GeoNode < 5.0.3; geonode (PyPI) < 5.0.3, ECOSYSTEM:introduced=0,fixed=5.0.3.
Is there a fix for CVE-2026-55649?: Yes. geonode (PyPI): upgrade to 5.0.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55649 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-55649?: Check whether you run GeoNode or geonode (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

geonode (PyPI): upgrade to 5.0.3 or later
```
pip install "geonode>=5.0.3"
```

Technical details

The vulnerability is a stored cross-site scripting (XSS) flaw in the document abstract metadata field, which fails to sanitize user input before rendering on the page. An authenticated attacker with low privileges can inject arbitrary HTML and JavaScript that persists in the database and executes when other users visit the affected document page. This requires user interaction (viewing the page) but leads to high confidentiality impact through session hijacking or credential theft.

Affected products

GeoNode GeoNode < 5.0.3

Identifiers

CVE-2026-55649
GHSA-r4hm-p9f9-fj9v

Timeline

2026-11-05: disclosed
2026-11-05: patched

References

https://github.com/GeoNode/geonode/security/advisories/GHSA-r4hm-p9f9-fj9v

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.