Microsoft Security Advisory CVE-2026-50523: PowerShell Remote Code Execution Vulnerability
Ninguém assumiu esta issue ainda.
Avaliação
- Dificuldade
- 2/5
- Tempo estimado
- 1-3 horas
- Facilidade para iniciantes
- 15/100
- Tipo de issue
- Documentação
- Clareza
- Precisa de esclarecimento
- Status de atividade
- Pouca atividade
- Stack de tecnologia
- shell
- Domínio
- documentation, security
Direção de pesquisa
This is a published Microsoft security advisory for PowerShell 7 with several leftover TBD comment markers in the body, but the payload does not say which of them should change or what the finished text should look like. Read the affected-software table and the Revisions section first, and confirm the intended scope with a maintainer before editing. The payload names no tests or code to run, so there is no clear way to show the work is done.
Escrita pelo modelo de indexação a partir do texto da issue.
Descrição
Microsoft Security Advisory CVE-2026-50523: PowerShell Remote Code Execution Vulnerability
Executive Summary
Improper neutralization of special elements used in a command ('command injection') in PowerShell 7 allows an authorized attacker to execute code 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.
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 | Yes |
| macOS | No |
| Linux | No |
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-50523
Revisions
V1.0 (August 17, 2026): Advisory published.
Version 1.0
Last Updated 2026-08-17
- Linguagem predominante
- Sem dados de linguagem
- Estrelas
- 20
- Forks
- 8
- Métricas de merge de PRs
- Nenhum PR com merge em 30d
Preparar o ambiente
- Sem Dockerfile nem arquivo Docker Compose
- Sem modelo de pull request
- Ler o guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Mais de PowerShell/Announcements
-
PowerShell Security
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 5/100
PowerShell/Announcements#101 ·
-
PowerShell Security
Dificuldade 5/5 Mais de uma semana Facilidade para iniciantes 5/100
PowerShell/Announcements#100 ·
-
PowerShell Security
Dificuldade 2/5 Menos de uma hora Facilidade para iniciantes 8/100
PowerShell/Announcements#99 ·
-
PowerShell Security
Dificuldade 3/5 Meio dia Facilidade para iniciantes 8/100
PowerShell/Announcements#98 ·
-
PowerShell Security
Dificuldade 2/5 Menos de uma hora Facilidade para iniciantes 8/100
PowerShell/Announcements#97 ·
Todas as issues de PowerShell/Announcements
Issues semelhantes
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 68/100
Mantenedores costumam responder em até 1 dia
-
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 85/100
components-web-app/docs#311 ·
-
Dificuldade 1/5 Menos de uma hora Facilidade para iniciantes 78/100
-
JS/TS: JSX props compile errors should link to a doc page explaining the static-list requirementAbertaarea: js-runtime enhancement exists-upstream interop priority: low
Dificuldade 2/5 1-3 horas Facilidade para iniciantes 78/100
shayanhabibi/fickl#307 ·
Mantenedores costumam responder em até 1 dia