# CVE-2026-86806: opengeos GeoLibre _is_within_roots server-side request forgery

> Remote attackers can exploit a server-side request forgery vulnerability in the GeoLibre library to access internal resources or bypass security controls.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2026
- **Updated:** 8 Sep 2026
- **Also known as:** GHSA-mgm6-2qqc-vwg8

## What is CVE-2026-86806?

CVE-2026-86806 is a medium-severity server-side request forgery vulnerability in opengeos GeoLibre, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A weakness has been identified in opengeos GeoLibre up to 2.3.0. Impacted is the function _is_within_roots. This manipulation causes server-side request forgery. The attack can be initiated remotely. Upgrading to version 2.4.0 is recommended to address this issue. Patch name: b745f62e29fa37364686525a21eee5e5c0f8a369. It is recommended to upgrade the affected component.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-86806?


## How do I fix CVE-2026-86806?

No fix has been published for CVE-2026-86806 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-86806 being exploited?

There is no known exploitation of CVE-2026-86806 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-86806 and fix it if it is affected.

What it is: CVE-2026-86806 is a medium-severity server-side request forgery vulnerability in opengeos GeoLibre, published on 8 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-86806 in the wild and no public exploit code.

Affected product: opengeos GeoLibre. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-86806/ (Markdown: https://insights.sbomify.com/CVE-2026-86806/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-86806
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-86806
- OSV: https://osv.dev/vulnerability/CVE-2026-86806

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-86806/
Summaries are generated and may contain mistakes; the official description above is the record.