CVE-2026-39921: GeoNode · Server-Side Request Forgery (SSRF)
Affects GeoNodeSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium : upgrade to 5.0.2 or 4.4.5 when convenient.
Data as of 8 Nov 2026, 14:19 UTC
Thin evidence
One scorer or none| CNA (VulnCheck) | CVSS 4.0 | 5.3 |
|---|
- CISA SSVC
- Exploitation
- No evidence of active exploitation and no public proof of concept
- Automatable
- Attackers cannot reliably automate steps 1–4 of the kill chain
- Technical impact
- Limited control over the software or limited information exposure
CISA SSVC assessment, 2026-04-13.
- Patch
- Available – fixed in 5.0.2, 4.4.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:LExploitation evidence
Disclosed: evidence found.
CVE published 10 Apr 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 8 Nov 2026.
What to do
Upgrade GeoNode to 5.0.2 or 4.4.5.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GeoNodeGeoNode | Affected
| Fixed in
|
| GeoNodeGeoNode | Affected
| Fixed in
|
GitHubGeoNodepkg:github/GeoNodeOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
GeoNode versions 4.0 before 4.4.5 and 5.0 before 5.0.2 contain a server-side request forgery vulnerability that allows authenticated users with document upload permissions to trigger arbitrary outbound HTTP requests by providing a malicious URL via the doc_url parameter during document upload. Attackers can supply URLs pointing to internal network targets, loopback addresses, RFC1918 addresses, or cloud metadata services to cause the server to make requests to internal resources without SSRF mitigations such as private IP filtering or redirect validation.
References
- github.com/GeoNode/geonode/releases/tag/5.0.2 (opens in a new tab)
- github.com/GeoNode/geonode/releases/tag/4.4.5 (opens in a new tab)
- github.com/GeoNode/geonode/pull/14058 (opens in a new tab)
- github.com/GeoNode/geonode/commit/9856cb5ab27e33c0adba9274f4cccf6d1f534bd1 (opens in a new tab)
- github.com/GeoNode/geonode/commit/4a852cfc1da732b10779b5bf5f087c8f02985571 (opens in a new tab)
- vulncheck.com/advisories/geonode-ssrf-via-document-upload (opens in a new tab)