Microsoft Security Advisory CVE-2026-62909: .NET Elevation of Privilege Vulnerability
まだ誰も着手していません。
評価
調査の方向性
This is a published Microsoft security advisory for PowerShell 7 on Linux and macOS, not a code task, and the payload names no file, test or entry point to change. The only open edits are the TBD placeholders in the advisory text, which belong to the maintainers. Treat it as read-only context and point the .NET runtime questions to the linked dotnet/runtime issue instead.
索引モデルが issue の本文から書いたものです。
説明
Microsoft Security Advisory CVE-2026-62909: .NET Elevation of Privilege Vulnerability
Executive Summary
Microsoft is releasing this security advisory to provide information about a vulnerability in .NET diagnostics IPC. This advisory also provides guidance on what developers can do to update their applications to remove this vulnerability.
A missing error check in .NET causes an improper ACL to be applied to a shared resource, resulting in local elevation of privilege.
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.
Please use https://github.com/dotnet/runtime/issues/132157 for discussion of the .NET Runtime aspects this advisory.
Affected Software
The vulnerability affects PowerShell 7 prior to the following versions:
| PowerShell 7 Version | Affected version | Patched Version |
|---|---|---|
| 7.6 | <7.6.5 | 7.6.5 |
| 7.5 | <7.5.10 | 7.5.10 |
| 7.4 | <7.4.19 | 7.4.19 |
The vulnerability affects PowerShell when running on the following operating systems:
| Operating System | Affected |
|---|---|
| Windows | No |
| 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-62909
Revisions
V1.0 (August 17, 2026): Advisory published.
Version 1.0
Last Updated 2026-08-17
- 主要言語
- 言語のデータがありません
- スター
- 20
- フォーク
- 8
- PR マージ指標
- 30日以内にマージされた PR はありません
環境構築
- Dockerfile・Docker Compose ファイルなし
- プルリクエストのテンプレートなし
- コントリビューションガイドを読む
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
PowerShell/Announcements のほかの issue
-
PowerShell Security
難易度 5/5 1週間以上 初心者へのやさしさ 5/100
PowerShell/Announcements#101 ·
-
PowerShell Security
難易度 5/5 1週間以上 初心者へのやさしさ 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
-
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
openremote/openremote#3487 · コメント 1 件 ·
-
bug(cli): theme file home-directory check uses startsWith (sibling dirs pass, Windows casing fails)オープンarea/core kind/bug priority/p2 status/bot-triaged
難易度 2/5 1〜3時間 初心者へのやさしさ 79/100
google-gemini/gemini-cli#29955 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信
-
intermediate security tests
難易度 1/5 1時間未満 初心者へのやさしさ 86/100
BistaDinesh03/critique#151 ·
メンテナーはふだん 1 日以内に返信
-
medium-priority security
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
DigiBanks99/menlo#474 ·
メンテナーはふだん 1 日以内に返信
-
bug confirmed issue
難易度 2/5 1〜3時間 初心者へのやさしさ 72/100
open-webui/open-webui#33200 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信