Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.36% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-70338High confidence
Microsoft PowerShell Security Feature Bypass Vulnerability
Microsoft · PowerShell 7.4
7.8HighCVSS 3.1
Within 7 days
Patch availableHigh technical severity; prioritise exposed affected systems while verifying vendor guidance.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityHigh→Operational priority:High, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict local access and enforce least privilege on affected hosts.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Microsoft PowerShell 7.4 and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch available01
What, why and how
Improper control of generation of code ('code injection') in Microsoft PowerShell allows an unauthorized attacker to bypass a security feature locally.
What
Improper control of generation of code ('code injection') in Microsoft PowerShell allows an unauthorized attacker to bypass a security feature locally.
Why
Untrusted data can cross into a code-evaluation path and be interpreted as executable instructions.
How
An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
What
Improper control of generation of code ('code injection') in Microsoft PowerShell allows an unauthorized attacker to bypass a security feature locally.
Why
Untrusted data can cross into a code-evaluation path and be interpreted as executable instructions.
How
An attacker operating through local access may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- local access → Improper Control of Generation of Code ('Code Injection') → cause the confidentiality, integrity or availability impact described by the vendor
- Attack surface
- Local
- Privileges required
- None: unauthenticated exploitation is possible
- User interaction
- Required interaction required
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Unchanged: impact remains within the vulnerable component's security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-94 ↗
CWE-94: Improper Control of Generation of Code ('Code Injection'). The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:CCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVLocalAttack vector: The attacker needs local access to the vulnerable system.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRNonePrivileges required: The attacker does not need an account or existing privileges.UIRequiredUser interaction: Another user must perform an action for exploitation to succeed.SUnchangedScope: The security impact remains within the vulnerable component's authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- The issue can support a local privilege or sandbox boundary transition; normal system utilities may then be available in the gained context.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Patch available
- Affected
- Action
- Review the linked authoritative reference and apply the recorded fixed release appropriate to the affected product branch.
- Workaround
- No verified workaround is recorded. Limit untrusted access and use least privilege until authoritative guidance is available.
04
Evidence and provenance
Published 11 Aug 2026 · Last source change 29 Sept 2026, 20:22 UTC · CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE recordCVE.org · 5.2
CVSS sourceCNA
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-56767
Product sourceCNA
Remediation sourceCVE/CNA references
CWE sourceOther authority
NVD statusNVD enriched
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-23.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-23 · vendor advisory: msrc.microsoft.com/CVE-2026-70338
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-70338
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.secure@microsoft.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-23.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-23 · vendor advisory: msrc.microsoft.com/CVE-2026-70338
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-70338
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.secure@microsoft.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Vendor guidanceAuthoritative vendor guidance changed: removed remediation: acn.gov.it/aggiornamenti-mensili-microsoft-23.secure@microsoft.com ↗
- Before
- remediation: acn.gov.it/aggiornamenti-mensili-microsoft-23 · vendor advisory: msrc.microsoft.com/CVE-2026-70338
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-70338
- Remediation statusRemediation status changed from Mitigation available to Awaiting fix.secure@microsoft.com ↗
- Before
- Mitigation available
- After
- Awaiting fix
- Affected versionsThe structured affected or fixed version information changed.CNA ↗
- Before
- 7.4.0 < 7.4.19.0; 7.5.0 < 7.5.10.0; 7.6.0 < 7.6.5 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- PowerShell 7.4: 7.4.0 < 7.4.19.0; PowerShell 7.5: 7.5.0 < 7.5.10.0; PowerShell 7.6: 7.6.0 < 7.6.5 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- Vendor guidanceAuthoritative vendor guidance changed: added vendor advisory: msrc.microsoft.com/CVE-2026-70338.secure@microsoft.com ↗
- Before
- no authoritative guidance recorded
- After
- vendor advisory: msrc.microsoft.com/CVE-2026-70338
- Remediation statusRemediation status changed from Awaiting fix to Mitigation available.CSIRT Italia ↗
- Before
- Awaiting fix
- After
- Mitigation available
CVE published
Remediation guidance recorded
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.