Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
pygeoapi versions 0.23.0 up to but not including 0.23.3 are vulnerable to server-side request forgery through the subscriber object in OGC API - Processes execution requests, which can make HTTP requests to internal services. The source indicates the attack needs no authentication. Upgrade to pygeoapi 0.23.3, which disables requests to internal resources by default unless allowed through the new allow_internal_requests setting. Until then, disabling process-based resources in the pygeoapi configuration is a workaround.
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
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 8.6 | High | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0045, the 39th percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 15:03 UTC First seen by agentprime
- 31 Oct 2026, 15:03 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-jgvc-94c8-3chc
- OSV: GHSA-jgvc-94c8-3chc
- github.com/geopython/pygeoapi/security/advisories/GHSA-jgvc-94c8-3chc
- nvd.nist.gov/vuln/detail/CVE-2026-42352
- github.com/geopython/pygeoapi/commit/3a63f5b0cc6275e3ae0edb47726b13a43cdd90ef
- github.com/geopython/pygeoapi
- github.com/geopython/pygeoapi/releases/tag/0.23.3