CVE-2026-37453
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 · uneditedInsecure Permissions vulnerability in MSI NBFoundation Service v.2.0.2506.1201 allows a remote attacker to obtain sensitive information via the MSI_SERVICE_2 pipe
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 confidenceThe MSI NBFoundation Service version 2.0.2506.1201 has insecure permissions configured on the MSI_SERVICE_2 named pipe, allowing unauthenticated remote attackers to access the pipe and obtain sensitive information. This is a classic privilege escalation/information disclosure issue where the pipe's access control list (ACL) is too permissive.
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< 2.0.70.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Verify Msi Center installationCheck if Msi Center is installed by looking in Program Files (C:\Program Files\MSI\Msi Center) or checking the registry key HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\MsiCenterAffected if Msi Center is not found on the system, the vulnerability does not apply
-
Identify installed Msi Center versionRight-click the Msi Center executable in Program Files\MSI\Msi Center, select Properties, and view the File Version under the Details tab. Alternatively, check the registry value at HKLM\SOFTWARE\MSI\MsiCenter\VersionAffected if The installed version is lower than 2.0.70.0 (for example, 2.0.2506.1201 as noted in the CVE)
-
Confirm NBFoundation Service presenceOpen Services (services.msc) and look for 'MSI NBFoundation Service' or run 'sc query MSI_NBFoundation' in Command PromptAffected if The MSI NBFoundation Service is installed and running on the system
-
Check MSI_SERVICE_2 named pipe permissionsUse PowerShell with Sysinternals PipeList.exe (pipelist -n MSI_SERVICE_2) or run 'get-childitem \\.\pipe\MSI_SERVICE_2' in PowerShell to enumerate the pipe, then inspect ACLs using Sysinternals AccessChk or icacls if the pipe is accessibleAffected if The MSI_SERVICE_2 named pipe exists and is accessible to unprivileged users or allows anonymous access
If Msi Center is installed with a version lower than 2.0.70.0 and the MSI NBFoundation Service is running with an accessible MSI_SERVICE_2 pipe, the environment is affected by this vulnerability.
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 · scoped2.0.70.0
Remediate by restricting permissions on the MSI_SERVICE_2 named pipe to authorized users/processes only, following the principle of least privilege. Verify the service's ACL configuration and ensure only required principals have access.
MSI NBFoundation Service version 2.0.70.0 or later
- Identify the current version of MSI NBFoundation Service installed on the system
- Download MSI NBFoundation Service version 2.0.70.0 or later from the official MSI support site (csr.msi.com) or authorized distribution channels
- Stop the MSI NBFoundation Service if it is currently running
- Apply the update/upgrade to the MSI NBFoundation Service to version 2.0.70.0 or newer
- Restart the MSI NBFoundation Service
- Verify the service is running and the version has been updated to 2.0.70.0 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-37453 — 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-37453 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