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 reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
✓
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.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Jan 1, 2034
2612 days remaining
Latest Release
—
Standard release
Release Date
Apr 4, 2022
Raspberry Pi Compute Module 4S series
Where these dates come from
End of lifeJan 1, 2034endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseApr 4, 2022endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
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.
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
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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Raspberry Pi Compute Module 4S past its EOL date creates a growing attack surface that a clean scan result does not rule out.
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 reaches end of life on January 1, 2034. That is 2612 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 vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Raspberry Pi should migrate immediately or implement compensating controls.