F5 AccessApplication · F5
CVE-2025-54809
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 · uneditedF5 Access for Android before version 3.1.2 which uses HTTPS does not verify the remote endpoint identity. 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 · high confidenceF5 Access for Android before version 3.1.2 fails to verify the remote endpoint identity when using HTTPS connections, allowing man-in-the-middle attackers to intercept and modify encrypted traffic between the app and the F5 server.
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
F5 AccessApplication
>= 3.1.0, < 3.1.2CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/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.
-
Check installed F5 Access versionOn the Android device, go to Settings > Apps > F5 Access, or use 'adb shell pm list packages' followed by 'adb shell dumpsys package <package_name>' to view versionInfo. Locate the version number displayed.Affected if The installed version is 3.1.0 or 3.1.1 (any version >= 3.1.0 but < 3.1.2)
-
Confirm app handles HTTPS connectionsReview the F5 Access app functionality to determine if it is configured to connect to F5 servers using HTTPS for VPN or remote access sessions.Affected if The app uses HTTPS connections to communicate with F5 servers while running a vulnerable version
If F5 Access for Android version 3.1.0 or 3.1.1 is installed and uses HTTPS connections to F5 servers, the lack of remote endpoint identity verification exposes traffic to man-in-the-middle interception.
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 · scoped3.1.2
Update F5 Access for Android to version 3.1.2 or later, which implements proper SSL/TLS certificate verification for HTTPS connections.
F5 Access for Android version 3.1.2
- Upgrade F5 Access for Android to version 3.1.2 or later from the Google Play Store or your organization's approved mobile device management (MDM) solution
- Verify the upgrade was successful by checking the app version in Settings > Apps > F5 Access
- For organizations using MDM, push the updated app to all managed Android devices running affected versions
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in F5 Access
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-54809 — 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-2025-54809 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