# CVE-2023-32726: Possible buffer overread from reading DNS responses

> A buffer overread in Zabbix's DNS response handling allows attackers to cause denial of service or disclose sensitive memory contents.

- **Severity:** Low 3.9 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 18 Dec 2023
- **Updated:** 3 Nov 2025
- **Also known as:** DEBIAN-CVE-2023-32726, GHSA-fqr7-2x83-wf2r, UBUNTU-CVE-2023-32726

## What is CVE-2023-32726?

CVE-2023-32726 is a low-severity memory corruption vulnerability in Zabbix, published on 18 Dec 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The vulnerability is caused by improper check for check if RDLENGTH does not overflow the buffer in response from DNS server.

Weakness: CWE-754 (Improper Check for Unusual or Exceptional Conditions)

## Which versions are affected by CVE-2023-32726?

It affects 1 product.


Products: Zabbix Zabbix-Agent.

## How do I fix CVE-2023-32726?

Apply the vendor's patch.

## Is CVE-2023-32726 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-32726 and fix it if it is affected.

What it is: CVE-2023-32726 is a low-severity memory corruption vulnerability in Zabbix, published on 18 Dec 2023. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-32726 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-2023-32726/ (Markdown: https://insights.sbomify.com/CVE-2023-32726/index.md)
```

## Sources

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

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