dbcve.org
NULL Pointer DereferenceWeakness · CWE-476

CVE-2026-2507

HIGH · 7.5 CVSS v3.1 Published 2026-02-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 BIG-IP AFM or BIG-IP DDoS is provisioned, undisclosed traffic can cause TMM 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 · moderate confidence

This is a denial of service vulnerability in F5 BIG-IP systems where the AFM (Advanced Firewall Manager) or BIG-IP DDoS modules are provisioned. Specific undisclosed traffic patterns can cause the TMM (Traffic Management Microkernel) to terminate, resulting in service disruption and potential availability loss.

MitigationApply the F5 patch or hotfix when released. Until then, consider network-level filtering or rate limiting as compensating controls, and restrict management access to trusted networks.

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

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 product
    Run 'tmsh show sys hardware' or check the BIG-IP login page/version to confirm this is a F5 BIG-IP system
    Affected if Not a F5 BIG-IP platform - not affected
  2. Check if AFM module is provisioned
    Run 'tmsh list sys provision module' and look for 'afm' with a level other than 'none', or check under System > Provisioning in the GUI
    Affected if AFM is provisioned (level not 'none') - potentially affected
  3. Check if BIG-IP DDoS module is provisioned
    Run 'tmsh list sys provision module' and look for 'dos' with a level other than 'none', or check under System > Provisioning in the GUI
    Affected if BIG-IP DDoS is provisioned (level not 'none') - potentially affected
  4. Compare installed version to any known affected ranges
    Run 'tmsh show sys version' or check the BIG-IP version displayed in the GUI or via 'tmsh show sys version' command
    Affected if Version falls within affected ranges if/when published by F5

The system is affected ONLY if it is a F5 BIG-IP with AFM or BIG-IP DDoS module provisioned AND running a vulnerable version, otherwise it is not affected by this CVE.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the F5 patch or hotfix when released. Until then, consider network-level filtering or rate limiting as compensating controls, and restrict management access to trusted networks.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

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