CuraSec

tag: F5-Big-Ip · 4 items

2026-09-23 · BleepingComputer · source ↗ #f5-big-ip#zero-day#rce
  • Engineer — Act: BIG-IP APM is a common enterprise edge/access device; active RCE exploitation with a patch now available means immediate upgrade is warranted — apply F5’s security updates to BIG-IP APM without waiting for your normal patch window.
  • SOC/IR — Act: Active exploitation of an edge access device requires an assume-breach posture — sweep BIG-IP APM logs for anomalous sessions, unauthorized admin activity, or unusual outbound connections dating back before the patch was issued.
  • Leader — Act: Confirm within the week whether BIG-IP APM is in your estate; if so, direct engineering to treat this as emergency patching and brief incident response, as actively exploited perimeter RCE zero-days carry real breach risk before patching completes.
2026-09-23 · The Hacker News · source ↗ #zero-day#rce#f5-big-ip
  • Engineer — Act: CISA KEV-listed, public PoC, and confirmed active exploitation on F5 BIG-IP APM systems configured as OAuth authorization servers — apply F5’s engineering hotfix for CVE-2026-94127 immediately and verify whether any BIG-IP instances serve that OAuth role.
  • SOC/IR — Act: Active exploitation of an edge device that precedes patching means assume-breach posture — sweep BIG-IP APM logs for anomalous unauthenticated requests to OAuth endpoints and hunt for post-compromise lateral movement since at least September 22.
  • Leader — Act: Actively exploited unauthenticated RCE on a widely-deployed enterprise network appliance warrants same-week action — confirm whether BIG-IP APM is in use as an OAuth server, verify engineering has the hotfix on track, and be ready to brief leadership if it is.
  • Signals: CVE-2026-94127 — CISA KEV: listed, EPSS 0.01, public PoC on GitHub
2026-09-09 · BleepingComputer · source ↗ #f5-big-ip#rootkit#fileless-malware
  • Engineer — Act: Active breach campaign targeting F5 BIG-IP APM appliances — a common enterprise edge device. Audit your BIG-IP APM fleet for indicators of compromise: look for anomalous PHP interpreter activity, unexpected in-memory web shell behavior, and verify firmware/software versions against F5’s latest advisories.
  • SOC/IR — Act: The fileless, memory-resident web shell evades file-based detection, so standard endpoint scans will miss it. Hunt for anomalous PHP file-load interception and unusual outbound connections from F5 BIG-IP APM processes; if your org runs BIG-IP APM, treat as assume-breach and initiate a memory forensics sweep.
  • Leader — Plan: Active compromise campaign against widely-deployed F5 BIG-IP APM appliances — confirm with your network/infra team whether your org runs these devices, verify that monitoring and patching processes are in place, and be prepared to brief leadership if exposure is confirmed.
2026-09-09 · The Hacker News · source ↗ #f5-big-ip#web-shell#memory-injection
  • Engineer — Act: F5 BIG-IP APM is a widely-deployed enterprise edge appliance and the malware is linked to confirmed break-ins; disk-based file integrity checks won’t detect this web shell, so audit BIG-IP APM instances using network-based IOCs and memory forensics from the Sophos September 7 analysis.
  • SOC/IR — Act: Active exploitation of an edge appliance combined with a memory-resident web shell means EDR and file-scan detections will miss it; assume-breach posture applies — hunt using any network or request-pattern IOCs from the Sophos report and flag all BIG-IP APM devices for manual inspection.
  • Leader — Act: If your organization runs F5 BIG-IP APM, direct the security team to perform a compromise assessment this week — the memory-evasion technique means standard monitoring may have already missed a breach on this access gateway.