CVE-2026-37452
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 MSIAPService.exe component
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 contains an insecure permissions vulnerability in the MSIAPService.exe component. This permissions misconfiguration allows a remote attacker to access sensitive information due to overly permissive access controls on the service executable or its associated configuration/data files.
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
- 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.
-
Confirm MSI NBFoundation Service is installedOpen Services console (services.msc) and look for 'NBFoundation Service' or check Program Files for MSI folder containing MSIAPService.exeAffected if The service is present in the environment
-
Locate MSIAPService.exe and retrieve its versionFind MSIAPService.exe (typically in C:\Program Files\MSI\NBFoundation or similar), right-click > Properties > Details to see File VersionAffected if File version matches 2.0.2506.1201 or falls within the 2.0.x.x range
-
Verify file permissions on MSIAPService.exeRight-click MSIAPService.exe > Properties > Security tab, click Advanced. Check the 'Access' entries for Users, Everyone, or authenticated users groupsAffected if Users, Everyone, or authenticated users have Read & Execute, Read, or Write permissions beyond what is required for service operation
-
Check permissions on related configuration or data filesInspect all files in the MSIAPService.exe directory (config files, XML, dat files) using the same Security > Advanced methodAffected if Configuration or data files grant excessive read access to non-privileged accounts
-
Identify if permissions allow unauthorized accessCompare observed permissions against least-privilege: only SYSTEM, Administrators, and the service account should have accessAffected if Any account other than SYSTEM, Administrators, and the service account has access to sensitive service files
The environment is affected if the MSI NBFoundation Service (MSIAPService.exe version 2.0.x.x) is installed AND file permissions grant excessive read or write access to standard users or Everyone.
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 dataReview and restrict file system permissions on MSIAPService.exe and related service components to follow least-privilege principles, ensuring only authorized users/processes have read access to sensitive files.
- Consultation2.0 h
- Implementation2.0 h
- Testing1.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-37452 — 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-37452 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