AWS WAF Classic 1 · Version Status
AWS WAF Classic 1 End of Life Date
AWS WAF Classic 1 end-of-life date, support status, and CVE risk. Dates read at the vendor's own lifecycle pages (docs.aws.amazon.com); the source of each date is on the product page.
⚠
AWS WAF Classic 1 is past end of life. This version no longer receives security patches. 31 days past EOL — migrate to a supported version immediately.
EOL Date
Oct 7, 2026
31 days past EOL
Latest Release
—
Standard release
Release Date
—
AWS WAF Classic 1 series
Where these dates come from
End of lifeOct 7, 2026Our catalog, built from the vendor pages · docs.aws.amazon.commedium · 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
It has been past its end-of-life date for 31 days.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 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 →
Extended Support
Extended AWS WAF Classic 1 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
All AWS WAF Classic Versions
| Version | Latest | EOL Date | Status |
|---|
| → 1 |
— |
Oct 7, 2026 |
EOL |
What does AWS WAF Classic 1 end of life mean?
When AWS WAF Classic 1 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 AWS WAF Classic 1 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to a supported version or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does AWS WAF Classic 1 reach end of life?
AWS WAF Classic 1 reached end of life on October 7, 2026. This version is no longer receiving security patches.
Is AWS WAF Classic 1 still supported?
No. AWS WAF Classic 1 reached end of life on October 7, 2026 and is no longer receiving security patches.
What should I upgrade to from AWS WAF Classic 1?
What are the security risks of running AWS WAF Classic 1 past EOL?
Since AWS WAF Classic 1 reached end of life, the maintainers no longer issue 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 AWS WAF Classic should migrate immediately or implement compensating controls.