CVE-2026-45777
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 · uneditedOpenXDMoD is an open framework for collecting and analyzing HPC metrics. Starting in version 9.5.0 and prior to version 11.0.3, an attacker can remotely execute arbitrary system commands on the web server hosting Open XDMoD with the privileges of the web server process. This could allow an attacker to read or modify application data, alter system configuration, or disrupt service availability. All deployments of Open XDMoD versions 9.5.0 through 11.0.2 (inclusive) are impacted. This issue was reported privately on 2026-04-06, and at this time there is no evidence that this vulnerability has been exploited in the wild. The vulnerability was patched in Open XDMoD 11.0.3 on 2026-05-12. As a workaround, apply the patch manually.
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 · high confidenceOpenXDMoD versions 9.5.0 through 11.0.2 contain a remote code execution vulnerability that allows unauthenticated attackers to execute arbitrary system commands on the web server with the privileges of the web server process. This critical flaw enables full compromise of the application and underlying host.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 9.5.0, < 11.0.3CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 if OpenXDMoD is installed on this systemLook for OpenXDMoD web application files in common web server document roots (e.g., /var/www/, /opt/, or check for openxdmod directories). On Linux, check for installed packages via package manager (dpkg -l | grep -i openxdmod, rpm -qa | grep -i openxdmod).Affected if OpenXDMoD is found installed on the system
-
Determine the installed OpenXDMoD versionCheck the version file or composer.json in the OpenXDMoD installation directory. Common locations include VERSION.txt, composer.json, or the About page in the web interface.Affected if Installed version is 9.5.0 through 11.0.2 (>= 9.5.0 and < 11.0.3)
-
Verify the web server is serving OpenXDMoDCheck if the web server (Apache, Nginx, etc.) is running and configured to serve the OpenXDMoD application. Inspect web server configuration files for OpenXDMoD virtual hosts or aliases.Affected if Web server is running and exposing OpenXDMoD to network requests
-
Confirm the OpenXDMoD web interface is accessibleAttempt to access the OpenXDMoD login page or main page via HTTP/HTTPS from the server itself (curl http://localhost/path/to/openxdmod or check for listening ports 80/443).Affected if The OpenXDMoD web interface responds to requests, indicating the vulnerable attack surface is exposed
You are affected if OpenXDMoD versions 9.5.0 through 11.0.2 are installed and the web interface is accessible, since unauthenticated remote attackers can execute commands through the vulnerable web application.
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.
dbcve · scoped11.0.3
Upgrade to Open XDMoD version 11.0.3 or apply the manually provided patch to remediate this RCE vulnerability. Given the CVSS 9.8 severity and network-exploitable nature, immediate prioritization is essential.
11.0.3
- Upgrade Open XDMoD to version 11.0.3 or later to obtain the patched code
- Alternatively, apply the vendor-provided patch manually from the GitHub security advisory at https://github.com/ubccr/xdmod/security/advisories/GHSA-29qm-7w4v-43fw
- After applying the fix, verify the web server is functioning correctly and test that the command injection vulnerability is no longer present
- Review the 11.0.3 release notes for any configuration or dependency changes that may require attention
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-45777 — 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-2026-45777 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