CVE-2026-40699
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 · uneditedA vulnerability exists in the undisclosed pages in the Configuration utility that may allow a low-privileged authenticated attacker to access to undisclosed sensitive information. 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 confidenceInformation disclosure vulnerability in undisclosed pages of a Configuration utility. A low-privileged authenticated attacker can access sensitive information that should be restricted, indicating improper access control on hidden configuration endpoints.
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>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6>= 17.1.0, <= 17.1.3>= 17.5.0, <= 17.5.1>= 16.1.0, <= 16.1.6CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Big IP versionRun 'tmsh show sys version' or check the Big IP web UI under Dashboard > Overview > System > Software VersionAffected if The version output falls within 16.1.0-16.1.6, 17.1.0-17.1.3, or 17.5.0-17.5.1 for any installed Big IP module (APM, AFM, AWAF, Analytics, AAM, ASM, AVR, or Automation Toolchain)
-
Confirm Configuration utility is accessibleAttempt to access the Configuration utility via the Big IP web UI or API endpoint, or check if the '/configuration' or similar configuration pages are enabled in the management interfaceAffected if The Configuration utility is exposed and accessible to authenticated users
-
Verify low-privileged user access restrictionsLog in with a low-privileged (non-admin) user account and attempt to enumerate or access hidden or undocumented configuration endpoints that should be restricted to administrative rolesAffected if A low-privileged authenticated user can access sensitive configuration data or pages that should be restricted to higher-privilege roles
You are affected if your Big IP version falls within the affected ranges AND the Configuration utility is accessible to low-privileged authenticated users who can reach undisclosed endpoints.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate to a supported software version if a patch is available. Restrict and audit access to configuration utilities, ensuring low-privileged accounts cannot reach undisclosed or administrative endpoints.
BIG-IP 16.1.7+ / 17.1.4+ / 17.5.2+ (depending on your current version branch)
- 1. Identify the currently installed BIG-IP version by running 'tmsh show sys version' or checking the Configuration utility (System > Software > Image).
- 2. Determine which version branch your current installation belongs to (16.1.x, 17.1.x, or 17.5.x).
- 3. For BIG-IP 16.1.x: Upgrade to version 16.1.7 or later.
- 4. For BIG-IP 17.1.x: Upgrade to version 17.1.4 or later.
- 5. For BIG-IP 17.5.x: Upgrade to version 17.5.2 or later.
- 6. Download the appropriate hotfix from downloads.f5.com or my.f5.com.
- 7. Upload the ISO/image via the Configuration utility (System > Software > Image) or via tmsh.
- 8. Install the new version following standard BIG-IP upgrade procedures.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40699 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-40699 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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