SSRF (Server-Side Request Forgery) in pygeoapi (CVE-2026-42352)
Summary
SSRF in pygeoapi (CVE-2026-42352). Confidential information can be exposed externally. Exploitable via subscriber. Mitigation: upgrade to 0.23.3 or later.
Original description
The description as published by the source.
Impact
OGC API - Process execution requests can use the subscriber object to requests to internal HTTP services.
Patches
The issue has been patched in master branch and made available as part of the 0.23.3 release. The patch disables any HTTP requests made to internal resources by default (unless explicitly defined in configuration by a new allow_internal_requests directive.
The commit/fix can be found in 3a63f5b0cc6275e3ae0edb47726b13a43cdd90ef.
Workarounds
Users can update existing applications by disabling process based resources in their pygeoapi config, until 0.23.3 can be installed and deployed.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-42352 has been found in pygeoapi.
Attackers can target a specific entry point like subscriber over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.6/10.
What to do: upgrade pygeoapi to 0.23.3 or later.
If unsure, ask your IT team or search "pygeoapi CVE-2026-42352" on the vendor's site.
CVE-2026-42352 (pygeoapi) — CWE-918 / CVSS v3 8.6
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: subscriber / allow_internal_requests
Patched: 0.23.3 — apply immediately
Workaround: Users can update existing applications by disabling process based resources in their pygeoapi config, until 0.23.3 can be installed and deployed.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SSRF (CWE-918) exists in pygeoapi. Attackers reach the vulnerable code path via subscriber without authentication.
Check the vendor advisory for the affected versions of pygeoapi. Attack surface: subscriber / allow_internal_requests.
Severity: High (CVSS 8.6/10). Confidential information can be exposed externally.
Update to 0.23.3.
Workaround: Users can update existing applications by disabling process based resources in their pygeoapi config, until 0.23.3 can be installed and deployed.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'pygeoapi' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pygeoapi' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pygeoapiを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply temporary workaround mitigate
Users can update existing applications by disabling process based resources in their pygeoapi config, until 0.23.3 can be installed and deployed.パッチが適用されるまでの応急処置として、Users can update existing applications by disabling process based resources in their pygeoapi config, until 0.23.3 can be installed and deployed. を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade pygeoapi to 0.23.3ステージング環境で 0.23.3 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com