dbcve.org
Big Ip Access Policy ManagerApplication · F5

CVE-2026-40703

MEDIUM · 5.4 CVSS v3.1 Published 2026-05-13
Fix available
A fix is available. Upgrade to after 17.5.1 or later.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A cross-site request forgery (CSRF) vulnerability exists in the dashboard of the BIG-IP Configuration utility.  Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A cross-site request forgery (CSRF) vulnerability exists in the BIG-IP Configuration utility's dashboard, allowing an attacker to potentially trick an authenticated administrator into performing unintended administrative actions via maliciously crafted requests.

MitigationApply the vendor-provided patch when released. Until then, administrators should avoid clicking untrusted links while logged into the Configuration utility and consider implementing additional session controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Big Ip Access Policy ManagerApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6
Big Ip Advanced Firewall ManagerApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6
Big Ip Advanced Web Application FirewallApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6
Big Ip AnalyticsApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6
Big Ip Application Acceleration ManagerApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6
Big Ip Application Security ManagerApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6
Big Ip Application Visibility And ReportingApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6
Big Ip Automation ToolchainApplication
Affected:>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the F5 BIG-IP product and version
    Run 'tmsh show sys version' or 'bigpipe version' to retrieve the installed BIG-IP version
    Affected if The installed version falls within 17.1.0-17.1.3, 17.5.0-17.5.1, or 16.1.0-16.1.6
  2. Confirm the Configuration utility is accessible
    Check if the BIG-IP Configuration utility (web-based management interface) is exposed and reachable on the management IP or a self IP
    Affected if The Configuration utility is accessible over HTTP/HTTPS and the version is within the affected ranges
  3. Verify administrative access is enabled
    Check via 'tmsh list auth user admin' or by confirming active admin sessions exist in the Configuration utility
    Affected if Administrative users can log into the Configuration utility and the version is within affected ranges
  4. Check for CSRF protection configuration
    Review the Configuration utility settings or proxy configuration for existing CSRF token enforcement. This typically requires access to F5 support or examining HTTP response headers for SameSite cookie attributes
    Affected if The version is within affected ranges and no SameSite=Strict or SameSite=Lax cookie attributes are enforced on session cookies

A user is affected if they are running any of the listed F5 BIG-IP modules (APM, AFM, ASM, Analytics, AAM, AVR, Automation Toolchain) within version ranges 17.1.0-17.1.3, 17.5.0-17.5.1, or 16.1.0-16.1.6 AND the Configuration utility is accessible to authenticated administrators.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 17.5.1
Interim mitigation

Apply the vendor-provided patch when released. Until then, administrators should avoid clicking untrusted links while logged into the Configuration utility and consider implementing additional session controls.

Recommended fix Moderate confidence

Upgrade to versions beyond 17.1.3 (e.g., 17.1.4+), beyond 17.5.1 (e.g., 17.5.2+), or beyond 16.1.6 (e.g., 16.1.7+) - consult my.f5.com for exact fixed releases

  1. 1. Identify the current BIG-IP version by navigating to System > Software Management > ISO Image or checking the version displayed in the BIG-IP Configuration utility
  2. 2. Determine which version branch is currently deployed (16.1.x, 17.1.x, or 17.5.x)
  3. 3. Access the F5 Downloads page at https://downloads.f5.com/ or log in to my.f5.com to obtain the latest available version for your branch
  4. 4. Download the appropriate hotfix or upgrade ISO for your version branch that addresses CVE-2026-40703
  5. 5. Follow F5 upgrade documentation to upload and install the new version using UCSR or manual ISO installation
  6. 6. After upgrade, verify the BIG-IP Configuration utility is accessible and functional
  7. 7. Test the dashboard functionality to confirm the CSRF protection is working properly
Caveat Review F5 release notes for any configuration or compatibility changes between versions; test in non-production environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Big Ip Access Policy Manager Scoped from the published advisory
  • Consultation3.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
24.0 hours of engineering $4,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,720.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40703 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40703 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data