CVE-2025-46706: BIG-IP iRules vulnerability
Noroxi assessment
Priority: Monitor (action score 34/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.42% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to CISA the attack is automatable: targets can be found by mass scanning.
- Fixed version: F5 BIG-IP Next CNF 1.4.0-EHF-3; F5 BIG-IP Next SPK 1.7.14-EHF-2.
Low priority for now. Upgrade to F5 BIG-IP Next CNF 1.4.0-EHF-3; F5 BIG-IP Next SPK 1.7.14-EHF-2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
When an iRule containing the HTTP::respond command is configured on a virtual server, undisclosed requests can cause an increase in memory resource utilization. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
- Published
- Oct 15, 2025
- Updated
- Oct 18, 2026
- EPSS
- 0.4% · 37th percentile
- CWE
- CWE-770
Report tools
Action score
34
Monitor
Low priority for now.
- CVSS
- 34 / 40 · 8.7 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · f5
- 7.5
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| f5 | big-ip next cloud-native network functions | cpe:2.3:a:f5:big-ip_next_cloud-native_network_functions |
| f5 | big-ip next service proxy for kubernetes | cpe:2.3:a:f5:big-ip_next_service_proxy_for_kubernetes |
| f5 | big-ip access policy manager | cpe:2.3:a:f5:big-ip_access_policy_manager |
| f5 | big-ip advanced firewall manager | cpe:2.3:a:f5:big-ip_advanced_firewall_manager |
| f5 | big-ip advanced web application firewall | cpe:2.3:a:f5:big-ip_advanced_web_application_firewall |
| f5 | big-ip analytics | cpe:2.3:a:f5:big-ip_analytics |
| f5 | big-ip application acceleration manager | cpe:2.3:a:f5:big-ip_application_acceleration_manager |
| f5 | big-ip application security manager | cpe:2.3:a:f5:big-ip_application_security_manager |
| f5 | big-ip application visibility and reporting | cpe:2.3:a:f5:big-ip_application_visibility_and_reporting |
| f5 | big-ip automation toolchain | cpe:2.3:a:f5:big-ip_automation_toolchain |
| f5 | big-ip carrier-grade nat | cpe:2.3:a:f5:big-ip_carrier-grade_nat |
| f5 | big-ip container ingress services | cpe:2.3:a:f5:big-ip_container_ingress_services |
and 11 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- f5 big-ip access policy manager17.1.0 and later · before 17.1.2.2
- f5 big-ip access policy manager16.1.0 and later · before 16.1.6
- f5 big-ip advanced firewall manager17.1.0 and later · before 17.1.2.2
- f5 big-ip advanced firewall manager16.1.0 and later · before 16.1.6
- f5 big-ip advanced web application firewall17.1.0 and later · before 17.1.2.2
- f5 big-ip advanced web application firewall16.1.0 and later · before 16.1.6
- f5 big-ip analytics17.1.0 and later · before 17.1.2.2
- f5 big-ip analytics16.1.0 and later · before 16.1.6
- f5 big-ip application acceleration manager16.1.0 and later · before 16.1.6
- f5 big-ip application acceleration manager17.1.0 and later · before 17.1.2.2
- f5 big-ip application security manager17.1.0 and later · before 17.1.2.2
- f5 big-ip application security manager16.1.0 and later · before 16.1.6
- f5 big-ip application visibility and reporting16.1.0 and later · before 16.1.6
- f5 big-ip application visibility and reporting17.1.0 and later · before 17.1.2.2
- f5 big-ip automation toolchain17.1.0 and later · before 17.1.2.2
- f5 big-ip automation toolchain16.1.0 and later · before 16.1.6
- f5 big-ip carrier-grade nat17.1.0 and later · before 17.1.2.2
- f5 big-ip carrier-grade nat16.1.0 and later · before 16.1.6
- f5 big-ip container ingress services17.1.0 and later · before 17.1.2.2
- f5 big-ip container ingress services16.1.0 and later · before 16.1.6
Versions reported by the vendor
Affected version ranges reported by the assigning authority (f5). Independent of NVD's CPE analysis and usually ahead of it.
F5 BIG-IP
- 17.5.0 and laternot affected
- 17.1.0 and later · before 17.1.2.2affected
- 16.1.0 and later · before 16.1.6affected
- 15.1.0 and laternot affected
F5 BIG-IP Next CNF
- 2.0.0 and laternot affected
- 1.1.0 and lateraffectedfixed in 1.4.0-EHF-3
F5 BIG-IP Next SPK
- 2.0.0 and laternot affected
- 1.7.0 and lateraffectedfixed in 1.7.14-EHF-2
Same product
f5: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-59762BIG-IP HTTP/2 vulnerability34Monitor
- CVE-2026-42409BIG-IP HTTP/2 vulnerability34Monitor
- CVE-2025-61974BIG-IP SSL/TLS vulnerability34Monitor
Published before and after this one in the same product
- ← EarlierCVE-2024-23306Feb 14, 2024 · BIG-IP Next CNF & SPK vulnerability28Monitor
- ← EarlierCVE-2024-28132May 8, 2024 · BIG-IP NEXT CNF vulnerability17Monitor
- Later →CVE-2025-48008Oct 15, 2025 · BIG-IP MPTCP vulnerability34Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| F5 BIG-IP Next CNF | 1.4.0-EHF-3 | Vendor (CNA) |
| F5 BIG-IP Next SPK | 1.7.14-EHF-2 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- F5finder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2026-59762273 days apartBIG-IP HTTP/2 vulnerability34Monitor
- CVE-2025-556700 days apartBIG-IP Next (CNF, SPK, and Kubernetes) vulnerability28Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- X
Weakness class (CWE)
CWE-770 · Allocation of Resources Without Limits or ThrottlingCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- FloodingCAPEC-125likelihood: High · Medium
- Excessive AllocationCAPEC-130likelihood: Medium · Medium
- XML Ping of the DeathCAPEC-147likelihood: Low · Medium
- Exponential Data ExpansionCAPEC-197likelihood: High · Medium
- Serialized Data Parameter BlowupCAPEC-229likelihood: High · High
- Serialized Data with Nested PayloadsCAPEC-230likelihood: Medium · High
- Oversized Serialized Data PayloadsCAPEC-231likelihood: Medium · High
- HTTP DoSCAPEC-469Low
ATT&CK techniques
- Network Denial of Service:Direct Network FloodT1498.001
- Network Denial of Service:Reflection AmplificationT1498.002
- Endpoint Denial of ServiceT1499
- Endpoint Denial of Service: OS Exhaustion FloodT1499.001
- Endpoint Denial of Service:Service Exhaustion FloodT1499.002
- Endpoint Denial of Service:Application Exhaustion FloodT1499.003
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.