CVE-2021-41526
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 vulnerability has been reported in the windows installer (MSI) built with InstallScript custom action. This vulnerability may allow privilege escalation when invoked ‘repair’ of the MSI which has an InstallScript custom action.
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 confidenceThis vulnerability exists in Windows MSI installers that use InstallScript custom actions. When the MSI repair function is invoked, the InstallScript custom action runs with elevated privileges, potentially allowing an attacker to execute arbitrary code or gain privileged access through the repair operation.
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< 2021= 2021CVSS 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.
-
Identify InstallShield version in useCheck the version of Flexera Revenera InstallShield used to build or maintain your MSI installers. This can be found in the InstallShield project file (.ism) or by examining the MSI package metadata in tools such as Orca, MSI Explorer, or similar MSI analysis utilities.Affected if The version is 2021 or any version prior to 2021 (versions < 2021 or = 2021).
-
Locate MSI packages with InstallScript custom actionsExamine your MSI databases for custom actions that invoke InstallScript. Use MSI analysis tools to query the CustomAction table for actions where the Type column indicates InstallScript (typically action types 51-55 or custom action sources referencing InstallScript DLLs).Affected if The MSI contains any InstallScript custom actions defined in the CustomAction table.
-
Verify repair operation is availableDetermine whether the MSI package is configured to support repair operations. Check the MSI Property table for the 'RepairPath' property or verify that the package includes the 'Reinstall' feature mode. Inspect whether the MSI is distributed in a form that allows end-users or attackers to trigger repair (via Add/Remove Programs repair button, msiexec /f command, or similar).Affected if The MSI supports repair operations and is accessible to users or processes that could trigger the repair function.
-
Confirm elevated execution context during repairReview the InstallScript custom action definitions in the InstallExecuteSequence table. Check the scheduling and condition columns to verify whether these custom actions are set to execute with elevated privileges during repair mode. Look for msidbCustomActionTypeNoImpersonate flag or elevated execution context.Affected if InstallScript custom actions are scheduled to run with elevated (system) privileges during repair operations.
Your environment is affected if you use InstallShield version 2021 or earlier and have MSI packages containing InstallScript custom actions that execute with elevated privileges when the repair function is invoked.
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 · scoped2021
Review and secure InstallScript custom actions in MSI packages to ensure they do not allow privilege escalation during repair operations; consider removing or properly sandboxing vulnerable custom actions.
InstallShield 2022 or later
- 1. Identify all systems running Revenera InstallShield version 2021 or earlier that build MSI installers with InstallScript custom actions
- 2. Download InstallShield 2022 or later from the official Revenera/Flexera download portal
- 3. Upgrade InstallShield on all build systems to the latest stable version (2022 or subsequent release)
- 4. Rebuild all MSI installers that use InstallScript custom actions using the upgraded InstallShield version
- 5. Redistribute the rebuilt MSI installers to replace vulnerable versions
- 6. Verify the repair functionality works correctly in the new MSI packages
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-41526 — 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-2021-41526 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