VendorsEdge

F5

F5 makes BIG-IP application delivery controllers and their modules (LTM, APM, ASM), BIG-IQ management, NGINX and F5 Distributed Cloud services.

Response trend, 6 months: Not enough history
Open now: None
Latest incident: 22 Sep 2026
Incidents on record: 2

Response to exploited bugs

Not rated. 1 reviewed zero-day on record. A grade needs at least 3.

Fixing privately reported bugs

Not rated. No private reports in the grading window.

What a grade means. B means the vendor met the public norm, such as a first fix within 7 days of the first public report or a private fix within 120 days. Taking half the norm time scores 92, an A. Taking twice the norm time scores 43, a D−. How grades work

Embed this report card

Why these grades

Response to exploited bugs: not rated. 1 reviewed zero-day in the last 36 months. A grade needs at least 3.
First fix within a day, for its one reviewed zero-day.
Every supported version fixed within a day, for its one reviewed zero-day.
First advisory within a day, for its one reviewed zero-day.
Fixing privately reported bugs: not rated. No private reports in the last 36 months.
1 of 2 reviewed exploited bugs had a public fix before exploitation was reported. It does not count toward the response grade.
NR (not rated) means a subject has fewer than 3 data points from the last 36 months, or their recency weights add up to less than one current data point. For response, a data point is a reviewed exploited zero-day. For private fixes, it is a private report (one vendor, one report date). KEV listings alone never rate a vendor. A grade is provisional when the vendor's own evidence does not yet outweigh the starting value, or confidence is below medium.

Response to exploited bugs: sub-scores

Time to first advisory1 zero-day, within a day
80
1 case, low confidence, not used for this vendor
Time to first fix1 zero-day, within a day
80
1 case, low confidence, not used for this vendor
Time to fix all versions1 zero-day, within a day
80
1 case, low confidence, not used for this vendor
OpennessNo machine-readable advisory feed listed. 1 of 1 fixed zero-day with a public fix date for every version.
44
3 cases, low confidence, not used for this vendor

Fixing privately reported bugs: sub-score

Private fix speedNo private reports in the last 36 months
NR
0 cases, not used

Response fingerprint

Compressed time scale

Counts toward the response grade 1

22 Sep 2026
BIG-IP APM OAuth authorization server heap overflow allowing unauthenticated RCE

Not graded 1: n-days, unreviewed timelines and end-of-life products

15 Oct 2025
BIG-IP APM flaw disclosed as DoS in Oct 2025, reclassified as exploited RCE in Mar 2026Not graded: n-day

Vendor silent
Vendor statement, no fix
Fixed for some versions
Open, no fix
Open, partly fixed
Fixed when disclosed
Date only, no time of day

One row per exploited incident, newest first. A tick at the start means a fix existed when the bug went public.

Exploited incidents

First report	Incident	CVSS	Silence	First fix	All fixed	Status	Grade
22 Sep 2026	BIG-IP APM OAuth authorization server heap overflow allowing unauthenticated RCECVE-2026-94127	9.8	0h	0h	same day	Fixed	Counts toward grade
15 Oct 2025	BIG-IP APM flaw disclosed as DoS in Oct 2025, reclassified as exploited RCE in Mar 2026CVE-2025-53521	9.8	0h	same day	same day	Fixed	Not graded: n-day

Private reports

Bugs reported privately to F5 by ZDI or Project Zero.

No privately reported cases from ZDI or Project Zero in the window.

Grade history

Response to exploited bugs: score at the end of each month.

Not rated at any point in this period.

Channels

Get F5's own alerts

XF5 on XFollow the account and turn on notifications.
Advisory pageF5 security advisories (MyF5 K articles)Check the advisory page. It has no push channel.

What we watch

We don't poll this vendor's channels yet. Incidents come from public sources.

See sources and health for when each was last read.