# CVE-2026-125107: Muhammara: NULL pointer dereference in LZWDecode filter when DecodeParms omits EarlyChange key


- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 9 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-fhp4-pr5j-46m5

## What is CVE-2026-125107?

CVE-2026-125107 is a high-severity vulnerability in julianhille MuhammaraJS, published on 9 Nov 2026. 

### Official description

Muhammara is a node module with c/cpp bindings to modify PDF with JavaScript for node or electron. Prior to 6.0.5, Muhammara PDFParser::CreateFilterForStream() in src/deps/PDFWriter/PDFParser.cpp dereferences a null PDFInteger pointer when a PDF stream uses the LZWDecode filter with a DecodeParms dictionary that omits the EarlyChange key. An application that processes an untrusted PDF and reads the affected stream can crash, causing a denial of service. This issue is fixed in version 6.0.5.

Weakness: CWE-476 (NULL Pointer Dereference)

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

1 open source package ship an affected version, including muhammara.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `muhammara` | npm | All versions | 6.0.5 |

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

Upgrade muhammara to 6.0.5 or later.

## Is CVE-2026-125107 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-125107 is a high-severity vulnerability in julianhille MuhammaraJS, published on 9 Nov 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-125107 exists.

Affected packages and fixed versions:
- muhammara (npm): affected all versions; fixed in 6.0.5

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

## Sources

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

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