GeoNode
GeoNode is an open source platform that facilitates the creation, sharing, and collaborative use of geospatial data.
View on Github
Activity
- Latest release
- 1w ago
- Total releases
- 233
- Cadence
- ~21 days
- Last 12 months
- 10
Reach
- Stars
- 1.7k
Details
- License
- unknown
- First release
- Jun 14, 2013
| Version | Released | |
|---|---|---|
5.1.1
patch
| ||
5.1.0.post1
pre
| ||
5.1.0
minor
| ||
5.0.3.post1
pre
| ||
5.0.3
patch
| ||
5.0.2
patch
| ||
4.4.5
patch
| ||
5.0.1
patch
2 CVEs
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
5.0.0
major
2 CVEs
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
4.4.4
patch
2 CVEs
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
4.4.3
patch
2 CVEs
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
4.4.2
patch
2 CVEs
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
4.4.1
patch
2 CVEs
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
4.4.0
minor
2 CVEs
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
4.3.1
patch
2 CVEs
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
4.3.0.post1
pre
2 CVEs
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
4.3.0
minor
2 CVEs
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
4.2.5
patch
2 CVEs
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
4.2.4
patch
2 CVEs
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
4.1.5
patch
4 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
4.2.3
patch
2 CVEs
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
4.1.4
patch
4 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
4.2.2
patch
3 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
4.2.1
patch
3 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
4.2.0
minor
3 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev | ||
4.1.3.post1
pre
4 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
4.1.3
patch
5 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
4.1.2
patch
5 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
4.1.1
patch
5 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
4.1.0
minor
5 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
4.0.3
patch
5 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
4.0.2
patch
6 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-26043
GHSA-mcmc-c59m-pqq8
PYSEC-2023-15
Aug 30, 2024
GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
High
Network
Low
Low
None
SummaryGeoNode is vulnerable to an XML External Entity (XXE) injection in the style upload functionality of GeoServer leading to Arbitrary File Read. DetailsGeoNode's GeoServer has the ability to upload new styles for datasets through the
PoC
Sample response: ImpactThis issue may lead to authenticated Affected versions
2.0
2.0.1
2.0.dev20130913181950
2.0.dev20140626191247
2.0b10
2.0b11
2.0b12
2.0b13
2.0b17
2.0b18
2.0b19
2.0b21
+ 199 more Show less
2.0b22
2.0b24
2.0b25
2.0b26
2.0b27
2.0b28
2.0b29
2.0b3
2.0b30
2.0b31
2.0b32
2.0b33
2.0b34
2.0b35
2.0b36
2.0b37
2.0b38
2.0b39
2.0b4
2.0b40
2.0b41
2.0b42
2.0b43
2.0b44
2.0b45
2.0b46
2.0b48
2.0b49
2.0b5
2.0b50
2.0b51
2.0b52
2.0b53
2.0b54
2.0b55
2.0b57
2.0b58
2.0b59
2.0b60
2.0b61
2.0b62
2.0b63
2.0b64
2.0b7
2.0c1
2.0c12
2.0c13
2.0c2
2.0c3
2.0c4
2.0c5
2.0c7
2.0c8
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10rc0
2.10rc1
2.10rc2
2.10rc3
2.10rc4
2.10rc5
2.4
2.4.1
2.4a1
2.4a10
2.4a11
2.4a12
2.4a13
2.4a14
2.4a15
2.4a16
2.4a17
2.4a18
2.4a19
2.4a2
2.4a20
2.4a21
2.4a22
2.4a23
2.4a24
2.4a25
2.4a26
2.4a28
2.4a29
2.4a3
2.4a30
2.4a31
2.4a32
2.4a33
2.4a34
2.4a35
2.4a36
2.4a38
2.4a4
2.4a5
2.4a6
2.4a7
2.4a8
2.4a9
2.4b1
2.4b10
2.4b11
2.4b12
2.4b13
2.4b14
2.4b15
2.4b16
2.4b17
2.4b18
2.4b19
2.4b2
2.4b20
2.4b21
2.4b22
2.4b23
2.4b24
2.4b25
2.4b26
2.4b27
2.4b28
2.4b3
2.4b4
2.4b5
2.4b6
2.4b7
2.4b8
2.4c1
2.4c2
2.4c3
2.4c4
2.5.1
2.5.10
2.5.12
2.5.13
2.5.14
2.5.15
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.9
2.5.9.dev20170116091328
2.5.dev20160825082804
2.6
2.6.1
2.6.2
2.6.3
2.6a1
2.6c1
2.7
2.7.1.dev20171013151516
2.7.2.dev20171013181854
2.7.4.dev20171114161428
2.7.5.dev20180123130714
2.7.5.dev20180125135927
2.8
2.8.1
2.8.1rc0
2.8rc0
2.8rc1
2.8rc10
2.8rc11
2.8rc12
2.8rc13
2.8rc2
2.8rc3
2.8rc4
2.8rc5
2.8rc6
2.8rc7
2.8rc8
2.8rc9
3.0.0
3.1.0
3.1.1
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
Fixed in
4.0.3
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
3.3.3
patch
4 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-26043
GHSA-mcmc-c59m-pqq8
PYSEC-2023-15
Aug 30, 2024
GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
High
Network
Low
Low
None
SummaryGeoNode is vulnerable to an XML External Entity (XXE) injection in the style upload functionality of GeoServer leading to Arbitrary File Read. DetailsGeoNode's GeoServer has the ability to upload new styles for datasets through the
PoC
Sample response: ImpactThis issue may lead to authenticated Affected versions
2.0
2.0.1
2.0.dev20130913181950
2.0.dev20140626191247
2.0b10
2.0b11
2.0b12
2.0b13
2.0b17
2.0b18
2.0b19
2.0b21
+ 199 more Show less
2.0b22
2.0b24
2.0b25
2.0b26
2.0b27
2.0b28
2.0b29
2.0b3
2.0b30
2.0b31
2.0b32
2.0b33
2.0b34
2.0b35
2.0b36
2.0b37
2.0b38
2.0b39
2.0b4
2.0b40
2.0b41
2.0b42
2.0b43
2.0b44
2.0b45
2.0b46
2.0b48
2.0b49
2.0b5
2.0b50
2.0b51
2.0b52
2.0b53
2.0b54
2.0b55
2.0b57
2.0b58
2.0b59
2.0b60
2.0b61
2.0b62
2.0b63
2.0b64
2.0b7
2.0c1
2.0c12
2.0c13
2.0c2
2.0c3
2.0c4
2.0c5
2.0c7
2.0c8
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10rc0
2.10rc1
2.10rc2
2.10rc3
2.10rc4
2.10rc5
2.4
2.4.1
2.4a1
2.4a10
2.4a11
2.4a12
2.4a13
2.4a14
2.4a15
2.4a16
2.4a17
2.4a18
2.4a19
2.4a2
2.4a20
2.4a21
2.4a22
2.4a23
2.4a24
2.4a25
2.4a26
2.4a28
2.4a29
2.4a3
2.4a30
2.4a31
2.4a32
2.4a33
2.4a34
2.4a35
2.4a36
2.4a38
2.4a4
2.4a5
2.4a6
2.4a7
2.4a8
2.4a9
2.4b1
2.4b10
2.4b11
2.4b12
2.4b13
2.4b14
2.4b15
2.4b16
2.4b17
2.4b18
2.4b19
2.4b2
2.4b20
2.4b21
2.4b22
2.4b23
2.4b24
2.4b25
2.4b26
2.4b27
2.4b28
2.4b3
2.4b4
2.4b5
2.4b6
2.4b7
2.4b8
2.4c1
2.4c2
2.4c3
2.4c4
2.5.1
2.5.10
2.5.12
2.5.13
2.5.14
2.5.15
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.9
2.5.9.dev20170116091328
2.5.dev20160825082804
2.6
2.6.1
2.6.2
2.6.3
2.6a1
2.6c1
2.7
2.7.1.dev20171013151516
2.7.2.dev20171013181854
2.7.4.dev20171114161428
2.7.5.dev20180123130714
2.7.5.dev20180125135927
2.8
2.8.1
2.8.1rc0
2.8rc0
2.8rc1
2.8rc10
2.8rc11
2.8rc12
2.8rc13
2.8rc2
2.8rc3
2.8rc4
2.8rc5
2.8rc6
2.8rc7
2.8rc8
2.8rc9
3.0.0
3.1.0
3.1.1
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
Fixed in
4.0.3
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
4.0.1
patch
6 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-26043
GHSA-mcmc-c59m-pqq8
PYSEC-2023-15
Aug 30, 2024
GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
High
Network
Low
Low
None
SummaryGeoNode is vulnerable to an XML External Entity (XXE) injection in the style upload functionality of GeoServer leading to Arbitrary File Read. DetailsGeoNode's GeoServer has the ability to upload new styles for datasets through the
PoC
Sample response: ImpactThis issue may lead to authenticated Affected versions
2.0
2.0.1
2.0.dev20130913181950
2.0.dev20140626191247
2.0b10
2.0b11
2.0b12
2.0b13
2.0b17
2.0b18
2.0b19
2.0b21
+ 199 more Show less
2.0b22
2.0b24
2.0b25
2.0b26
2.0b27
2.0b28
2.0b29
2.0b3
2.0b30
2.0b31
2.0b32
2.0b33
2.0b34
2.0b35
2.0b36
2.0b37
2.0b38
2.0b39
2.0b4
2.0b40
2.0b41
2.0b42
2.0b43
2.0b44
2.0b45
2.0b46
2.0b48
2.0b49
2.0b5
2.0b50
2.0b51
2.0b52
2.0b53
2.0b54
2.0b55
2.0b57
2.0b58
2.0b59
2.0b60
2.0b61
2.0b62
2.0b63
2.0b64
2.0b7
2.0c1
2.0c12
2.0c13
2.0c2
2.0c3
2.0c4
2.0c5
2.0c7
2.0c8
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10rc0
2.10rc1
2.10rc2
2.10rc3
2.10rc4
2.10rc5
2.4
2.4.1
2.4a1
2.4a10
2.4a11
2.4a12
2.4a13
2.4a14
2.4a15
2.4a16
2.4a17
2.4a18
2.4a19
2.4a2
2.4a20
2.4a21
2.4a22
2.4a23
2.4a24
2.4a25
2.4a26
2.4a28
2.4a29
2.4a3
2.4a30
2.4a31
2.4a32
2.4a33
2.4a34
2.4a35
2.4a36
2.4a38
2.4a4
2.4a5
2.4a6
2.4a7
2.4a8
2.4a9
2.4b1
2.4b10
2.4b11
2.4b12
2.4b13
2.4b14
2.4b15
2.4b16
2.4b17
2.4b18
2.4b19
2.4b2
2.4b20
2.4b21
2.4b22
2.4b23
2.4b24
2.4b25
2.4b26
2.4b27
2.4b28
2.4b3
2.4b4
2.4b5
2.4b6
2.4b7
2.4b8
2.4c1
2.4c2
2.4c3
2.4c4
2.5.1
2.5.10
2.5.12
2.5.13
2.5.14
2.5.15
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.9
2.5.9.dev20170116091328
2.5.dev20160825082804
2.6
2.6.1
2.6.2
2.6.3
2.6a1
2.6c1
2.7
2.7.1.dev20171013151516
2.7.2.dev20171013181854
2.7.4.dev20171114161428
2.7.5.dev20180123130714
2.7.5.dev20180125135927
2.8
2.8.1
2.8.1rc0
2.8rc0
2.8rc1
2.8rc10
2.8rc11
2.8rc12
2.8rc13
2.8rc2
2.8rc3
2.8rc4
2.8rc5
2.8rc6
2.8rc7
2.8rc8
2.8rc9
3.0.0
3.1.0
3.1.1
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
Fixed in
4.0.3
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
4.0.0.post1
pre
6 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-26043
GHSA-mcmc-c59m-pqq8
PYSEC-2023-15
Aug 30, 2024
GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
High
Network
Low
Low
None
SummaryGeoNode is vulnerable to an XML External Entity (XXE) injection in the style upload functionality of GeoServer leading to Arbitrary File Read. DetailsGeoNode's GeoServer has the ability to upload new styles for datasets through the
PoC
Sample response: ImpactThis issue may lead to authenticated Affected versions
2.0
2.0.1
2.0.dev20130913181950
2.0.dev20140626191247
2.0b10
2.0b11
2.0b12
2.0b13
2.0b17
2.0b18
2.0b19
2.0b21
+ 199 more Show less
2.0b22
2.0b24
2.0b25
2.0b26
2.0b27
2.0b28
2.0b29
2.0b3
2.0b30
2.0b31
2.0b32
2.0b33
2.0b34
2.0b35
2.0b36
2.0b37
2.0b38
2.0b39
2.0b4
2.0b40
2.0b41
2.0b42
2.0b43
2.0b44
2.0b45
2.0b46
2.0b48
2.0b49
2.0b5
2.0b50
2.0b51
2.0b52
2.0b53
2.0b54
2.0b55
2.0b57
2.0b58
2.0b59
2.0b60
2.0b61
2.0b62
2.0b63
2.0b64
2.0b7
2.0c1
2.0c12
2.0c13
2.0c2
2.0c3
2.0c4
2.0c5
2.0c7
2.0c8
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10rc0
2.10rc1
2.10rc2
2.10rc3
2.10rc4
2.10rc5
2.4
2.4.1
2.4a1
2.4a10
2.4a11
2.4a12
2.4a13
2.4a14
2.4a15
2.4a16
2.4a17
2.4a18
2.4a19
2.4a2
2.4a20
2.4a21
2.4a22
2.4a23
2.4a24
2.4a25
2.4a26
2.4a28
2.4a29
2.4a3
2.4a30
2.4a31
2.4a32
2.4a33
2.4a34
2.4a35
2.4a36
2.4a38
2.4a4
2.4a5
2.4a6
2.4a7
2.4a8
2.4a9
2.4b1
2.4b10
2.4b11
2.4b12
2.4b13
2.4b14
2.4b15
2.4b16
2.4b17
2.4b18
2.4b19
2.4b2
2.4b20
2.4b21
2.4b22
2.4b23
2.4b24
2.4b25
2.4b26
2.4b27
2.4b28
2.4b3
2.4b4
2.4b5
2.4b6
2.4b7
2.4b8
2.4c1
2.4c2
2.4c3
2.4c4
2.5.1
2.5.10
2.5.12
2.5.13
2.5.14
2.5.15
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.9
2.5.9.dev20170116091328
2.5.dev20160825082804
2.6
2.6.1
2.6.2
2.6.3
2.6a1
2.6c1
2.7
2.7.1.dev20171013151516
2.7.2.dev20171013181854
2.7.4.dev20171114161428
2.7.5.dev20180123130714
2.7.5.dev20180125135927
2.8
2.8.1
2.8.1rc0
2.8rc0
2.8rc1
2.8rc10
2.8rc11
2.8rc12
2.8rc13
2.8rc2
2.8rc3
2.8rc4
2.8rc5
2.8rc6
2.8rc7
2.8rc8
2.8rc9
3.0.0
3.1.0
3.1.1
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
Fixed in
4.0.3
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
4.0.0
major
6 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2026-39922
GHSA-hw9r-6m78-w6h3
PYSEC-2026-61
Jun 08, 2026
GeoNode contains a server-side request forgery vulnerability in the service registration endpoint
Medium
Network
Low
Low
None
GeoNode versions 4.4.5 and 5.0.2 (and prior within their respective releases) contain a server-side request forgery vulnerability in the service registration endpoint that allows authenticated attackers to trigger outbound network requests to arbitrary URLs by submitting a crafted service URL during form validation. Attackers can probe internal network targets including loopback addresses, RFC1918 private IP ranges, link-local addresses, and cloud metadata services by exploiting insufficient URL validation in the WMS service handler without private IP filtering or allowlist enforcement. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jun 08, 2026 · Source: OSV.dev
CVE-2026-39921
PYSEC-2026-2159
Apr 10, 2026
6.3
/ 10
Medium
Network
Low
Low
None
Unchanged
Low
Low
Low
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. Affected versions
4.0.0
4.0.0.post1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
+ 16 more Show less
4.2.0
4.2.1
4.2.2
4.2.3
4.2.4
4.2.5
4.3.0
4.3.0.post1
4.3.1
4.4.0
4.4.1
4.4.2
4.4.3
4.4.4
5.0.0
5.0.1
Fixed in
4.4.5
5.0.2
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-26043
GHSA-mcmc-c59m-pqq8
PYSEC-2023-15
Aug 30, 2024
GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
High
Network
Low
Low
None
SummaryGeoNode is vulnerable to an XML External Entity (XXE) injection in the style upload functionality of GeoServer leading to Arbitrary File Read. DetailsGeoNode's GeoServer has the ability to upload new styles for datasets through the
PoC
Sample response: ImpactThis issue may lead to authenticated Affected versions
2.0
2.0.1
2.0.dev20130913181950
2.0.dev20140626191247
2.0b10
2.0b11
2.0b12
2.0b13
2.0b17
2.0b18
2.0b19
2.0b21
+ 199 more Show less
2.0b22
2.0b24
2.0b25
2.0b26
2.0b27
2.0b28
2.0b29
2.0b3
2.0b30
2.0b31
2.0b32
2.0b33
2.0b34
2.0b35
2.0b36
2.0b37
2.0b38
2.0b39
2.0b4
2.0b40
2.0b41
2.0b42
2.0b43
2.0b44
2.0b45
2.0b46
2.0b48
2.0b49
2.0b5
2.0b50
2.0b51
2.0b52
2.0b53
2.0b54
2.0b55
2.0b57
2.0b58
2.0b59
2.0b60
2.0b61
2.0b62
2.0b63
2.0b64
2.0b7
2.0c1
2.0c12
2.0c13
2.0c2
2.0c3
2.0c4
2.0c5
2.0c7
2.0c8
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10rc0
2.10rc1
2.10rc2
2.10rc3
2.10rc4
2.10rc5
2.4
2.4.1
2.4a1
2.4a10
2.4a11
2.4a12
2.4a13
2.4a14
2.4a15
2.4a16
2.4a17
2.4a18
2.4a19
2.4a2
2.4a20
2.4a21
2.4a22
2.4a23
2.4a24
2.4a25
2.4a26
2.4a28
2.4a29
2.4a3
2.4a30
2.4a31
2.4a32
2.4a33
2.4a34
2.4a35
2.4a36
2.4a38
2.4a4
2.4a5
2.4a6
2.4a7
2.4a8
2.4a9
2.4b1
2.4b10
2.4b11
2.4b12
2.4b13
2.4b14
2.4b15
2.4b16
2.4b17
2.4b18
2.4b19
2.4b2
2.4b20
2.4b21
2.4b22
2.4b23
2.4b24
2.4b25
2.4b26
2.4b27
2.4b28
2.4b3
2.4b4
2.4b5
2.4b6
2.4b7
2.4b8
2.4c1
2.4c2
2.4c3
2.4c4
2.5.1
2.5.10
2.5.12
2.5.13
2.5.14
2.5.15
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.9
2.5.9.dev20170116091328
2.5.dev20160825082804
2.6
2.6.1
2.6.2
2.6.3
2.6a1
2.6c1
2.7
2.7.1.dev20171013151516
2.7.2.dev20171013181854
2.7.4.dev20171114161428
2.7.5.dev20180123130714
2.7.5.dev20180125135927
2.8
2.8.1
2.8.1rc0
2.8rc0
2.8rc1
2.8rc10
2.8rc11
2.8rc12
2.8rc13
2.8rc2
2.8rc3
2.8rc4
2.8rc5
2.8rc6
2.8rc7
2.8rc8
2.8rc9
3.0.0
3.1.0
3.1.1
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
Fixed in
4.0.3
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
4.0.0rc1
pre
4 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-26043
GHSA-mcmc-c59m-pqq8
PYSEC-2023-15
Aug 30, 2024
GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
High
Network
Low
Low
None
SummaryGeoNode is vulnerable to an XML External Entity (XXE) injection in the style upload functionality of GeoServer leading to Arbitrary File Read. DetailsGeoNode's GeoServer has the ability to upload new styles for datasets through the
PoC
Sample response: ImpactThis issue may lead to authenticated Affected versions
2.0
2.0.1
2.0.dev20130913181950
2.0.dev20140626191247
2.0b10
2.0b11
2.0b12
2.0b13
2.0b17
2.0b18
2.0b19
2.0b21
+ 199 more Show less
2.0b22
2.0b24
2.0b25
2.0b26
2.0b27
2.0b28
2.0b29
2.0b3
2.0b30
2.0b31
2.0b32
2.0b33
2.0b34
2.0b35
2.0b36
2.0b37
2.0b38
2.0b39
2.0b4
2.0b40
2.0b41
2.0b42
2.0b43
2.0b44
2.0b45
2.0b46
2.0b48
2.0b49
2.0b5
2.0b50
2.0b51
2.0b52
2.0b53
2.0b54
2.0b55
2.0b57
2.0b58
2.0b59
2.0b60
2.0b61
2.0b62
2.0b63
2.0b64
2.0b7
2.0c1
2.0c12
2.0c13
2.0c2
2.0c3
2.0c4
2.0c5
2.0c7
2.0c8
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10rc0
2.10rc1
2.10rc2
2.10rc3
2.10rc4
2.10rc5
2.4
2.4.1
2.4a1
2.4a10
2.4a11
2.4a12
2.4a13
2.4a14
2.4a15
2.4a16
2.4a17
2.4a18
2.4a19
2.4a2
2.4a20
2.4a21
2.4a22
2.4a23
2.4a24
2.4a25
2.4a26
2.4a28
2.4a29
2.4a3
2.4a30
2.4a31
2.4a32
2.4a33
2.4a34
2.4a35
2.4a36
2.4a38
2.4a4
2.4a5
2.4a6
2.4a7
2.4a8
2.4a9
2.4b1
2.4b10
2.4b11
2.4b12
2.4b13
2.4b14
2.4b15
2.4b16
2.4b17
2.4b18
2.4b19
2.4b2
2.4b20
2.4b21
2.4b22
2.4b23
2.4b24
2.4b25
2.4b26
2.4b27
2.4b28
2.4b3
2.4b4
2.4b5
2.4b6
2.4b7
2.4b8
2.4c1
2.4c2
2.4c3
2.4c4
2.5.1
2.5.10
2.5.12
2.5.13
2.5.14
2.5.15
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.9
2.5.9.dev20170116091328
2.5.dev20160825082804
2.6
2.6.1
2.6.2
2.6.3
2.6a1
2.6c1
2.7
2.7.1.dev20171013151516
2.7.2.dev20171013181854
2.7.4.dev20171114161428
2.7.5.dev20180123130714
2.7.5.dev20180125135927
2.8
2.8.1
2.8.1rc0
2.8rc0
2.8rc1
2.8rc10
2.8rc11
2.8rc12
2.8rc13
2.8rc2
2.8rc3
2.8rc4
2.8rc5
2.8rc6
2.8rc7
2.8rc8
2.8rc9
3.0.0
3.1.0
3.1.1
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
Fixed in
4.0.3
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
3.3.2.post2
pre
4 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-26043
GHSA-mcmc-c59m-pqq8
PYSEC-2023-15
Aug 30, 2024
GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
High
Network
Low
Low
None
SummaryGeoNode is vulnerable to an XML External Entity (XXE) injection in the style upload functionality of GeoServer leading to Arbitrary File Read. DetailsGeoNode's GeoServer has the ability to upload new styles for datasets through the
PoC
Sample response: ImpactThis issue may lead to authenticated Affected versions
2.0
2.0.1
2.0.dev20130913181950
2.0.dev20140626191247
2.0b10
2.0b11
2.0b12
2.0b13
2.0b17
2.0b18
2.0b19
2.0b21
+ 199 more Show less
2.0b22
2.0b24
2.0b25
2.0b26
2.0b27
2.0b28
2.0b29
2.0b3
2.0b30
2.0b31
2.0b32
2.0b33
2.0b34
2.0b35
2.0b36
2.0b37
2.0b38
2.0b39
2.0b4
2.0b40
2.0b41
2.0b42
2.0b43
2.0b44
2.0b45
2.0b46
2.0b48
2.0b49
2.0b5
2.0b50
2.0b51
2.0b52
2.0b53
2.0b54
2.0b55
2.0b57
2.0b58
2.0b59
2.0b60
2.0b61
2.0b62
2.0b63
2.0b64
2.0b7
2.0c1
2.0c12
2.0c13
2.0c2
2.0c3
2.0c4
2.0c5
2.0c7
2.0c8
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10rc0
2.10rc1
2.10rc2
2.10rc3
2.10rc4
2.10rc5
2.4
2.4.1
2.4a1
2.4a10
2.4a11
2.4a12
2.4a13
2.4a14
2.4a15
2.4a16
2.4a17
2.4a18
2.4a19
2.4a2
2.4a20
2.4a21
2.4a22
2.4a23
2.4a24
2.4a25
2.4a26
2.4a28
2.4a29
2.4a3
2.4a30
2.4a31
2.4a32
2.4a33
2.4a34
2.4a35
2.4a36
2.4a38
2.4a4
2.4a5
2.4a6
2.4a7
2.4a8
2.4a9
2.4b1
2.4b10
2.4b11
2.4b12
2.4b13
2.4b14
2.4b15
2.4b16
2.4b17
2.4b18
2.4b19
2.4b2
2.4b20
2.4b21
2.4b22
2.4b23
2.4b24
2.4b25
2.4b26
2.4b27
2.4b28
2.4b3
2.4b4
2.4b5
2.4b6
2.4b7
2.4b8
2.4c1
2.4c2
2.4c3
2.4c4
2.5.1
2.5.10
2.5.12
2.5.13
2.5.14
2.5.15
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.9
2.5.9.dev20170116091328
2.5.dev20160825082804
2.6
2.6.1
2.6.2
2.6.3
2.6a1
2.6c1
2.7
2.7.1.dev20171013151516
2.7.2.dev20171013181854
2.7.4.dev20171114161428
2.7.5.dev20180123130714
2.7.5.dev20180125135927
2.8
2.8.1
2.8.1rc0
2.8rc0
2.8rc1
2.8rc10
2.8rc11
2.8rc12
2.8rc13
2.8rc2
2.8rc3
2.8rc4
2.8rc5
2.8rc6
2.8rc7
2.8rc8
2.8rc9
3.0.0
3.1.0
3.1.1
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
Fixed in
4.0.3
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
3.3.2.post1
pre
4 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-26043
GHSA-mcmc-c59m-pqq8
PYSEC-2023-15
Aug 30, 2024
GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
High
Network
Low
Low
None
SummaryGeoNode is vulnerable to an XML External Entity (XXE) injection in the style upload functionality of GeoServer leading to Arbitrary File Read. DetailsGeoNode's GeoServer has the ability to upload new styles for datasets through the
PoC
Sample response: ImpactThis issue may lead to authenticated Affected versions
2.0
2.0.1
2.0.dev20130913181950
2.0.dev20140626191247
2.0b10
2.0b11
2.0b12
2.0b13
2.0b17
2.0b18
2.0b19
2.0b21
+ 199 more Show less
2.0b22
2.0b24
2.0b25
2.0b26
2.0b27
2.0b28
2.0b29
2.0b3
2.0b30
2.0b31
2.0b32
2.0b33
2.0b34
2.0b35
2.0b36
2.0b37
2.0b38
2.0b39
2.0b4
2.0b40
2.0b41
2.0b42
2.0b43
2.0b44
2.0b45
2.0b46
2.0b48
2.0b49
2.0b5
2.0b50
2.0b51
2.0b52
2.0b53
2.0b54
2.0b55
2.0b57
2.0b58
2.0b59
2.0b60
2.0b61
2.0b62
2.0b63
2.0b64
2.0b7
2.0c1
2.0c12
2.0c13
2.0c2
2.0c3
2.0c4
2.0c5
2.0c7
2.0c8
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10rc0
2.10rc1
2.10rc2
2.10rc3
2.10rc4
2.10rc5
2.4
2.4.1
2.4a1
2.4a10
2.4a11
2.4a12
2.4a13
2.4a14
2.4a15
2.4a16
2.4a17
2.4a18
2.4a19
2.4a2
2.4a20
2.4a21
2.4a22
2.4a23
2.4a24
2.4a25
2.4a26
2.4a28
2.4a29
2.4a3
2.4a30
2.4a31
2.4a32
2.4a33
2.4a34
2.4a35
2.4a36
2.4a38
2.4a4
2.4a5
2.4a6
2.4a7
2.4a8
2.4a9
2.4b1
2.4b10
2.4b11
2.4b12
2.4b13
2.4b14
2.4b15
2.4b16
2.4b17
2.4b18
2.4b19
2.4b2
2.4b20
2.4b21
2.4b22
2.4b23
2.4b24
2.4b25
2.4b26
2.4b27
2.4b28
2.4b3
2.4b4
2.4b5
2.4b6
2.4b7
2.4b8
2.4c1
2.4c2
2.4c3
2.4c4
2.5.1
2.5.10
2.5.12
2.5.13
2.5.14
2.5.15
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.9
2.5.9.dev20170116091328
2.5.dev20160825082804
2.6
2.6.1
2.6.2
2.6.3
2.6a1
2.6c1
2.7
2.7.1.dev20171013151516
2.7.2.dev20171013181854
2.7.4.dev20171114161428
2.7.5.dev20180123130714
2.7.5.dev20180125135927
2.8
2.8.1
2.8.1rc0
2.8rc0
2.8rc1
2.8rc10
2.8rc11
2.8rc12
2.8rc13
2.8rc2
2.8rc3
2.8rc4
2.8rc5
2.8rc6
2.8rc7
2.8rc8
2.8rc9
3.0.0
3.1.0
3.1.1
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
Fixed in
4.0.3
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
3.3.2
patch
4 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-26043
GHSA-mcmc-c59m-pqq8
PYSEC-2023-15
Aug 30, 2024
GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
High
Network
Low
Low
None
SummaryGeoNode is vulnerable to an XML External Entity (XXE) injection in the style upload functionality of GeoServer leading to Arbitrary File Read. DetailsGeoNode's GeoServer has the ability to upload new styles for datasets through the
PoC
Sample response: ImpactThis issue may lead to authenticated Affected versions
2.0
2.0.1
2.0.dev20130913181950
2.0.dev20140626191247
2.0b10
2.0b11
2.0b12
2.0b13
2.0b17
2.0b18
2.0b19
2.0b21
+ 199 more Show less
2.0b22
2.0b24
2.0b25
2.0b26
2.0b27
2.0b28
2.0b29
2.0b3
2.0b30
2.0b31
2.0b32
2.0b33
2.0b34
2.0b35
2.0b36
2.0b37
2.0b38
2.0b39
2.0b4
2.0b40
2.0b41
2.0b42
2.0b43
2.0b44
2.0b45
2.0b46
2.0b48
2.0b49
2.0b5
2.0b50
2.0b51
2.0b52
2.0b53
2.0b54
2.0b55
2.0b57
2.0b58
2.0b59
2.0b60
2.0b61
2.0b62
2.0b63
2.0b64
2.0b7
2.0c1
2.0c12
2.0c13
2.0c2
2.0c3
2.0c4
2.0c5
2.0c7
2.0c8
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10rc0
2.10rc1
2.10rc2
2.10rc3
2.10rc4
2.10rc5
2.4
2.4.1
2.4a1
2.4a10
2.4a11
2.4a12
2.4a13
2.4a14
2.4a15
2.4a16
2.4a17
2.4a18
2.4a19
2.4a2
2.4a20
2.4a21
2.4a22
2.4a23
2.4a24
2.4a25
2.4a26
2.4a28
2.4a29
2.4a3
2.4a30
2.4a31
2.4a32
2.4a33
2.4a34
2.4a35
2.4a36
2.4a38
2.4a4
2.4a5
2.4a6
2.4a7
2.4a8
2.4a9
2.4b1
2.4b10
2.4b11
2.4b12
2.4b13
2.4b14
2.4b15
2.4b16
2.4b17
2.4b18
2.4b19
2.4b2
2.4b20
2.4b21
2.4b22
2.4b23
2.4b24
2.4b25
2.4b26
2.4b27
2.4b28
2.4b3
2.4b4
2.4b5
2.4b6
2.4b7
2.4b8
2.4c1
2.4c2
2.4c3
2.4c4
2.5.1
2.5.10
2.5.12
2.5.13
2.5.14
2.5.15
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.9
2.5.9.dev20170116091328
2.5.dev20160825082804
2.6
2.6.1
2.6.2
2.6.3
2.6a1
2.6c1
2.7
2.7.1.dev20171013151516
2.7.2.dev20171013181854
2.7.4.dev20171114161428
2.7.5.dev20180123130714
2.7.5.dev20180125135927
2.8
2.8.1
2.8.1rc0
2.8rc0
2.8rc1
2.8rc10
2.8rc11
2.8rc12
2.8rc13
2.8rc2
2.8rc3
2.8rc4
2.8rc5
2.8rc6
2.8rc7
2.8rc8
2.8rc9
3.0.0
3.1.0
3.1.1
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
Fixed in
4.0.3
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
3.2.4
patch
4 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-26043
GHSA-mcmc-c59m-pqq8
PYSEC-2023-15
Aug 30, 2024
GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
High
Network
Low
Low
None
SummaryGeoNode is vulnerable to an XML External Entity (XXE) injection in the style upload functionality of GeoServer leading to Arbitrary File Read. DetailsGeoNode's GeoServer has the ability to upload new styles for datasets through the
PoC
Sample response: ImpactThis issue may lead to authenticated Affected versions
2.0
2.0.1
2.0.dev20130913181950
2.0.dev20140626191247
2.0b10
2.0b11
2.0b12
2.0b13
2.0b17
2.0b18
2.0b19
2.0b21
+ 199 more Show less
2.0b22
2.0b24
2.0b25
2.0b26
2.0b27
2.0b28
2.0b29
2.0b3
2.0b30
2.0b31
2.0b32
2.0b33
2.0b34
2.0b35
2.0b36
2.0b37
2.0b38
2.0b39
2.0b4
2.0b40
2.0b41
2.0b42
2.0b43
2.0b44
2.0b45
2.0b46
2.0b48
2.0b49
2.0b5
2.0b50
2.0b51
2.0b52
2.0b53
2.0b54
2.0b55
2.0b57
2.0b58
2.0b59
2.0b60
2.0b61
2.0b62
2.0b63
2.0b64
2.0b7
2.0c1
2.0c12
2.0c13
2.0c2
2.0c3
2.0c4
2.0c5
2.0c7
2.0c8
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10rc0
2.10rc1
2.10rc2
2.10rc3
2.10rc4
2.10rc5
2.4
2.4.1
2.4a1
2.4a10
2.4a11
2.4a12
2.4a13
2.4a14
2.4a15
2.4a16
2.4a17
2.4a18
2.4a19
2.4a2
2.4a20
2.4a21
2.4a22
2.4a23
2.4a24
2.4a25
2.4a26
2.4a28
2.4a29
2.4a3
2.4a30
2.4a31
2.4a32
2.4a33
2.4a34
2.4a35
2.4a36
2.4a38
2.4a4
2.4a5
2.4a6
2.4a7
2.4a8
2.4a9
2.4b1
2.4b10
2.4b11
2.4b12
2.4b13
2.4b14
2.4b15
2.4b16
2.4b17
2.4b18
2.4b19
2.4b2
2.4b20
2.4b21
2.4b22
2.4b23
2.4b24
2.4b25
2.4b26
2.4b27
2.4b28
2.4b3
2.4b4
2.4b5
2.4b6
2.4b7
2.4b8
2.4c1
2.4c2
2.4c3
2.4c4
2.5.1
2.5.10
2.5.12
2.5.13
2.5.14
2.5.15
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.9
2.5.9.dev20170116091328
2.5.dev20160825082804
2.6
2.6.1
2.6.2
2.6.3
2.6a1
2.6c1
2.7
2.7.1.dev20171013151516
2.7.2.dev20171013181854
2.7.4.dev20171114161428
2.7.5.dev20180123130714
2.7.5.dev20180125135927
2.8
2.8.1
2.8.1rc0
2.8rc0
2.8rc1
2.8rc10
2.8rc11
2.8rc12
2.8rc13
2.8rc2
2.8rc3
2.8rc4
2.8rc5
2.8rc6
2.8rc7
2.8rc8
2.8rc9
3.0.0
3.1.0
3.1.1
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
Fixed in
4.0.3
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
4.0.0rc0
pre
4 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-26043
GHSA-mcmc-c59m-pqq8
PYSEC-2023-15
Aug 30, 2024
GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
High
Network
Low
Low
None
SummaryGeoNode is vulnerable to an XML External Entity (XXE) injection in the style upload functionality of GeoServer leading to Arbitrary File Read. DetailsGeoNode's GeoServer has the ability to upload new styles for datasets through the
PoC
Sample response: ImpactThis issue may lead to authenticated Affected versions
2.0
2.0.1
2.0.dev20130913181950
2.0.dev20140626191247
2.0b10
2.0b11
2.0b12
2.0b13
2.0b17
2.0b18
2.0b19
2.0b21
+ 199 more Show less
2.0b22
2.0b24
2.0b25
2.0b26
2.0b27
2.0b28
2.0b29
2.0b3
2.0b30
2.0b31
2.0b32
2.0b33
2.0b34
2.0b35
2.0b36
2.0b37
2.0b38
2.0b39
2.0b4
2.0b40
2.0b41
2.0b42
2.0b43
2.0b44
2.0b45
2.0b46
2.0b48
2.0b49
2.0b5
2.0b50
2.0b51
2.0b52
2.0b53
2.0b54
2.0b55
2.0b57
2.0b58
2.0b59
2.0b60
2.0b61
2.0b62
2.0b63
2.0b64
2.0b7
2.0c1
2.0c12
2.0c13
2.0c2
2.0c3
2.0c4
2.0c5
2.0c7
2.0c8
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10rc0
2.10rc1
2.10rc2
2.10rc3
2.10rc4
2.10rc5
2.4
2.4.1
2.4a1
2.4a10
2.4a11
2.4a12
2.4a13
2.4a14
2.4a15
2.4a16
2.4a17
2.4a18
2.4a19
2.4a2
2.4a20
2.4a21
2.4a22
2.4a23
2.4a24
2.4a25
2.4a26
2.4a28
2.4a29
2.4a3
2.4a30
2.4a31
2.4a32
2.4a33
2.4a34
2.4a35
2.4a36
2.4a38
2.4a4
2.4a5
2.4a6
2.4a7
2.4a8
2.4a9
2.4b1
2.4b10
2.4b11
2.4b12
2.4b13
2.4b14
2.4b15
2.4b16
2.4b17
2.4b18
2.4b19
2.4b2
2.4b20
2.4b21
2.4b22
2.4b23
2.4b24
2.4b25
2.4b26
2.4b27
2.4b28
2.4b3
2.4b4
2.4b5
2.4b6
2.4b7
2.4b8
2.4c1
2.4c2
2.4c3
2.4c4
2.5.1
2.5.10
2.5.12
2.5.13
2.5.14
2.5.15
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.9
2.5.9.dev20170116091328
2.5.dev20160825082804
2.6
2.6.1
2.6.2
2.6.3
2.6a1
2.6c1
2.7
2.7.1.dev20171013151516
2.7.2.dev20171013181854
2.7.4.dev20171114161428
2.7.5.dev20180123130714
2.7.5.dev20180125135927
2.8
2.8.1
2.8.1rc0
2.8rc0
2.8rc1
2.8rc10
2.8rc11
2.8rc12
2.8rc13
2.8rc2
2.8rc3
2.8rc4
2.8rc5
2.8rc6
2.8rc7
2.8rc8
2.8rc9
3.0.0
3.1.0
3.1.1
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
Fixed in
4.0.3
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
3.3.1.post1
pre
4 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-26043
GHSA-mcmc-c59m-pqq8
PYSEC-2023-15
Aug 30, 2024
GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
High
Network
Low
Low
None
SummaryGeoNode is vulnerable to an XML External Entity (XXE) injection in the style upload functionality of GeoServer leading to Arbitrary File Read. DetailsGeoNode's GeoServer has the ability to upload new styles for datasets through the
PoC
Sample response: ImpactThis issue may lead to authenticated Affected versions
2.0
2.0.1
2.0.dev20130913181950
2.0.dev20140626191247
2.0b10
2.0b11
2.0b12
2.0b13
2.0b17
2.0b18
2.0b19
2.0b21
+ 199 more Show less
2.0b22
2.0b24
2.0b25
2.0b26
2.0b27
2.0b28
2.0b29
2.0b3
2.0b30
2.0b31
2.0b32
2.0b33
2.0b34
2.0b35
2.0b36
2.0b37
2.0b38
2.0b39
2.0b4
2.0b40
2.0b41
2.0b42
2.0b43
2.0b44
2.0b45
2.0b46
2.0b48
2.0b49
2.0b5
2.0b50
2.0b51
2.0b52
2.0b53
2.0b54
2.0b55
2.0b57
2.0b58
2.0b59
2.0b60
2.0b61
2.0b62
2.0b63
2.0b64
2.0b7
2.0c1
2.0c12
2.0c13
2.0c2
2.0c3
2.0c4
2.0c5
2.0c7
2.0c8
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10rc0
2.10rc1
2.10rc2
2.10rc3
2.10rc4
2.10rc5
2.4
2.4.1
2.4a1
2.4a10
2.4a11
2.4a12
2.4a13
2.4a14
2.4a15
2.4a16
2.4a17
2.4a18
2.4a19
2.4a2
2.4a20
2.4a21
2.4a22
2.4a23
2.4a24
2.4a25
2.4a26
2.4a28
2.4a29
2.4a3
2.4a30
2.4a31
2.4a32
2.4a33
2.4a34
2.4a35
2.4a36
2.4a38
2.4a4
2.4a5
2.4a6
2.4a7
2.4a8
2.4a9
2.4b1
2.4b10
2.4b11
2.4b12
2.4b13
2.4b14
2.4b15
2.4b16
2.4b17
2.4b18
2.4b19
2.4b2
2.4b20
2.4b21
2.4b22
2.4b23
2.4b24
2.4b25
2.4b26
2.4b27
2.4b28
2.4b3
2.4b4
2.4b5
2.4b6
2.4b7
2.4b8
2.4c1
2.4c2
2.4c3
2.4c4
2.5.1
2.5.10
2.5.12
2.5.13
2.5.14
2.5.15
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.9
2.5.9.dev20170116091328
2.5.dev20160825082804
2.6
2.6.1
2.6.2
2.6.3
2.6a1
2.6c1
2.7
2.7.1.dev20171013151516
2.7.2.dev20171013181854
2.7.4.dev20171114161428
2.7.5.dev20180123130714
2.7.5.dev20180125135927
2.8
2.8.1
2.8.1rc0
2.8rc0
2.8rc1
2.8rc10
2.8rc11
2.8rc12
2.8rc13
2.8rc2
2.8rc3
2.8rc4
2.8rc5
2.8rc6
2.8rc7
2.8rc8
2.8rc9
3.0.0
3.1.0
3.1.1
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
Fixed in
4.0.3
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
3.2.3.post1
pre
4 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-26043
GHSA-mcmc-c59m-pqq8
PYSEC-2023-15
Aug 30, 2024
GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
High
Network
Low
Low
None
SummaryGeoNode is vulnerable to an XML External Entity (XXE) injection in the style upload functionality of GeoServer leading to Arbitrary File Read. DetailsGeoNode's GeoServer has the ability to upload new styles for datasets through the
PoC
Sample response: ImpactThis issue may lead to authenticated Affected versions
2.0
2.0.1
2.0.dev20130913181950
2.0.dev20140626191247
2.0b10
2.0b11
2.0b12
2.0b13
2.0b17
2.0b18
2.0b19
2.0b21
+ 199 more Show less
2.0b22
2.0b24
2.0b25
2.0b26
2.0b27
2.0b28
2.0b29
2.0b3
2.0b30
2.0b31
2.0b32
2.0b33
2.0b34
2.0b35
2.0b36
2.0b37
2.0b38
2.0b39
2.0b4
2.0b40
2.0b41
2.0b42
2.0b43
2.0b44
2.0b45
2.0b46
2.0b48
2.0b49
2.0b5
2.0b50
2.0b51
2.0b52
2.0b53
2.0b54
2.0b55
2.0b57
2.0b58
2.0b59
2.0b60
2.0b61
2.0b62
2.0b63
2.0b64
2.0b7
2.0c1
2.0c12
2.0c13
2.0c2
2.0c3
2.0c4
2.0c5
2.0c7
2.0c8
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10rc0
2.10rc1
2.10rc2
2.10rc3
2.10rc4
2.10rc5
2.4
2.4.1
2.4a1
2.4a10
2.4a11
2.4a12
2.4a13
2.4a14
2.4a15
2.4a16
2.4a17
2.4a18
2.4a19
2.4a2
2.4a20
2.4a21
2.4a22
2.4a23
2.4a24
2.4a25
2.4a26
2.4a28
2.4a29
2.4a3
2.4a30
2.4a31
2.4a32
2.4a33
2.4a34
2.4a35
2.4a36
2.4a38
2.4a4
2.4a5
2.4a6
2.4a7
2.4a8
2.4a9
2.4b1
2.4b10
2.4b11
2.4b12
2.4b13
2.4b14
2.4b15
2.4b16
2.4b17
2.4b18
2.4b19
2.4b2
2.4b20
2.4b21
2.4b22
2.4b23
2.4b24
2.4b25
2.4b26
2.4b27
2.4b28
2.4b3
2.4b4
2.4b5
2.4b6
2.4b7
2.4b8
2.4c1
2.4c2
2.4c3
2.4c4
2.5.1
2.5.10
2.5.12
2.5.13
2.5.14
2.5.15
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.9
2.5.9.dev20170116091328
2.5.dev20160825082804
2.6
2.6.1
2.6.2
2.6.3
2.6a1
2.6c1
2.7
2.7.1.dev20171013151516
2.7.2.dev20171013181854
2.7.4.dev20171114161428
2.7.5.dev20180123130714
2.7.5.dev20180125135927
2.8
2.8.1
2.8.1rc0
2.8rc0
2.8rc1
2.8rc10
2.8rc11
2.8rc12
2.8rc13
2.8rc2
2.8rc3
2.8rc4
2.8rc5
2.8rc6
2.8rc7
2.8rc8
2.8rc9
3.0.0
3.1.0
3.1.1
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
Fixed in
4.0.3
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
3.2.3
patch
4 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-26043
GHSA-mcmc-c59m-pqq8
PYSEC-2023-15
Aug 30, 2024
GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
High
Network
Low
Low
None
SummaryGeoNode is vulnerable to an XML External Entity (XXE) injection in the style upload functionality of GeoServer leading to Arbitrary File Read. DetailsGeoNode's GeoServer has the ability to upload new styles for datasets through the
PoC
Sample response: ImpactThis issue may lead to authenticated Affected versions
2.0
2.0.1
2.0.dev20130913181950
2.0.dev20140626191247
2.0b10
2.0b11
2.0b12
2.0b13
2.0b17
2.0b18
2.0b19
2.0b21
+ 199 more Show less
2.0b22
2.0b24
2.0b25
2.0b26
2.0b27
2.0b28
2.0b29
2.0b3
2.0b30
2.0b31
2.0b32
2.0b33
2.0b34
2.0b35
2.0b36
2.0b37
2.0b38
2.0b39
2.0b4
2.0b40
2.0b41
2.0b42
2.0b43
2.0b44
2.0b45
2.0b46
2.0b48
2.0b49
2.0b5
2.0b50
2.0b51
2.0b52
2.0b53
2.0b54
2.0b55
2.0b57
2.0b58
2.0b59
2.0b60
2.0b61
2.0b62
2.0b63
2.0b64
2.0b7
2.0c1
2.0c12
2.0c13
2.0c2
2.0c3
2.0c4
2.0c5
2.0c7
2.0c8
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10rc0
2.10rc1
2.10rc2
2.10rc3
2.10rc4
2.10rc5
2.4
2.4.1
2.4a1
2.4a10
2.4a11
2.4a12
2.4a13
2.4a14
2.4a15
2.4a16
2.4a17
2.4a18
2.4a19
2.4a2
2.4a20
2.4a21
2.4a22
2.4a23
2.4a24
2.4a25
2.4a26
2.4a28
2.4a29
2.4a3
2.4a30
2.4a31
2.4a32
2.4a33
2.4a34
2.4a35
2.4a36
2.4a38
2.4a4
2.4a5
2.4a6
2.4a7
2.4a8
2.4a9
2.4b1
2.4b10
2.4b11
2.4b12
2.4b13
2.4b14
2.4b15
2.4b16
2.4b17
2.4b18
2.4b19
2.4b2
2.4b20
2.4b21
2.4b22
2.4b23
2.4b24
2.4b25
2.4b26
2.4b27
2.4b28
2.4b3
2.4b4
2.4b5
2.4b6
2.4b7
2.4b8
2.4c1
2.4c2
2.4c3
2.4c4
2.5.1
2.5.10
2.5.12
2.5.13
2.5.14
2.5.15
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.9
2.5.9.dev20170116091328
2.5.dev20160825082804
2.6
2.6.1
2.6.2
2.6.3
2.6a1
2.6c1
2.7
2.7.1.dev20171013151516
2.7.2.dev20171013181854
2.7.4.dev20171114161428
2.7.5.dev20180123130714
2.7.5.dev20180125135927
2.8
2.8.1
2.8.1rc0
2.8rc0
2.8rc1
2.8rc10
2.8rc11
2.8rc12
2.8rc13
2.8rc2
2.8rc3
2.8rc4
2.8rc5
2.8rc6
2.8rc7
2.8rc8
2.8rc9
3.0.0
3.1.0
3.1.1
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
Fixed in
4.0.3
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
3.3.1
patch
4 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-26043
GHSA-mcmc-c59m-pqq8
PYSEC-2023-15
Aug 30, 2024
GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
High
Network
Low
Low
None
SummaryGeoNode is vulnerable to an XML External Entity (XXE) injection in the style upload functionality of GeoServer leading to Arbitrary File Read. DetailsGeoNode's GeoServer has the ability to upload new styles for datasets through the
PoC
Sample response: ImpactThis issue may lead to authenticated Affected versions
2.0
2.0.1
2.0.dev20130913181950
2.0.dev20140626191247
2.0b10
2.0b11
2.0b12
2.0b13
2.0b17
2.0b18
2.0b19
2.0b21
+ 199 more Show less
2.0b22
2.0b24
2.0b25
2.0b26
2.0b27
2.0b28
2.0b29
2.0b3
2.0b30
2.0b31
2.0b32
2.0b33
2.0b34
2.0b35
2.0b36
2.0b37
2.0b38
2.0b39
2.0b4
2.0b40
2.0b41
2.0b42
2.0b43
2.0b44
2.0b45
2.0b46
2.0b48
2.0b49
2.0b5
2.0b50
2.0b51
2.0b52
2.0b53
2.0b54
2.0b55
2.0b57
2.0b58
2.0b59
2.0b60
2.0b61
2.0b62
2.0b63
2.0b64
2.0b7
2.0c1
2.0c12
2.0c13
2.0c2
2.0c3
2.0c4
2.0c5
2.0c7
2.0c8
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10rc0
2.10rc1
2.10rc2
2.10rc3
2.10rc4
2.10rc5
2.4
2.4.1
2.4a1
2.4a10
2.4a11
2.4a12
2.4a13
2.4a14
2.4a15
2.4a16
2.4a17
2.4a18
2.4a19
2.4a2
2.4a20
2.4a21
2.4a22
2.4a23
2.4a24
2.4a25
2.4a26
2.4a28
2.4a29
2.4a3
2.4a30
2.4a31
2.4a32
2.4a33
2.4a34
2.4a35
2.4a36
2.4a38
2.4a4
2.4a5
2.4a6
2.4a7
2.4a8
2.4a9
2.4b1
2.4b10
2.4b11
2.4b12
2.4b13
2.4b14
2.4b15
2.4b16
2.4b17
2.4b18
2.4b19
2.4b2
2.4b20
2.4b21
2.4b22
2.4b23
2.4b24
2.4b25
2.4b26
2.4b27
2.4b28
2.4b3
2.4b4
2.4b5
2.4b6
2.4b7
2.4b8
2.4c1
2.4c2
2.4c3
2.4c4
2.5.1
2.5.10
2.5.12
2.5.13
2.5.14
2.5.15
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.9
2.5.9.dev20170116091328
2.5.dev20160825082804
2.6
2.6.1
2.6.2
2.6.3
2.6a1
2.6c1
2.7
2.7.1.dev20171013151516
2.7.2.dev20171013181854
2.7.4.dev20171114161428
2.7.5.dev20180123130714
2.7.5.dev20180125135927
2.8
2.8.1
2.8.1rc0
2.8rc0
2.8rc1
2.8rc10
2.8rc11
2.8rc12
2.8rc13
2.8rc2
2.8rc3
2.8rc4
2.8rc5
2.8rc6
2.8rc7
2.8rc8
2.8rc9
3.0.0
3.1.0
3.1.1
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
Fixed in
4.0.3
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
3.3.0
minor
4 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-26043
GHSA-mcmc-c59m-pqq8
PYSEC-2023-15
Aug 30, 2024
GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
High
Network
Low
Low
None
SummaryGeoNode is vulnerable to an XML External Entity (XXE) injection in the style upload functionality of GeoServer leading to Arbitrary File Read. DetailsGeoNode's GeoServer has the ability to upload new styles for datasets through the
PoC
Sample response: ImpactThis issue may lead to authenticated Affected versions
2.0
2.0.1
2.0.dev20130913181950
2.0.dev20140626191247
2.0b10
2.0b11
2.0b12
2.0b13
2.0b17
2.0b18
2.0b19
2.0b21
+ 199 more Show less
2.0b22
2.0b24
2.0b25
2.0b26
2.0b27
2.0b28
2.0b29
2.0b3
2.0b30
2.0b31
2.0b32
2.0b33
2.0b34
2.0b35
2.0b36
2.0b37
2.0b38
2.0b39
2.0b4
2.0b40
2.0b41
2.0b42
2.0b43
2.0b44
2.0b45
2.0b46
2.0b48
2.0b49
2.0b5
2.0b50
2.0b51
2.0b52
2.0b53
2.0b54
2.0b55
2.0b57
2.0b58
2.0b59
2.0b60
2.0b61
2.0b62
2.0b63
2.0b64
2.0b7
2.0c1
2.0c12
2.0c13
2.0c2
2.0c3
2.0c4
2.0c5
2.0c7
2.0c8
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10rc0
2.10rc1
2.10rc2
2.10rc3
2.10rc4
2.10rc5
2.4
2.4.1
2.4a1
2.4a10
2.4a11
2.4a12
2.4a13
2.4a14
2.4a15
2.4a16
2.4a17
2.4a18
2.4a19
2.4a2
2.4a20
2.4a21
2.4a22
2.4a23
2.4a24
2.4a25
2.4a26
2.4a28
2.4a29
2.4a3
2.4a30
2.4a31
2.4a32
2.4a33
2.4a34
2.4a35
2.4a36
2.4a38
2.4a4
2.4a5
2.4a6
2.4a7
2.4a8
2.4a9
2.4b1
2.4b10
2.4b11
2.4b12
2.4b13
2.4b14
2.4b15
2.4b16
2.4b17
2.4b18
2.4b19
2.4b2
2.4b20
2.4b21
2.4b22
2.4b23
2.4b24
2.4b25
2.4b26
2.4b27
2.4b28
2.4b3
2.4b4
2.4b5
2.4b6
2.4b7
2.4b8
2.4c1
2.4c2
2.4c3
2.4c4
2.5.1
2.5.10
2.5.12
2.5.13
2.5.14
2.5.15
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.9
2.5.9.dev20170116091328
2.5.dev20160825082804
2.6
2.6.1
2.6.2
2.6.3
2.6a1
2.6c1
2.7
2.7.1.dev20171013151516
2.7.2.dev20171013181854
2.7.4.dev20171114161428
2.7.5.dev20180123130714
2.7.5.dev20180125135927
2.8
2.8.1
2.8.1rc0
2.8rc0
2.8rc1
2.8rc10
2.8rc11
2.8rc12
2.8rc13
2.8rc2
2.8rc3
2.8rc4
2.8rc5
2.8rc6
2.8rc7
2.8rc8
2.8rc9
3.0.0
3.1.0
3.1.1
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
Fixed in
4.0.3
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
3.2.2
patch
4 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-26043
GHSA-mcmc-c59m-pqq8
PYSEC-2023-15
Aug 30, 2024
GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
High
Network
Low
Low
None
SummaryGeoNode is vulnerable to an XML External Entity (XXE) injection in the style upload functionality of GeoServer leading to Arbitrary File Read. DetailsGeoNode's GeoServer has the ability to upload new styles for datasets through the
PoC
Sample response: ImpactThis issue may lead to authenticated Affected versions
2.0
2.0.1
2.0.dev20130913181950
2.0.dev20140626191247
2.0b10
2.0b11
2.0b12
2.0b13
2.0b17
2.0b18
2.0b19
2.0b21
+ 199 more Show less
2.0b22
2.0b24
2.0b25
2.0b26
2.0b27
2.0b28
2.0b29
2.0b3
2.0b30
2.0b31
2.0b32
2.0b33
2.0b34
2.0b35
2.0b36
2.0b37
2.0b38
2.0b39
2.0b4
2.0b40
2.0b41
2.0b42
2.0b43
2.0b44
2.0b45
2.0b46
2.0b48
2.0b49
2.0b5
2.0b50
2.0b51
2.0b52
2.0b53
2.0b54
2.0b55
2.0b57
2.0b58
2.0b59
2.0b60
2.0b61
2.0b62
2.0b63
2.0b64
2.0b7
2.0c1
2.0c12
2.0c13
2.0c2
2.0c3
2.0c4
2.0c5
2.0c7
2.0c8
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10rc0
2.10rc1
2.10rc2
2.10rc3
2.10rc4
2.10rc5
2.4
2.4.1
2.4a1
2.4a10
2.4a11
2.4a12
2.4a13
2.4a14
2.4a15
2.4a16
2.4a17
2.4a18
2.4a19
2.4a2
2.4a20
2.4a21
2.4a22
2.4a23
2.4a24
2.4a25
2.4a26
2.4a28
2.4a29
2.4a3
2.4a30
2.4a31
2.4a32
2.4a33
2.4a34
2.4a35
2.4a36
2.4a38
2.4a4
2.4a5
2.4a6
2.4a7
2.4a8
2.4a9
2.4b1
2.4b10
2.4b11
2.4b12
2.4b13
2.4b14
2.4b15
2.4b16
2.4b17
2.4b18
2.4b19
2.4b2
2.4b20
2.4b21
2.4b22
2.4b23
2.4b24
2.4b25
2.4b26
2.4b27
2.4b28
2.4b3
2.4b4
2.4b5
2.4b6
2.4b7
2.4b8
2.4c1
2.4c2
2.4c3
2.4c4
2.5.1
2.5.10
2.5.12
2.5.13
2.5.14
2.5.15
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.9
2.5.9.dev20170116091328
2.5.dev20160825082804
2.6
2.6.1
2.6.2
2.6.3
2.6a1
2.6c1
2.7
2.7.1.dev20171013151516
2.7.2.dev20171013181854
2.7.4.dev20171114161428
2.7.5.dev20180123130714
2.7.5.dev20180125135927
2.8
2.8.1
2.8.1rc0
2.8rc0
2.8rc1
2.8rc10
2.8rc11
2.8rc12
2.8rc13
2.8rc2
2.8rc3
2.8rc4
2.8rc5
2.8rc6
2.8rc7
2.8rc8
2.8rc9
3.0.0
3.1.0
3.1.1
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
Fixed in
4.0.3
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
3.2.1
patch
4 CVEs
CVE-2024-27091
GHSA-rwcv-whm8-fmxm
PYSEC-2024-320
Jul 13, 2026
GeoNode: Stored XSS to full account takeover
6.1
/ 10
Medium
Network
Low
None
Required
Changed
Low
Low
None
An issue exists within GEONODE where the current rich text editor is vulnerable to Stored XSS. The applications cookies are set securely, but it is possible to retrieve a victims CSRF token and issue a request to change another user's email address to perform a full account takeover. Due to the script element not impacting the CORS policy, requests will succeed. Affected versions
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
+ 17 more Show less
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
4.2.0
4.2.1
4.2.2
Fixed in
4.2.3
References
Updated Jul 13, 2026 · Source: OSV.dev
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-26043
GHSA-mcmc-c59m-pqq8
PYSEC-2023-15
Aug 30, 2024
GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
High
Network
Low
Low
None
SummaryGeoNode is vulnerable to an XML External Entity (XXE) injection in the style upload functionality of GeoServer leading to Arbitrary File Read. DetailsGeoNode's GeoServer has the ability to upload new styles for datasets through the
PoC
Sample response: ImpactThis issue may lead to authenticated Affected versions
2.0
2.0.1
2.0.dev20130913181950
2.0.dev20140626191247
2.0b10
2.0b11
2.0b12
2.0b13
2.0b17
2.0b18
2.0b19
2.0b21
+ 199 more Show less
2.0b22
2.0b24
2.0b25
2.0b26
2.0b27
2.0b28
2.0b29
2.0b3
2.0b30
2.0b31
2.0b32
2.0b33
2.0b34
2.0b35
2.0b36
2.0b37
2.0b38
2.0b39
2.0b4
2.0b40
2.0b41
2.0b42
2.0b43
2.0b44
2.0b45
2.0b46
2.0b48
2.0b49
2.0b5
2.0b50
2.0b51
2.0b52
2.0b53
2.0b54
2.0b55
2.0b57
2.0b58
2.0b59
2.0b60
2.0b61
2.0b62
2.0b63
2.0b64
2.0b7
2.0c1
2.0c12
2.0c13
2.0c2
2.0c3
2.0c4
2.0c5
2.0c7
2.0c8
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10rc0
2.10rc1
2.10rc2
2.10rc3
2.10rc4
2.10rc5
2.4
2.4.1
2.4a1
2.4a10
2.4a11
2.4a12
2.4a13
2.4a14
2.4a15
2.4a16
2.4a17
2.4a18
2.4a19
2.4a2
2.4a20
2.4a21
2.4a22
2.4a23
2.4a24
2.4a25
2.4a26
2.4a28
2.4a29
2.4a3
2.4a30
2.4a31
2.4a32
2.4a33
2.4a34
2.4a35
2.4a36
2.4a38
2.4a4
2.4a5
2.4a6
2.4a7
2.4a8
2.4a9
2.4b1
2.4b10
2.4b11
2.4b12
2.4b13
2.4b14
2.4b15
2.4b16
2.4b17
2.4b18
2.4b19
2.4b2
2.4b20
2.4b21
2.4b22
2.4b23
2.4b24
2.4b25
2.4b26
2.4b27
2.4b28
2.4b3
2.4b4
2.4b5
2.4b6
2.4b7
2.4b8
2.4c1
2.4c2
2.4c3
2.4c4
2.5.1
2.5.10
2.5.12
2.5.13
2.5.14
2.5.15
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.9
2.5.9.dev20170116091328
2.5.dev20160825082804
2.6
2.6.1
2.6.2
2.6.3
2.6a1
2.6c1
2.7
2.7.1.dev20171013151516
2.7.2.dev20171013181854
2.7.4.dev20171114161428
2.7.5.dev20180123130714
2.7.5.dev20180125135927
2.8
2.8.1
2.8.1rc0
2.8rc0
2.8rc1
2.8rc10
2.8rc11
2.8rc12
2.8rc13
2.8rc2
2.8rc3
2.8rc4
2.8rc5
2.8rc6
2.8rc7
2.8rc8
2.8rc9
3.0.0
3.1.0
3.1.1
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
Fixed in
4.0.3
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev | ||
3.2.0
minor
3 CVEs
CVE-2023-40017
GHSA-rmxg-6qqf-x8mr
PYSEC-2023-269
Nov 21, 2024
GeoNode Server Side Request forgery
7.5
/ 10
High
Network
Low
None
None
Unchanged
High
None
None
SummaryA server side request forgery vuln was found within geonode when testing on a bug bounty program. Server side request forgery allows a user to request information on the internal service/services. DetailsThe endpoint /proxy/?url= does not properly protect against SSRF. when using the following format you can request internal hosts and display data. /proxy/?url=http://169.254.169.254@whitelistedIPhere. This will state wether the AWS internal IP is alive. If you get a 404, the host is alive. A non alive host will not display a response. To display metadata, use a hashfrag on the url /proxy/?url=http://169.254.169.254@#whitelisteddomain.com or try /proxy/?url=http://169.254.169.254@%23whitelisteddomain.com ImpactPort scan internal hosts, and request information from internal hosts. Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 15 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
4.1.3.post1
4.1.4
4.1.5
Fixed in
4.2.0
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-26043
GHSA-mcmc-c59m-pqq8
PYSEC-2023-15
Aug 30, 2024
GeoServer style upload functionality vulnerable to XML External Entity (XXE) injection
High
Network
Low
Low
None
SummaryGeoNode is vulnerable to an XML External Entity (XXE) injection in the style upload functionality of GeoServer leading to Arbitrary File Read. DetailsGeoNode's GeoServer has the ability to upload new styles for datasets through the
PoC
Sample response: ImpactThis issue may lead to authenticated Affected versions
2.0
2.0.1
2.0.dev20130913181950
2.0.dev20140626191247
2.0b10
2.0b11
2.0b12
2.0b13
2.0b17
2.0b18
2.0b19
2.0b21
+ 199 more Show less
2.0b22
2.0b24
2.0b25
2.0b26
2.0b27
2.0b28
2.0b29
2.0b3
2.0b30
2.0b31
2.0b32
2.0b33
2.0b34
2.0b35
2.0b36
2.0b37
2.0b38
2.0b39
2.0b4
2.0b40
2.0b41
2.0b42
2.0b43
2.0b44
2.0b45
2.0b46
2.0b48
2.0b49
2.0b5
2.0b50
2.0b51
2.0b52
2.0b53
2.0b54
2.0b55
2.0b57
2.0b58
2.0b59
2.0b60
2.0b61
2.0b62
2.0b63
2.0b64
2.0b7
2.0c1
2.0c12
2.0c13
2.0c2
2.0c3
2.0c4
2.0c5
2.0c7
2.0c8
2.10
2.10.1
2.10.2
2.10.3
2.10.4
2.10rc0
2.10rc1
2.10rc2
2.10rc3
2.10rc4
2.10rc5
2.4
2.4.1
2.4a1
2.4a10
2.4a11
2.4a12
2.4a13
2.4a14
2.4a15
2.4a16
2.4a17
2.4a18
2.4a19
2.4a2
2.4a20
2.4a21
2.4a22
2.4a23
2.4a24
2.4a25
2.4a26
2.4a28
2.4a29
2.4a3
2.4a30
2.4a31
2.4a32
2.4a33
2.4a34
2.4a35
2.4a36
2.4a38
2.4a4
2.4a5
2.4a6
2.4a7
2.4a8
2.4a9
2.4b1
2.4b10
2.4b11
2.4b12
2.4b13
2.4b14
2.4b15
2.4b16
2.4b17
2.4b18
2.4b19
2.4b2
2.4b20
2.4b21
2.4b22
2.4b23
2.4b24
2.4b25
2.4b26
2.4b27
2.4b28
2.4b3
2.4b4
2.4b5
2.4b6
2.4b7
2.4b8
2.4c1
2.4c2
2.4c3
2.4c4
2.5.1
2.5.10
2.5.12
2.5.13
2.5.14
2.5.15
2.5.2
2.5.3
2.5.4
2.5.5
2.5.6
2.5.7
2.5.9
2.5.9.dev20170116091328
2.5.dev20160825082804
2.6
2.6.1
2.6.2
2.6.3
2.6a1
2.6c1
2.7
2.7.1.dev20171013151516
2.7.2.dev20171013181854
2.7.4.dev20171114161428
2.7.5.dev20180123130714
2.7.5.dev20180125135927
2.8
2.8.1
2.8.1rc0
2.8rc0
2.8rc1
2.8rc10
2.8rc11
2.8rc12
2.8rc13
2.8rc2
2.8rc3
2.8rc4
2.8rc5
2.8rc6
2.8rc7
2.8rc8
2.8rc9
3.0.0
3.1.0
3.1.1
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
Fixed in
4.0.3
References
Updated Sep 10, 2026 · Source: OSV.dev
CVE-2023-42439
GHSA-pxg5-h34r-7q8p
PYSEC-2023-176
Sep 20, 2023
GeoNode vulnerable to SSRF Bypass to return internal host data
High
Network
Low
None
None
A SSRF vulnerability exists, bypassing existing controls on the software. This can allow a user to request internal services for a full read SSRF, returning any data from the internal network. the application is using a whitelist, but the whitelist can be bypassed with @ and encoded value of @ (%40) GET /proxy/?url=http://development.demo.geonode.org%40geoserver:8080/geoserver/web This will trick the application that the first host is a whitelisted address, but the browser will use @ or %40 as a credential to the host geoserver on port 8080, this will return the data to that host on the response.
Affected versions
3.2.0
3.2.1
3.2.2
3.2.3
3.2.3.post1
3.2.4
3.3.0
3.3.1
3.3.1.post1
3.3.2
3.3.2.post1
3.3.2.post2
+ 12 more Show less
3.3.3
4.0.0
4.0.0.post1
4.0.0rc0
4.0.0rc1
4.0.1
4.0.2
4.0.3
4.1.0
4.1.1
4.1.2
4.1.3
Fixed in
4.1.3.post1
References
Updated Sep 10, 2026 · Source: OSV.dev |
