dbcve.org
F5os COperating system · F5

CVE-2025-59778

HIGH · 7.5 CVSS v3.1 Published 2025-10-15
Fix available
A fix is available. Upgrade to 1.8.2 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
When the Allowed IP Addresses feature is configured on the F5OS-C partition control plane, undisclosed traffic can cause multiple containers to terminate.   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 · low confidence

This is a denial-of-service vulnerability in F5OS-C where the Allowed IP Addresses feature on the partition control plane fails to properly handle certain network traffic, causing multiple containers to crash unexpectedly.

MitigationApply the vendor-supplied patch when available; until then, consider restricting network exposure of the control plane and monitoring for unusual container termination events.

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 COperating system
Affected:>= 1.6.0, <= 1.6.2>= 1.8.0, < 1.8.2

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
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

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

  1. Identify the installed F5OS-C version
    Run 'show system version' or access the F5OS-C management interface to view the system version information
    Affected if The version displayed is >= 1.6.0 and <= 1.6.2, OR >= 1.8.0 and < 1.8.2
  2. Verify partition control plane configuration
    Access the F5OS-C partition management interface and navigate to the control plane network settings to confirm the partition exists
    Affected if A partition with a control plane is configured on the system
  3. Check if Allowed IP Addresses feature is configured
    Examine the partition control plane settings for any configured Allowed IP Address entries or ACL rules restricting access
    Affected if The Allowed IP Addresses feature has IP addresses or ranges defined for the partition control plane
  4. Cross-reference version and feature state
    Compare the detected version against the affected ranges and confirm whether the Allowed IP Addresses feature is actively configured
    Affected if The system runs an affected version AND the Allowed IP Addresses feature is configured on the partition control plane

If the system runs F5OS-C version 1.6.0-1.6.2 or 1.8.0-1.8.2 and has the Allowed IP Addresses feature configured on a partition control plane, the environment is affected by this vulnerability.

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 1.8.2 or later
Fixed in 1.8.2
Interim mitigation

Apply the vendor-supplied patch when available; until then, consider restricting network exposure of the control plane and monitoring for unusual container termination events.

Recommended fix High confidence

F5OS-C version 1.8.2 (or 1.6.3 for 1.6.x branch)

  1. 1. Identify the current F5OS-C partition control plane version using the system management interface or CLI.
  2. 2. If running version 1.6.0-1.6.2, schedule a maintenance window and upgrade to version 1.6.3 or later.
  3. 3. If running version 1.8.0-1.8.1, schedule a maintenance window and upgrade to version 1.8.2 or later.
  4. 4. After upgrade, verify the Allowed IP Addresses feature functions correctly with the new version.
  5. 5. Monitor system logs to confirm containers are no longer terminating unexpectedly.
Caveat Review F5 release notes for any configuration or behavioral changes between your current version and the target upgrade version

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

Fix this in F5os C Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59778 — 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-2025-59778 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