# CVE-2026-59782: JavaScript preprocessing memory disclosure

> A limited administrator can read raw heap data from the Duktape engine, potentially leaking sensitive information from other preprocessors.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-59782, GHSA-wg6x-hw9j-7vg6, UBUNTU-CVE-2026-59782

## What is CVE-2026-59782?

CVE-2026-59782 is a medium-severity vulnerability in Zabbix, published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The JavaScript preprocessing (Duktape) engine on Zabbix server has a vulnerability where a limited administrator is able to read raw heap data potentially resulting in leaked data from other running preprocessors not available to said administrator.

Weakness: CWE-125 (Out-of-bounds Read)

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


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

Apply the vendor's patch.

## Is CVE-2026-59782 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59782 is a medium-severity vulnerability in Zabbix, published on 5 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-59782 in the wild and no public exploit code.

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

## Sources

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

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