BugZero | F5 BugID 759778 - API Protection request log messages from different...

F5 - Defect ID: 759778

API Protection request log messages from different virtual servers have the same flow ID

F5 - Defect ID: 759778

API Protection request log messages from different virtual servers have the same flow ID

Last updated on July 18th, 2026

BugZero Risk Score
7.0 High

Overall: 7.0

Severity: 7.3

Community: 4.2

Lifecycle: 10.0

What is the BugZero Risk Score?

F5 Integration

Learn more about where this data comes from

F5 Integration

Learn more

BugZero Plan

Streamline upgrades with automated vendor bug scrubs

BugZero Plan

Learn more

BugZero Prevent

Wish you caught this bug sooner? Get proactive today.

BugZero Prevent

Learn more

Bug Details

Priority: 3-Major
Status: Resolved
Impact Category: Access Policy Manager

Description

Symptoms

API Protection flow IDs are the same for request log messages that are generated from different configurations.

Impact

Support/flow-IDs should be unique to request flows

Conditions

-- Configure two api protected virtual servers with (api-prot profile, access profile, virtual) -- Generate virtually simultaneous requests to each virtual server

Workaround

None

Fix Information

None

Change history

Links

Original Vendor Announcement

Relevant Products

Click on a version to see all relevant bugs

Affected versions:15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 15.1.10.7, 15.1.10.8

Fixed versions: No known fixed versions

Relevant Products

Click on a version to see all relevant bugs

Fixed versions: No known fixed versions

Top F5 Defects

9.6Defect ID: 546260
TMM can crash if using the v6rd profile
9.6Defect ID: 934133
Unable to Create/delete ltm virtual server via CLI transaction when destination is not specified on the ltm virtual object
9.6Defect ID: 1154417
Profile based attack is not mitigated at hardware on L2 wire setup
9.6Defect ID: 913713
Rebooting a blade causes MCPd to core as it rejoins the cluster
9.6Defect ID: 2141125
Multicast traffic is dropped with incorrect VLAN tagging

F5 Integration

Learn more about where this data comes from

F5 Integration

Learn more

BugZero Plan

Streamline upgrades with automated vendor bug scrubs

BugZero Plan

Learn more

BugZero Prevent

Wish you caught this bug sooner? Get proactive today.

BugZero Prevent

Learn more

Ready to prevent the next vendor outage?

Get a demo

F5 - Defect ID: 759778

API Protection request log messages from different virtual servers have the same flow ID

F5 - Defect ID: 759778

API Protection request log messages from different virtual servers have the same flow ID

Last updated on July 18th, 2026

BugZero Risk Score7.0 High

Bug Details

Symptoms

Impact

Conditions

Workaround

Fix Information

Links

Top F5 Defects

Ready to prevent the next vendor outage?

F5 - Defect ID: 759778

API Protection request log messages from different virtual servers have the same flow ID

F5 - Defect ID: 759778

API Protection request log messages from different virtual servers have the same flow ID

Last updated on July 18th, 2026

BugZero Risk Score7.0 High

Bug Details

Symptoms

Impact

Conditions

Workaround

Fix Information

Links

Top F5 Defects

Ready to prevent the next vendor outage?

BugZero Risk Score
7.0 High

BugZero Risk Score
7.0 High