CVE-2025-49641: A regular Zabbix user with no permission to the Monitoring -> Problems view is still able to call the problem.

Routine

MEDIUM 4.3UPGRADE

CVE-2025-49641 is a medium-severity flaw (CVSS 4.3) affecting zabbix. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A regular Zabbix user with no permission to the Monitoring -> Problems view is still able to call the problem.view.refresh action and therefore still retrieve a list of active problems.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 77%)
CISA exploited list	No
Weakness	CWE-863
Published	2025-10-03
Last modified	2026-10-19

Publisher (CNA): Zabbix · Vendor: zabbix

Last updated 2026-10-19 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-10-03 12:15 UTCPublished CVE record published
2026-10-19 17:10 UTCUpdated Record last modified

zabbix zabbix UPGRADE

Affected: >= 6.0.0 and < 6.0.41 · >= 7.0.0 and < 7.0.18 · >= 7.2.0 and < 7.2.12 · >= 7.4.0 and < 7.4.2

Fixed in: 6.0.41, 7.0.18, 7.2.12, 7.4.2

Safe to downgrade to: a release before 6.0.0

1. Check installed version

apt-cache policy zabbix || rpm -q zabbix || zabbix --version

2. UPGRADE to 6.0.41 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade zabbix

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade zabbix

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 6.0.0 (Debian / Ubuntu)

apt-cache madison zabbix sudo apt install zabbix=<VERSION_BEFORE_6.0.0> sudo apt-mark hold zabbix

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list zabbix sudo dnf downgrade zabbix-<VERSION_BEFORE_6.0.0> sudo dnf versionlock add zabbix

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-49641?

zabbix: upgrade to 6.0.41, 7.0.18, 7.2.12, 7.4.2. Exact commands for each OS are on this page.

Is CVE-2025-49641 being exploited?

CVE-2025-49641 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-49641 affect?

CVE-2025-49641 affects zabbix. Severity is medium (CVSS 4.3). A regular Zabbix user with no permission to the Monitoring -> Problems view is still able to call the problem.view.refresh action and therefore still retrieve a list of active problems.

How urgent is CVE-2025-49641?

Priority 21/100. No elevated risk signals yet.

Software pages

Zabbix vulnerabilities

Related CVEs

CVE-2025-27240 HIGH 7.2 UPGRADE A Zabbix adminitrator can inject arbitrary SQL during the autoremoval of hosts by inserting malicious SQL in t
CVE-2025-27236 MEDIUM 6.5 UPGRADE A regular Zabbix user can search other users in their user group via Zabbix API by select fields the user does
CVE-2025-27231 MEDIUM 4.9 UPGRADE The LDAP 'Bind password' value cannot be read after saving, but a Super Admin account can leak it by changing
CVE-2025-27238 LOW 3.5 UPGRADE Due to a bug in Zabbix API, the hostprototype.get method lists all host prototypes to users that do not have a
CVE-2026-23919 MEDIUM 6.0 UPGRADE For performance reasons Zabbix Server/Proxy reuses JavaScript (Duktape) contexts (used in script items, JavaSc

References

← Back to latest CVEs