# CVE-2026-131872: SOIL2 before 1.4.2 NULL Pointer Dereference in DDS, PVR and PKM Loaders


- **Severity:** Medium 6.8 (`CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 18 Nov 2026
- **Updated:** 18 Nov 2026
- **Also known as:** GHSA-4gw9-pqc2-jhpg, UBUNTU-CVE-2026-131872

## What is CVE-2026-131872?

CVE-2026-131872 is a medium-severity vulnerability in Martin Lucas Golini SOIL2, published on 18 Nov 2026. 

### Official description

SOIL2 before 1.4.2 contains a NULL pointer dereference vulnerability in its DDS, PVR and PKM image loaders that write results through unchecked caller-supplied output pointers. Attackers can supply a valid DDS, PVR or PKM file to applications passing NULL output pointers to SOIL_load_image or stbi_info, causing a crash.

Weakness: CWE-476 (NULL Pointer Dereference)

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

1 open source package ship an affected version, including spartanj/soil2.


| Package | Ecosystem | PURL | Affected | Fixed in |
| --- | --- | --- | --- | --- |
| `spartanj/soil2` | GitHub | `pkg:github/spartanj/soil2` | All versions | 1.4.2 |

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

Upgrade spartanj/soil2 to 1.4.2 or later.

## Is CVE-2026-131872 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-131872 is a medium-severity vulnerability in Martin Lucas Golini SOIL2, published on 18 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-131872 in the wild and no public exploit code.

Affected packages and fixed versions:
- spartanj/soil2 (GitHub): affected all versions; fixed in 1.4.2

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-131872/ (Markdown: https://insights.sbomify.com/CVE-2026-131872/index.md)
```

## Sources

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

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