{"answers":{"affected":"3 open source packages ship an affected version, including pygeoapi.","exploited":"There is no known exploitation of CVE-2026-42351 in the wild and no public exploit code.","fix":"Upgrade pygeoapi to 0.23.3 or later.","what":"CVE-2026-42351 is a high-severity path traversal vulnerability in geopython pygeoapi, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-42351 and fix it if it is affected.\n\nWhat it is: CVE-2026-42351 is a high-severity path traversal vulnerability in geopython pygeoapi, published on 8 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-42351 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- pygeoapi (PyPI): affected from 0.23.0; fixed in 0.23.3\n- pygeoapi (PyPI): affected from 0.23.0; fixed in 0.23.3\n- pygeoapi (PyPI): affected from 0.23.0; fixed in 0.23.3\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-42351/ (Markdown: https://insights.sbomify.com/CVE-2026-42351/index.md)","id":"CVE-2026-42351","markdown":"https://insights.sbomify.com/CVE-2026-42351/index.md","name":"CVE-2026-42351","record":{"aliases":["GHSA-f6pr-83pg-ghh6","PYSEC-2026-2985"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":true,"product_category":"OGC API server","requires_auth":"none","summary":"Attackers can expose directories without authentication in pygeoapi STAC collections if deployed without a normalizing proxy.","user_interaction":"not_required","vuln_class":"path_traversal"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-22","name":"Improper Limitation of a Pathname to a Restricted Directory"}],"description":"pygeoapi is a Python server implementation of the OGC API suite of standards. From version 0.23.0 to before version 0.23.3, a raw string path concatenation vulnerability in pygeoapi's STAC FileSystemProvider plugin can allow for requests to STAC collection based collections to expose directories without authentication. The issue manifests when pygeoapi is deployed without a proxy or web front end that would normalize URLs with .. values, along with a resource of type stac-collection defined in configuration. This issue has been patched in version 0.23.3.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"pygeoapi: Path Traversal in STAC FileSystemProvider","id":"CVE-2026-42351","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"path_traversal","year":"2026"},"n_packages":3,"n_references":3,"next":{"headline":"pygeoapi 0.23.x: Unauthenticated SSRF via OGC API - Processes Subscriber","id":"CVE-2026-42352"},"packages":[{"ecosystem":"PyPI","fixed":["0.23.3"],"introduced":["0.23.0"],"last_affected":[],"package":"pygeoapi","purl":null,"source":"GHSA-f6pr-83pg-ghh6"},{"ecosystem":"PyPI","fixed":["0.23.3"],"introduced":["0.23.0"],"last_affected":[],"package":"pygeoapi","purl":"pkg:pypi/pygeoapi","source":"GHSA-f6pr-83pg-ghh6"},{"ecosystem":"PyPI","fixed":["0.23.3"],"introduced":["0.23.0"],"last_affected":[],"package":"pygeoapi","purl":"pkg:pypi/pygeoapi","source":"PYSEC-2026-2985"}],"prev":{"headline":"Kargo: Open Redirect in UI OIDC Login Flow via redirectTo Query Parameter","id":"CVE-2026-42350"},"products":["pygeoapi"],"published":"2026-05-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-12","vendors":["geopython"]},"summary":"Attackers can expose directories without authentication in pygeoapi STAC collections if deployed without a normalizing proxy.","url":"https://insights.sbomify.com/CVE-2026-42351/"}