Font Awesome · Lifecycle Status

Font Awesome End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Font Awesome versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Font Awesome 7.2.0 is actively supported. No versions approaching EOL in the next 6 months.
Latest Active
7.2.0
7 series
Next EOL
None upcoming
Active Versions
7
of 7 total
EOL Versions
0
no longer patched
10 / 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
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 →
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 201320142015201620172018201920202021202220232024202520261234567TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
1 1.0.0 Mar 3, 2012 No EOL date Supported Active
2 2.0.0 Jun 4, 2012 No EOL date Supported Active
3 3.2.1 Jan 2, 2013 No EOL date Supported Active
4 4.7.0 Oct 23, 2013 No EOL date Supported Active
5 LTS 5.15.4 Feb 5, 2018 TBD Supported Active
6 LTS 6.7.2 Feb 7, 2022 TBD Supported Active
7 7.2.0 Jul 22, 2025 TBD Supported Active

What does Font Awesome end of life mean for your organization?

When a version of Font Awesome reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.

Organizations running EOL Font Awesome should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Extended Support Options

If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Font Awesome versions. This is a bridge, not a permanent solution — plan your migration in parallel.

endoflife.ai
Need Extended Support?

We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.

Contact Us →
Frequently Asked Questions
What is the end-of-life date for Font Awesome?
See the full table above for all Font Awesome version EOL dates.
When is the Font Awesome support end date?
Each Font Awesome version has its own support end date — see the table above for every version's date.
What is the latest supported version of Font Awesome?
The latest active version of Font Awesome is 7.2.0. Always verify against the table above as support windows can change.
What happens when Font Awesome reaches end of life?
When Font Awesome reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Font Awesome?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Font Awesome versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →