# 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 outb...

Advisory record · `PYSEC-2026-2159`

- **Identifiers:** `PYSEC-2026-2159` · `CVE-2026-39921`
- **State:** Confirmed
- **Severity:** CVSS 5.3 Medium
- **Critical:** No
- **Weakness (CWE):** [CWE-918](https://cwe.mitre.org/data/definitions/918.html)
- **Tags:** [Server-side request forgery (SSRF)](https://agentprime.io/advisories/tag/ssrf.md)
- **Published:** 10 Apr 2026
- **Updated:** 13 Jul 2026
- **Reviewed by a person:** No

Published by OSV at 10 Apr 2026, 20:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `geonode` (PyPI): affected `>=4.0.0, <4.4.5 || >=5.0.0, <5.0.2`; fixed in `4.4.5`, `5.0.2`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> GeoNode versions 4.0 before 4.4.5 and 5.0 before 5.0.2 are vulnerable to server-side request forgery. An authenticated user with document upload permissions can supply a URL through the doc_url parameter, causing the server to send outbound requests to internal network addresses, including loopback, private, and cloud metadata targets. Upgrade to GeoNode 4.4.5 or 5.0.2.

Written 6 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 5.3 Medium, CVSS 4.0: `CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:L`, from CNA (VulnCheck)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0023, the 13th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 10 Apr 2026, 19:52 UTC: [Confirmed by the CVE List](https://www.cve.org/CVERecord?id=CVE-2026-39921)
- 31 Oct 2026, 15:04 UTC: First seen by agentprime
- 31 Oct 2026, 15:04 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/PYSEC-2026-2159)

## Sources

- [OSV: PYSEC-2026-2159](https://osv.dev/vulnerability/PYSEC-2026-2159)
- <https://github.com/GeoNode/geonode/releases/tag/4.4.5>
- <https://github.com/GeoNode/geonode/releases/tag/5.0.2>
- <https://www.vulncheck.com/advisories/geonode-ssrf-via-document-upload>
- <https://github.com/GeoNode/geonode/commit/4a852cfc1da732b10779b5bf5f087c8f02985571>
- <https://github.com/GeoNode/geonode/commit/9856cb5ab27e33c0adba9274f4cccf6d1f534bd1>
- <https://github.com/GeoNode/geonode/pull/14058>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/PYSEC-2026-2159>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/PYSEC-2026-2159/>. Everything for agents: <https://agentprime.io/llms.txt>.