CVE-2026-2123
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 · uneditedA security audit identified a privilege escalation vulnerability in Operations Agent(<=OA 12.29) on Windows. Under specific conditions Operations Agent may run executables from specific writeable locations.Thanks to Manuel Rickli & Philippe Leiser of Oneconsult AG for reporting this vulnerability
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 confidenceA privilege escalation vulnerability exists in Operations Agent (versions 12.29 and below) on Windows where the software may execute binaries from specific writable locations under certain conditions, potentially allowing an attacker to escalate privileges.
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>= 12.22, <= 12.29CVSS 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
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/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.
-
Confirm Operations Agent is installedCheck the Windows system for the presence of Micro Focus Operations Agent. Look for the installation directory (typically under C:\Program Files\Micro Focus\ or check Windows Services for 'Operations Agent' service).Affected if The software is present on the system.
-
Identify installed versionLocate the Operations Agent version information. This is typically found in the product's About dialog, in the installation directory metadata, or via Windows Registry under HKLM\SOFTWARE\Micro Focus\Operations Agent. Compare the version against the affected range: 12.22 through 12.29.Affected if The installed version is 12.22, 12.23, 12.24, 12.25, 12.26, 12.27, 12.28, or 12.29.
-
Identify vulnerable executable locationsConsult the specific security advisory for this CVE to determine the exact writeable directory paths used by the agent for executable placement. These are locations where the privileged agent service searches for or executes binaries.Affected if The identified vulnerable locations exist on the system and are writable by lower-privilege users.
-
Verify write permissions on vulnerable locationsUse icacls or AccessChk to examine permissions on the identified vulnerable directories. Check if standard users or non-admin accounts have write (W) or create-file (CI,OI) permissions to these locations.Affected if Unprivileged users can write files to the directories from which the agent executes binaries.
The system is affected if Micro Focus Operations Agent version 12.22 through 12.29 is installed AND unprivileged users have write access to the specific executable locations used by the agent service.
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 dataUpdate Operations Agent to a version beyond 12.29. Additionally, restrict write permissions on directories from which Operations Agent loads and executes binaries to prevent unauthorized executable placement.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2123 — 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-2123 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