F5os AOperating system · F5
CVE-2025-61955
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 F5OS-A and F5OS-C systems that may allow an authenticated attacker with local access to escalate their privileges. A successful exploit may allow the attacker to cross a security boundary. 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 confidenceA local privilege escalation vulnerability in F5OS-A and F5OS-C allows an authenticated attacker with local access (physical or console) to escalate privileges beyond their assigned role. The vulnerability may enable crossing security boundaries, potentially leading to unauthorized access to administrative functions or sensitive data.
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
F5os AOperating system
>= 1.5.1, < 1.5.4= 1.8.0
F5os COperating system
>= 1.6.0, <= 1.6.2>= 1.8.0, < 1.8.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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
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 the F5OS product variantLog into the F5OS system and run 'show system version' or check the product model/name to determine if it is F5OS-A (appliance) or F5OS-C (container)Affected if The system is identified as either F5OS-A or F5OS-C variants
-
Determine the installed F5OS versionRun the command 'show system version' or 'tmsh show sys version' to retrieve the exact version number installed on the systemAffected if The displayed version falls within any of these ranges: F5OS-A >= 1.5.1 and < 1.5.4, or = 1.8.0; F5OS-C >= 1.6.0 and <= 1.6.2, or >= 1.8.0 and < 1.8.2
-
Verify local user account configurationRun 'show auth user' or check /config/ips/aaa.xml (if accessible) to list locally configured user accounts on the systemAffected if One or more local user accounts exist with privileges that could be escalated beyond their assigned role
-
Assess physical and console access exposureReview physical security controls and console access policies to determine if untrusted individuals could obtain local console access to the F5OS deviceAffected if Physical security is not restricted or console access is available to untrusted personnel
A user is affected if their F5OS-A or F5OS-C version matches the vulnerable ranges AND local accounts exist with physical or console access exposure.
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 · scoped1.5.41.8.2
Apply the vendor-provided patch or upgrade to a supported F5OS version that addresses this vulnerability. For systems that cannot be immediately patched, restrict physical and console access to trusted personnel only.
F5OS-A: 1.5.4+ or 1.8.1+; F5OS-C: 1.6.3+ or 1.8.2+
- 1. Identify the current F5OS version by running 'show version' in the F5OS CLI
- 2. For F5OS-A: If running 1.5.1-1.5.3, upgrade to version 1.5.4 or later; if running 1.8.0, upgrade to version 1.8.1 or later
- 3. For F5OS-C: If running 1.6.0-1.6.2, upgrade to version 1.6.3 or later; if running 1.8.0-1.8.1, upgrade to version 1.8.2 or later
- 4. Upload the upgrade image to the F5OS system via the web UI or SCP
- 5. Execute the upgrade using 'upgrade <image-name>' command in F5OS CLI
- 6. Confirm the upgrade completed successfully and verify the new version with 'show version'
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in F5os A
Scoped from the published advisory
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-61955 — 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-61955 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