CVE-2026-20967
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 · uneditedImproper input validation in System Center Operations Manager allows an authorized attacker to elevate privileges over a network.
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 confidenceImproper input validation in Microsoft System Center Operations Manager enables an authenticated attacker to escalate privileges by sending specially crafted network requests. The vulnerability allows lateral movement from low-privilege to higher-privilege accounts within the SCOM environment.
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= 2019= 2022= 2025CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/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.
-
Identify SCOM installation versionOpen Operations Manager console, go to Administration > Management Servers, or run Get-SCOMManagementServer PowerShell cmdlet on management server. Check the build version in Help > About Microsoft System Center Operations Manager.Affected if Version matches 2019, 2022, or 2025 (any build)
-
Confirm web console is enabledCheck if SCOM Web Console service (Microsoft.SystemCenter.OpsMgrWebApp) is running. In IIS Manager, verify OpsMgrWebApp application pool exists under Default Web Site. Alternatively, run Get-SCWebAddress PowerShell cmdlet.Affected if Web console is installed and accessible on network (HTTP/HTTPS)
-
Check management server exposureVerify which network interfaces the OpsMgr SDK Service and web services bind to. Review firewall rules allowing incoming connections to ports 5723, 5724, and web console ports (default 80/443).Affected if Management server has open inbound ports to untrusted networks
-
Review user role assignmentsIn Operations Manager console, navigate to Administration > User Roles. Examine all User Role profiles (Administrator, Advanced Operator, Operator, Read-Only Operator, etc.) and list assigned users/groups.Affected if Multiple users or groups assigned to roles beyond Read-Only Operator, especially if untrusted accounts exist in higher-privilege roles
-
Audit recent authentication activityReview Operations Manager event logs on management servers for Event ID 4624/4625 (account logon) and look for privilege escalation patterns from low-privilege to privileged account sessions.Affected if Evidence of lateral movement attempts or unexpected privilege escalation events
Environment is affected if running SCOM 2019, 2022, or 2025 with the web console or management interfaces network-accessible and any non-administrator user accounts exist in the environment.
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 dataApply Microsoft security patches for System Center Operations Manager when released. Review and restrict user role assignments to minimum necessary permissions until patch deployment.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.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 $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-20967 — 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-20967 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