Add CVE-2026-50343 (InstallService) check - #88
Open
KenjiEndo15 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Hi!
I wrote this PR for testing CVE-2026-50343.
In Brief
InstallService is a Windows service that manages Microsoft Store app installations and updates. The service can load plugins and execute them. To perform these actions, it reads registry keys:
PluginInList:HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\InstallService\State\PlugInListList of plugins to load
StaticPluginMap:HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\InstallService\State\StaticPluginMapWhere each plugin's DLL is
When
InstallServicestarts or checks for updates, it:PrivescCheck
I found verifying write permissions via ACL analysis complex. Instead, the check attempts to create the required subkeys (
PlugInListandStaticPluginMap) underHKLM\...\InstallService\State and write test values to them. If successful, the vulnerability exists. Any subkeys or entries created during testing are removed afterward to leave the system unchanged.Windows Build
Researchers say the CVE affects Windows 11. That said, I was able to write to the relevant subkeys on Windows 10, but the exploit did not succeed. This makes me wonder whether there might be a way to adapt the exploit so that the CVE could also be triggered on Windows 10.
References