# GeoNode vulnerable to SSRF Bypass to return internal host data

Advisory record · `GHSA-pxg5-h34r-7q8p`

- **Identifiers:** `GHSA-pxg5-h34r-7q8p` · `CVE-2023-42439` · `PYSEC-2023-176`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **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:** 20 Sept 2023
- **Updated:** 10 Sept 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 20 Sept 2023, 23:04 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `geonode` (PyPI): affected `>=3.2.0, <4.1.3.post1`; fixed in `4.1.3.post1`

## Machine-written summary

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

> GeoNode versions 3.2.0 up to but not including 4.1.3.post1 are vulnerable to server-side request forgery. An attacker who can reach the proxy endpoint can bypass the host allowlist by embedding an @ character (or its encoded form) in the URL, causing the server to fetch internal services and return their contents. Upgrade geonode to 4.1.3.post1 or later.

Written 5 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

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0096, the 62nd percentile, on 15 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:36 UTC: First seen by agentprime
- 31 Oct 2026, 14:36 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-pxg5-h34r-7q8p)

## Sources

- [GitHub Advisory Database: GHSA-pxg5-h34r-7q8p](https://github.com/advisories/GHSA-pxg5-h34r-7q8p)
- [OSV: GHSA-pxg5-h34r-7q8p](https://osv.dev/vulnerability/GHSA-pxg5-h34r-7q8p)
- <https://github.com/GeoNode/geonode/security/advisories/GHSA-pxg5-h34r-7q8p>
- <https://nvd.nist.gov/vuln/detail/CVE-2023-42439>
- <https://github.com/GeoNode/geonode/commit/79ac6e70419c2e0261548bed91c159b54ff35b8d>
- <https://github.com/GeoNode/geonode>
- <https://github.com/GeoNode/geonode/releases/tag/4.1.3>
- <https://github.com/pypa/advisory-database/tree/main/vulns/geonode/PYSEC-2023-176.yaml>

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/GHSA-pxg5-h34r-7q8p>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-pxg5-h34r-7q8p/>. Everything for agents: <https://agentprime.io/llms.txt>.
