CVE-2025-27237
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn Zabbix Agent and Agent 2 on Windows, the OpenSSL configuration file is loaded from a path writable by low-privileged users, allowing malicious modification and potential local privilege escalation by injecting a DLL.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceZabbix Agent and Agent 2 on Windows load the OpenSSL configuration file from a directory path that is writable by low-privileged users, allowing an attacker with basic user access to modify the config and inject a malicious DLL for local privilege escalation.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Zabbix Agent installation on WindowsCheck for Zabbix Agent service: open Services.msc and look for 'Zabbix Agent' or 'Zabbix Agent 2', or check for the executable at common paths like C:\Program Files\Zabbix Agent\zabbix_agentd.exeAffected if Zabbix Agent or Agent 2 service exists on the system
-
Check Zabbix Agent versionRun 'zabbix_agentd --version' or right-click the executable and view Properties > Details to see the version numberAffected if Version matches the affected release where the vulnerable OpenSSL config path behavior exists (verify against Zabbix release notes for CVE-2025-27237)
-
Locate the OpenSSL configuration file path used by ZabbixCheck the Zabbix Agent configuration file (zabbix_agentd.conf) for 'TLS' or 'SSL' related settings, and check the system environment variable OPENSSL_CONF by running 'echo %OPENSSL_CONF%' in Command PromptAffected if OPENSSL_CONF points to a directory that is writable by standard users
-
Verify directory permissions on the OpenSSL config pathRight-click the directory containing openssl.cnf (from the identified path), go to Properties > Security, and check what users have Write or Modify permissions. Alternatively, run 'icacls [directory_path]' in Command PromptAffected if Users with low privileges (e.g., standard users, authenticated users) have Write or Modify access to the directory containing the OpenSSL configuration file
The environment is affected if Zabbix Agent or Agent 2 is installed on Windows and the OpenSSL configuration file is loaded from a directory where standard users have write permissions, allowing DLL injection for privilege escalation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRelocate the OpenSSL configuration file to a secure, non-writable path (e.g., system directory with restricted permissions) or ensure the current path has appropriate access controls to prevent modification by non-privileged users.
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27237 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-27237 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data