Skip to main content
VulnerabilityPublished Updated

CVE-2026-39921: GeoNode · Server-Side Request Forgery (SSRF)

Affects GeoNodeSource CVE Database V5

0
Compare

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

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.05.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:L

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 10 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
GeoNodeGeoNodeAffected
  • >=5.0.0 <5.0.2
Fixed in
  • 5.0.2
GeoNodeGeoNodeAffected
  • >=4.0.0 <4.4.5
Fixed in
  • 4.4.5
GitHubGeoNodepkg:github/GeoNodeOther threatsAffected
  • >=4.0.0 <4.4.5
  • >=5.0.0 <5.0.2
Fixed in
  • 4.4.5
  • 5.0.2

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

Community reviews

Loading reviews…