Salt 3006 (LTS)
Salt 3006 (LTS)
Third-party support for the Salt 3006 (LTS): 24/7 engineers manage issues, remediate vulnerabilities, and help you maintain compliance — independent of the vendor contract.
24/7 engineers own your Salt 3006 (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
- salt
- release
- 3006
- product Label
- Salt
- release Label
- 3006 (LTS)
- codename
- lts
- true
- latest Version
- 3006.27
- release Date
- 2023-04-18
- maintained
- true
- source Url
- https://endoflife.date/salt
Lifecycle Dates
- End of Service Life
- Jun 30, 2027
- Last OEM Support
- Jul 31, 2026
OEM vs. 3rd Party Support
See how third-party support compares to the vendor contract for Salt 3006 (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 Salt 3006 (LTS)?
Vulnerability Remediation
Scanning, mitigation and patch-around guidance for Salt 3006 (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.
Salt 3006 (LTS) Support: Frequently Asked Questions
Is the Salt 3006 (LTS) still supported?
Yes. The Salt 3006 (LTS) is currently supported by Salt, and third-party support is available as an alternative — issue management, vulnerability remediation, and compliance help independent of the vendor contract.
When is the Salt 3006 (LTS) end of service life (EOSL) date?
Salt lists the end of service life for the Salt 3006 (LTS) as Jun 30, 2027.
Can I keep using the Salt 3006 (LTS) after its EOSL date?
Yes. EOSL means Salt 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 Salt 3006 (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 Salt 3006 (LTS)
3 published CVEs affect the Salt 3006 (LTS), including 1 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-38824 | CRITICAL | 9.6 | Jun 13, 2025 | Directory traversal vulnerability in recv_file method allows arbitrary files to be written to the master cache directory. |
| CVE-2023-20897 | MEDIUM | 5.3 | Sep 5, 2023 | Salt masters prior to 3005.2 or 3006.2 contain a DOS in minion return. After receiving several bad packets on the request server equal to the number of worker threads, the master will become unresponsive to return requests until restarted. |
| CVE-2023-20898 | MEDIUM | 4.2 | Sep 5, 2023 | Git Providers can read from the wrong environment because they get the same cache directory base name in Salt masters prior to 3005.2 or 3006.2. Anything that uses Git Providers with different environments can get garbage data or the wrong data, which can lead to wrongful data disclosure, wrongful executions, data corruption and/or crash. |