# CVE-2026-133217: OSGeo shapelib dbfopen.c DBFCloneEmpty null pointer dereference


- **Severity:** Medium 4.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 19 Nov 2026
- **Updated:** 20 Nov 2026
- **Also known as:** GHSA-9c8v-hmfw-mr6f

## What is CVE-2026-133217?

CVE-2026-133217 is a medium-severity vulnerability in OSGeo shapelib, published on 19 Nov 2026. 

### Official description

A weakness has been identified in OSGeo shapelib up to 1.6.3. This vulnerability affects the function DBFCloneEmpty of the file dbfopen.c. This manipulation causes null pointer dereference. It is possible to launch the attack on the local host. Patch name: f79050a900d2a05529501b2b714b8f89067db071. It is recommended to apply a patch to fix this issue.

Weakness: CWE-476 (NULL Pointer Dereference), CWE-404 (Improper Resource Shutdown or Release)

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

It affects 1 product.


Products: Shapelib.

CPE match criteria (CPE 2.3):

- `cpe:2.3:a:osgeo:shapelib:*:*:*:*:*:*:*:*` from 1.6.0 up to 1.6.0
- `cpe:2.3:a:osgeo:shapelib:*:*:*:*:*:*:*:*` from 1.6.1 up to 1.6.1
- `cpe:2.3:a:osgeo:shapelib:*:*:*:*:*:*:*:*` from 1.6.2 up to 1.6.2
- `cpe:2.3:a:osgeo:shapelib:*:*:*:*:*:*:*:*` from 1.6.3 up to 1.6.3

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

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

## Is CVE-2026-133217 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-133217 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-133217 is a medium-severity vulnerability in OSGeo shapelib, published on 19 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-133217 exists.

Affected product: OSGeo shapelib. 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-133217/ (Markdown: https://insights.sbomify.com/CVE-2026-133217/index.md)
```

## Sources

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

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