Microsoft PowerShell 7.4 (LTS)
Microsoft PowerShell 7.4 (LTS)
The Microsoft PowerShell 7.4 (LTS) reaches end of service life on Nov 10, 2026. Third-party support keeps it managed past that date — issue management, vulnerability remediation, and compliance maintenance from 24/7 engineers.
24/7 engineers own your Microsoft PowerShell 7.4 (LTS) incidents end to end.
Mitigation and patch-around guidance when the vendor no longer ships fixes.
Controls evidence and documentation that keep auditors satisfied.
Specifications
- product
- powershell
- release
- 7.4
- product Label
- Microsoft PowerShell
- release Label
- 7.4 (LTS)
- codename
- lts
- true
- latest Version
- 7.4.19
- release Date
- 2023-11-16
- maintained
- true
- source Url
- https://endoflife.date/powershell
Lifecycle Dates
- End of Service Life
- Nov 10, 2026
- Last OEM Support
- Nov 10, 2026
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Microsoft PowerShell 7.4 (LTS) — monitoring, break/fix, vulnerability work, operations and compliance, before and after EOSL.
| Feature | OEM Support | 3rd Party Support |
|---|---|---|
| Post-EOSL Support | ||
| Break/Fix Support | Until EOSL | |
| 24/7 Monitoring | ||
| Vulnerability Scanning & Remediation | ||
| Managed Operations | ||
| Procedure & Configuration Review | ||
| Compliance & Audit Documentation | Limited | |
| Discounted Migration to Other Platforms |
Why Choose 3rd Party Support for Microsoft PowerShell 7.4 (LTS)?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Microsoft PowerShell 7.4 (LTS) when the vendor no longer ships fixes.
Compliance Maintenance
Procedure review, controls evidence and the documentation auditors ask for — maintained continuously, not scrambled at audit time.
24/7 Expert Support
Engineers who know this release monitor, manage and fix issues around the clock — break/fix to managed operations.
Microsoft PowerShell 7.4 (LTS) Support: Frequently Asked Questions
Is the Microsoft PowerShell 7.4 (LTS) still supported?
Yes, but Microsoft support for the Microsoft PowerShell 7.4 (LTS) ends on Nov 10, 2026. You can upgrade on the vendor's schedule, or move to third-party support and keep the release you're on — issues managed, vulnerabilities remediated, compliance maintained.
When is the Microsoft PowerShell 7.4 (LTS) end of service life (EOSL) date?
Microsoft lists the end of service life for the Microsoft PowerShell 7.4 (LTS) as Nov 10, 2026.
Can I keep using the Microsoft PowerShell 7.4 (LTS) after its EOSL date?
Yes. EOSL means Microsoft stops issuing patches and support — the software itself keeps running. Third-party support covers it from there: issue management, security vulnerability remediation, and the compliance documentation auditors ask for, for as long as you choose to run it.
How much does third-party support for the Microsoft PowerShell 7.4 (LTS) cost?
Typically 40-70% below the OEM maintenance renewal price. Exact pricing depends on quantity, service level and location — request a quote and we respond within 24 hours.
Known Vulnerabilities Affecting Microsoft PowerShell 7.4 (LTS)
14 published CVEs affect the Microsoft PowerShell 7.4 (LTS), including 13 rated critical or high severity. Our 24/7 engineers help you assess exposure, prioritize fixes and apply available patches.
| CVE | Severity | CVSS | Published | Summary |
|---|---|---|---|---|
| CVE-2024-0057 | CRITICAL | 9.1 | Jan 9, 2024 | NET, .NET Framework, and Visual Studio Security Feature Bypass Vulnerability |
| CVE-2026-70337 | HIGH | 8.8 | Aug 11, 2026 | Relative path traversal in Microsoft PowerShell Core allows an unauthorized attacker to execute code over a network. |
| CVE-2026-50523 | HIGH | 7.8 | Aug 14, 2026 | Improper neutralization of special elements used in a command ('command injection') in Microsoft PowerShell allows an authorized attacker to execute code locally. |
| CVE-2026-70338 | HIGH | 7.8 | Aug 11, 2026 | Improper control of generation of code ('code injection') in Microsoft PowerShell allows an unauthorized attacker to bypass a security feature locally. |
| CVE-2026-26143 | HIGH | 7.8 | Apr 14, 2026 | Improper input validation in Microsoft PowerShell allows an unauthorized attacker to bypass a security feature locally. |
| CVE-2025-30399 | HIGH | 7.5 | Jun 13, 2025 | Untrusted search path in .NET and Visual Studio allows an unauthorized attacker to execute code over a network. |
| CVE-2024-26190 | HIGH | 7.5 | Mar 12, 2024 | Microsoft QUIC Denial of Service Vulnerability |
| CVE-2024-21392 | HIGH | 7.5 | Mar 12, 2024 | .NET and Visual Studio Denial of Service Vulnerability |
| CVE-2026-58612 | HIGH | 7.4 | Aug 11, 2026 | Server-side request forgery (ssrf) in Microsoft PowerShell Core allows an unauthorized attacker to disclose information over a network. |
| CVE-2026-59119 | HIGH | 7.3 | Aug 11, 2026 | Incorrect default permissions in Microsoft PowerShell allows an authorized attacker to elevate privileges locally. |
| CVE-2025-25004 | HIGH | 7.3 | Oct 14, 2025 | Improper access control in Microsoft PowerShell allows an authorized attacker to elevate privileges locally. |
| CVE-2024-21409 | HIGH | 7.3 | Apr 9, 2024 | .NET, .NET Framework, and Visual Studio Remote Code Execution Vulnerability |
| CVE-2025-49734 | HIGH | 7.0 | Sep 9, 2025 | Improper restriction of communication channel to intended endpoints in Windows PowerShell allows an authorized attacker to elevate privileges locally. |
| CVE-2024-30045 | MEDIUM | 6.3 | May 14, 2024 | .NET and Visual Studio Remote Code Execution Vulnerability |