Raspberry Pi Compute Module 4S · Version Status

Raspberry Pi Compute Module 4S End of Life Date

Raspberry Pi Compute Module 4S end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Raspberry Pi Compute Module 4S is actively supported. EOL date: January 1, 2034.
📅 Get reminded before Raspberry Pi Compute Module 4S reaches EOL on January 1, 2034 — alerts 90, 30 & 7 days out.
Google →
EOL Date
Jan 1, 2034
2702 days remaining
Latest Release
Standard release
Release Date
Apr 4, 2022
Raspberry Pi Compute Module 4S series
Lifecycle detail

Raspberry Pi cm4s was released on April 4, 2022 and support is scheduled to end on January 1, 2034 — a planned supported lifespan of 11 years and 9 months, in line with the 11 years and 9 months median for Raspberry Pi releases.

← Raspberry Pi Zero 2 W All Raspberry Pi versions Raspberry Pi 5 →
20 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
10/10 None available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →  ·  View score card →
All Raspberry Pi Versions
VersionLatestEOL DateStatus
1 Model B Jul 14, 2014 EOL
1 Model A Nov 10, 2014 EOL
Compute Module 1 Jan 1, 2026 EOL
1 Model B+ Jan 1, 2030 Active
1 Model A+ Jan 1, 2030 Active
2 Model B EOL Active
Zero Jan 1, 2030 Active
3 Model B Jan 1, 2028 Active

What does Raspberry Pi Compute Module 4S end of life mean?

When Raspberry Pi Compute Module 4S reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Raspberry Pi Compute Module 4S past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Raspberry Pi 500+ or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Raspberry Pi Compute Module 4S reach end of life?
Raspberry Pi Compute Module 4S reached end of life on January 1, 2034. That is 2702 days remaining.
Is Raspberry Pi Compute Module 4S still supported?
Yes, Raspberry Pi Compute Module 4S is currently supported. The EOL date is January 1, 2034.
What should I upgrade to from Raspberry Pi Compute Module 4S?
The recommended upgrade from Raspberry Pi Compute Module 4S is Raspberry Pi 500+ — the latest actively supported version. Check the Raspberry Pi full timeline for all supported versions.
What are the security risks of running Raspberry Pi Compute Module 4S past EOL?
When Raspberry Pi Compute Module 4S reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Raspberry Pi should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →