Quick answers
- Is CVE-2026-39922 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-39922 being exploited in the wild.
- How severe is CVE-2026-39922?
- Medium severity, with a CVSS score of 6.3, published 10 April 2026.
- Which products and versions are affected?
- geonode (PyPI) ECOSYSTEM:introduced=4.0.0,fixed=4.4.5, ECOSYSTEM:introduced=4.0.0,fixed=4.4.5,introduced=5.0.0,fixed=5.0.2.
- Is there a fix for CVE-2026-39922?
- Yes. geonode (PyPI): upgrade to 4.4.5, 5.0.2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-39922 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-39922?
- Check whether you run 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 4.4.5, 5.0.2 or later
pip install "geonode>=5.0.2"
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in the GeoNode service registration endpoint, specifically within the WMS service handler. The root cause is insufficient URL validation and a lack of private IP filtering or allowlist enforcement during form validation. An authenticated attacker can submit a crafted service URL to trigger outbound requests from the server. This allows for probing of internal network targets, including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services (e.g., IMDS). The vulnerability is addressed in versions subsequent to 4.4.5 and 5.0.2.
Affected products
- GeoNode GeoNode 4.0.0 to 4.4.5, 5.0.0 to 5.0.2
Identifiers
- CVE-2026-39922
- GHSA-hw9r-6m78-w6h3
- PYSEC-2026-61
Timeline
- 2026-04-10: advisory: Initial advisory published by VulnCheck
- 2026-04-10: disclosed