Every CVE Search/ Get API key

CVE-2019-1167

System.Management.Automation subject to bypass via script debugging

4.1 MediumFix available

A security feature bypass vulnerability exists in Windows Defender Application Control (WDAC) which could allow an attacker to bypass WDAC enforcement, aka 'Windows Defender Application Control Security Feature Bypass Vulnerability'.

Attack profile

How easy it is to exploit

Attack vector
Local
Complexity
High
Privileges needed
High
User interaction
None

What an attacker can affect

Confidentiality
High
Integrity
None
Availability
None

Exploit likelihood

1.10%Down 3.5 points since Apr 14, 2021
90%50%10%1%

What each source reports

NVD Score used 4.1

A security feature bypass vulnerability exists in Windows Defender Application Control (WDAC) which could allow an attacker to bypass WDAC enforcement, aka 'Windows Defender Application Control Security Feature Bypass Vulnerability'.

Record
CVE-2019-1167
CVSS 3.0
4.1 MediumCVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N
CVSS 2.0
1.9 LowAV:L/AC:M/Au:N/C:P/I:N/A:N
Updated
2026-11-02
CVE List No score

A security feature bypass vulnerability exists in Windows Defender Application Control (WDAC) which could allow an attacker to bypass WDAC enforcement, aka 'Windows Defender Application Control Security Feature Bypass Vulnerability'.

Record
CVE-2019-1167
Updated
2026-11-02
EUVDEUVD-2019-0577 No score

A security feature bypass vulnerability exists in Windows Defender Application Control (WDAC) which could allow an attacker to bypass WDAC enforcement, aka 'Windows Defender Application Control Security Feature Bypass Vulnerability'.

Record
EUVD-2019-0577
Updated
2026-11-03
GitHub AdvisoriesGHSA-5frh-8cmj-gc59 4.1

System.Management.Automation subject to bypass via script debugging

Microsoft Security Advisory CVE-2019-1167: Windows Defender Application Control Security Feature Bypass Vulnerability

Microsoft Security Advisory CVE-2019-1167: Windows Defender Application Control Security Feature Bypass Vulnerability

Executive Summary

A security feature bypass vulnerability exists in Windows Defender Application Control (WDAC) which could allow an attacker to bypass WDAC enforcement. An attacker who successfully exploited this vulnerability could circumvent PowerShell Core Constrained Language Mode on the machine.

To exploit the vulnerability, an attacker would first have access to the local machine where PowerShell is running in Constrained Language mode. By doing that an attacker could leverage script debugging to abuse signed modules in an unintended way.

The update addresses the vulnerability by correcting how PowerShell functions in Constrained Language Mode. System administrators are advised to update PowerShell Core to an unaffected version (see affected software.)

Discussion

Please use PowerShell/PowerShell#TBD for discussion of this advisory.

<a name="affected-software">Affected Software</a>

The vulnerability affects PowerShell Core prior to the following versions:

| PowerShell Core Version | Fixed in | |-------------------------|-------------------| | 6.1 | 6.1.5 | | 6.2 | 6.2.2 |

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 Core is affected.
  2. If you are running a version of PowerShell Core where the executable is not pwsh or pwsh.exe, then you are affected. This only existed for preview version of 6.0.

How do I update to an unaffected version?

Follow the instructions at Installing PowerShell Core to install the latest version of PowerShell Core.

Other Information

Reporting Security Issues

If you have found a potential security issue in PowerShell Core, 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.

What if the update breaks my script or module?

You can uninstall the newer version of PowerShell Core and install the previous version of PowerShell Core. This should be treated as a temporary measure. Therefore, the script or module should be updated to work with the patched version of PowerShell Core.

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-2019-1167

Revisions

V1.0 (July 16, 2019): Advisory published.

Version 1.0 Last Updated 2019-07-16

Record
GHSA-5frh-8cmj-gc59
CVSS 3.0
4.1 MediumCVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N
Updated
2026-11-02
OSV 4.1

A security feature bypass vulnerability exists in Windows Defender Application Control (WDAC) which could allow an attacker to bypass WDAC enforcement, aka 'Windows Defender Application Control Security Feature Bypass Vulnerability'.

Record
CVE-2019-1167
CVSS 3.0
4.1 MediumCVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N
Updated
2026-11-02
OSVGHSA-5frh-8cmj-gc59 4.1

System.Management.Automation subject to bypass via script debugging

Microsoft Security Advisory CVE-2019-1167: Windows Defender Application Control Security Feature Bypass Vulnerability

Microsoft Security Advisory CVE-2019-1167: Windows Defender Application Control Security Feature Bypass Vulnerability

Executive Summary

A security feature bypass vulnerability exists in Windows Defender Application Control (WDAC) which could allow an attacker to bypass WDAC enforcement. An attacker who successfully exploited this vulnerability could circumvent PowerShell Core Constrained Language Mode on the machine.

To exploit the vulnerability, an attacker would first have access to the local machine where PowerShell is running in Constrained Language mode. By doing that an attacker could leverage script debugging to abuse signed modules in an unintended way.

The update addresses the vulnerability by correcting how PowerShell functions in Constrained Language Mode. System administrators are advised to update PowerShell Core to an unaffected version (see affected software.)

Discussion

Please use PowerShell/PowerShell#TBD for discussion of this advisory.

<a name="affected-software">Affected Software</a>

The vulnerability affects PowerShell Core prior to the following versions:

| PowerShell Core Version | Fixed in | |-------------------------|-------------------| | 6.1 | 6.1.5 | | 6.2 | 6.2.2 |

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 Core is affected.
  2. If you are running a version of PowerShell Core where the executable is not pwsh or pwsh.exe, then you are affected. This only existed for preview version of 6.0.

How do I update to an unaffected version?

Follow the instructions at Installing PowerShell Core to install the latest version of PowerShell Core.

Other Information

Reporting Security Issues

If you have found a potential security issue in PowerShell Core, 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.

What if the update breaks my script or module?

You can uninstall the newer version of PowerShell Core and install the previous version of PowerShell Core. This should be treated as a temporary measure. Therefore, the script or module should be updated to work with the patched version of PowerShell Core.

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-2019-1167

Revisions

V1.0 (July 16, 2019): Advisory published.

Version 1.0 Last Updated 2019-07-16

Record
GHSA-5frh-8cmj-gc59
CVSS 3.0
4.1 MediumCVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:N/A:N
Updated
2026-11-02

Affected products

Affected packages

Affected packages
PackageAffectedFixed
System.Management.Automation
NuGet
6.2.0 up to 6.2.2
6.2.2
System.Management.Automation
NuGet
6.1.0 up to 6.1.5
6.1.5
System.Management.Automation
NuGet
6.2.0 up to 6.2.2, plus listed versions
6.2.1
6.2.2
System.Management.Automation
NuGet
6.1.0 up to 6.1.5, plus listed versions
6.1.16.1.26.1.36.1.4
6.1.5

History

History
RecordedChangedSources
aliasesEUVD
first indexedCVE List, GitHub Advisories, NVD, OSV

Dates are when Every CVE recorded each change. Upstream dates may differ.

In short

CVE-2019-1167 is a medium vulnerability (CVSS 4.1) in Microsoft Powershell Core, published July 17, 2019. No source lists public exploit code. EPSS puts the chance of exploitation in the next 30 days at 1.10%, the 65th percentile. Fixed in System.Management.Automation 6.2.2.

References

MoveEnter Open