CyberSecBulletin
CVE-2026-41217NVD status: Analyzed

BIG-IP: Incorrect Permission Assignment for Critical Resource

Published Updated By the CyberSecBulletin desk

CVE-2026-41217 is a high-severity incorrect permission assignment for critical resource vulnerability in BIG-IP from F5, with a CVSS 3.1 base score of 7.9 out of 10. It can be exploited with local access to the system by an attacker with administrator privileges, without any action from a user. The record lists versions 21.0.0.2, 17.5.1.6, 17.1.3.2 as the first without the flaw, so updating BIG-IP to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.11% chance of exploitation within 30 days, which is low compared with other CVEs.

Next patch cycle

High severity with no evidence of exploitation so far.

What to do

  1. Update BIG-IP to 21.0.0.2 or 17.5.1.6 or 17.1.3.2, whichever matches your release line, or a later version.
  2. Read the advisory on my.f5.com for workarounds and exact fixed builds.

Affected products and versions

VendorProductAffected versionsFixed in
F5BIG-IP21.0.0 up to, but not including, 21.0.0.2; 17.5.0 up to, but not including, 17.5.1.6; 17.1.0 up to, but not including, 17.1.3.2; 16.1.0 and later21.0.0.2, 17.5.1.6, 17.1.3.2
F5Big-ip Access Policy Manager17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip Advanced Firewall Manager17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip Advanced Web Application Firewall17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip Analytics17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip Application Acceleration Manager17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip Application Security Manager17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip Application Visibility And Reporting17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip Automation Toolchain17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip Carrier-grade Nat17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip Container Ingress Services17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip Ddos Hybrid Defender17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip Domain Name System17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip Edge Gateway17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip Fraud Protection Service17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip Global Traffic Manager17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip Link Controller17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip Local Traffic Manager17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip Policy Enforcement Manager17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip SSL Orchestrator17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip Webaccelerator17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated
F5Big-ip Websafe17.1.0 through 17.1.3; 17.5.0 through 17.5.1; 16.1.0 through 16.1.6; 21.0.0Not stated

Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
LocalThe attacker needs local access or must trick a user into running something.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
HighAdministrator-level access is required first.
User interaction
NoneNo action by a victim is required.
Scope
ChangedThe attack can reach beyond the vulnerable component into other systems.
Confidentiality
HighAll data handled by the component can be read.
Integrity
HighData or code can be modified at will.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N. Scored by CNA (f5.com).

Scoring systemScoreSeverityScored by
CVSS 4.08.3HighCNA (f5.com)
CVSS 3.17.9HighCNA (f5.com)

Official description

A vulnerability exists in an undisclosed BIG-IP TMOS Shell (tmsh) command that may allow an authenticated attacker with resource administrator or administrator role to execute arbitrary system commands with higher privileges. In Appliance mode deployments, a successful exploit can allow the attacker to cross a security boundary. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Incorrect Permission Assignment for Critical Resource

The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.

How developers prevent this class of flaw

  • When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
  • Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly. This will allow you to maintain more fine-grained control over your resources.
  • During program startup, explicitly set the default permissions or umask to the most restrictive setting possible. Also set the appropriate permissions during program installation. This will prevent you from inheriting insecure permissions from any user who installs or runs the program.

More Incorrect Permission Assignment for Critical Resource vulnerabilities (CWE-732)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
  3. Record last changed materially (score, affected products, status or references).

References

Other vulnerabilities in BIG-IP

All BIG-IP vulnerabilities

Recent Incorrect Permission Assignment for Critical Resource vulnerabilities

Spotted an error? Tell us.