Microsoft Security Advisory CVE-2026-26143: Microsoft PowerShell Security Feature Bypass Vulnerability
还没有人认领这个 Issue。
评估
调研方向
This is a published security advisory with no requested code change, and the fix belongs to the PowerShell/PowerShell repository, not this one. Read the affected-versions table and the note on -SkipLimitCheck with Import-PowerShellDataFile, then check the installed version with pwsh -v. Done means confirming which versions are patched (7.4.14, 7.5.5, 7.6.0) and, if you want to contribute, opening a question on the linked support path.
由索引模型根据 Issue 内容生成。
描述
Microsoft Security Advisory CVE-2026-26143: Microsoft PowerShell Security Feature Bypass Vulnerability
Executive Summary
Improper input validation in Microsoft PowerShell allows an unauthorized attacker to bypass a security feature locally.
System administrators are advised to update PowerShell 7 to an unaffected version (see affected software).
Discussion
Please open a support question to discuss the PowerShell aspects of this advisory.
Mitigation factors
What kind of security feature could be bypassed by successfully exploiting this vulnerability?
Exploiting this vulnerability bypasses dynamic-expression security checks which may lead to arbitrary code execution when then -SkipLimitCheck is used with Import-PowerShellDataFile. If you do not use the -SkipLimitCheck switch, you are not affected.
Affected Software
The vulnerability affects PowerShell 7 prior to the following versions:
| PowerShell 7 Version | Affected version | Patched Version |
|---|---|---|
| 7.6 | <7.6.0 | 7.6.0 |
| 7.5 | <7.5.5 | 7.5.5 |
| 7.4 | <7.4.14 | 7.4.14 |
The vulnerability affects PowerShell when running on the following operating systems:
| Operating System | Affected |
|---|---|
| Windows | Yes |
| macOS | Yes |
| Linux | Yes |
Advisory FAQ
How do I know if I am affected?
If all of the following are true:
- Run
pwsh -v, then, check the version in the table in Affected Software to see if your version of PowerShell 7 is affected.
How do I update to an unaffected version?
Follow the instructions at Installing PowerShell 7 to install the latest version of PowerShell 7.
Updating PowerShell 7 using Microsoft Update
Updating PowerShell 7 using Microsoft Update
Other Information
Reporting Security Issues
If you have found a potential security issue in PowerShell 7,
please email details to [email protected].
Support
You can ask questions about this issue on GitHub in the PowerShell organization.
This is located at https://github.com/PowerShell/.
The Announcements repo (https://github.com/PowerShell/Announcements)
will contain this bulletin as an issue and will include a link to a discussion issue where you can ask questions.
Disclaimer
The information provided in this advisory is provided "as is" without warranty of any kind. Microsoft disclaims all warranties, either express or implied, including the warranties of merchantability and fitness for a particular purpose. In no event shall Microsoft Corporation or its suppliers be liable for any damages whatsoever including direct, indirect, incidental, consequential, loss of business profits or special damages, even if Microsoft Corporation or its suppliers have been advised of the possibility of such damages. Some states do not allow the exclusion or limitation of liability for consequential or incidental damages so the foregoing limitation may not apply.
What if the update breaks my script or module?
You can uninstall the newer version of PowerShell 7 and install the previous version of PowerShell 7.
This should be treated as a temporary measure.
Therefore, the script or module should be updated to work with the patched version of PowerShell 7.
Acknowledgments
Microsoft recognizes the efforts of those in the security community who help us protect customers through coordinated vulnerability disclosure.
See acknowledgments for more information.
External Links
CVE-2026-26143
Revisions
V1.0 (April 14, 2026): Advisory published.
Version 1.0
Last Updated 2026-04-14
- 主要语言
- 没有语言数据
- 星标
- 20
- 派生
- 8
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
PowerShell/Announcements 的其他 Issue
-
PowerShell Security
难度 5/5 一周以上 新手友好度 5/100
PowerShell/Announcements#101 ·
-
PowerShell Security
难度 5/5 一周以上 新手友好度 5/100
PowerShell/Announcements#100 ·
-
PowerShell Security
难度 2/5 1 小时以内 新手友好度 8/100
PowerShell/Announcements#99 ·
-
PowerShell Security
难度 3/5 半天 新手友好度 8/100
PowerShell/Announcements#98 ·
-
PowerShell Security
难度 2/5 1 小时以内 新手友好度 8/100
PowerShell/Announcements#97 ·
查看 PowerShell/Announcements 的全部 Issue
相似的 Issue
-
scope:core type:security
难度 2/5 1-3 小时 新手友好度 75/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 66/100
mailgun/mailgun.js#544 ·
-
Mend: dependency security vulnerability
难度 2/5 1-3 小时 新手友好度 68/100
维护者通常 1 天内回复
-
security-scan-failure
难度 2/5 1-3 小时 新手友好度 70/100
semantica-agi/semantica#2182 ·
维护者通常 1 天内回复
-
area: dependencies auto-generated cwe: 400 dependencies ecosystem: npm help wanted package: glob scope: runtime security security-alert severity: medium source: dependabot supply-chain vulnerability
难度 2/5 1-3 小时 新手友好度 74/100
tdk-landscape/tdk-cli-core#2814 ·