# CVE-2026-59785: Hidden host credentials inferable via multiselect.get filtering

> Attackers with read access can infer hidden host credentials by observing search results, exposing sensitive IPMI and PSK data.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 5 Oct 2026
- **Updated:** 5 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-59785, GHSA-pr2j-9fvv-cqvq, UBUNTU-CVE-2026-59785

## What is CVE-2026-59785?

CVE-2026-59785 is a medium-severity vulnerability in Zabbix, published on 5 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Host search in Frontend allows filtering by fields that are not displayed, including stored IPMI and PSK credentials. A user with read access can guess a credential and see from the search result whether the guess was right, letting them uncover it.

Weakness: CWE-204 (Observable Response Discrepancy)

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


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

Apply the vendor's patch.

## Is CVE-2026-59785 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-59785 is a medium-severity vulnerability in Zabbix, published on 5 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-59785 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-59785/ (Markdown: https://insights.sbomify.com/CVE-2026-59785/index.md)
```

## Sources

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

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