Microsoft Security Advisory CVE-2026-70338: PowerShell Security Feature Bypass Vulnerability

Offen
  • Stimmt etwas nicht?
#88 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit
3/5
Geschätzter Aufwand
Ein halber Tag
Anfängerfreundlichkeit
8/100
Issue-Typ
Dokumentation
Klarheit
Muss geklärt werden
Aktivitätsstatus
Ruhig
Tech-Stack
shell
Bereich
security

Rechercherichtung

This is a draft security advisory with unfilled TBD comments for the summary, mitigation factors, acknowledgments and revision date, and it names no file or test to change. Read the advisory body and the affected-version table first, then confirm with a maintainer which placeholders are still open. Done means the maintainers have decided on the remaining text, which needs security-team input rather than a code change.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

PowerShell Security

Microsoft Security Advisory CVE-2026-70338: PowerShell Security Feature Bypass Vulnerability

Executive Summary

Improper control of generation of code ('code injection') in PowerShell 7 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.

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 Yes
Linux Yes

Advisory FAQ

How do I know if I am affected?

If all of the following are true:

  1. 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-70338

Revisions

V1.0 (August 17, 2026): Advisory published.

Version 1.0
Last Updated 2026-08-17

Vorherrschende Sprache
Keine Sprachdaten
Sterne
20
Forks
8
Keine gemergten PRs in 30 T.

Entwicklungsumgebung

Erste Schritte

  1. Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
  3. Forken Sie das Repository und arbeiten Sie in einem Branch.
  4. Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus PowerShell/Announcements

Alle Issues in PowerShell/Announcements

Ähnliche Issues

Weitere Issues zu Security

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.