CVE-2026-42930: Authentication Bypass in F5 BIG-IP
プラットフォーム
linux
コンポーネント
bigip
修正版
21.0.0.2
CVE-2026-42930 describes an authentication bypass vulnerability in F5 BIG-IP when operating in Appliance mode. An authenticated administrator with the 'Administrator' role can circumvent restrictions, allowing them to perform actions they shouldn't be able to. This vulnerability impacts versions 16.1.0 through 21.0.0.2; a fix is available in version 21.0.0.2.
影響と攻撃シナリオ翻訳中…
Successful exploitation of CVE-2026-42930 allows an authenticated administrator to bypass Appliance mode restrictions within the F5 BIG-IP system. This effectively grants them elevated privileges and the ability to modify configurations or access sensitive data beyond their intended scope. The attacker could potentially gain full control of the BIG-IP system, leading to data breaches, service disruption, or further compromise of the network. The blast radius extends to any systems or services relying on the BIG-IP for load balancing, security, or application delivery.
悪用の状況翻訳中…
CVE-2026-42930 was published on May 13, 2026. Severity is rated HIGH with a CVSS score of 8.7. Public proof-of-concept (POC) code is currently unavailable. The vulnerability is not listed on CISA KEV as of this writing. Exploitation probability is considered medium, given the requirement for authenticated access but the potential for significant impact.
脅威インテリジェンス
エクスプロイト状況
CISA SSVC
CVSS ベクトル
これらのメトリクスの意味は？
- Attack Vector
- ネットワーク — インターネット経由でリモートから悪用可能。物理・ローカルアクセス不要。
- Attack Complexity
- 低 — 特別な条件不要。安定して悪用可能。
- Privileges Required
- 高 — 管理者または特権アカウントが必要。
- User Interaction
- なし — 自動かつ無音の攻撃。被害者は何もしない。
- Scope
- 変化あり — 攻撃が脆弱なコンポーネントを超えて他のシステムに波及可能。
- Confidentiality
- 高 — 機密性の完全喪失。全データが読み取り可能。
- Integrity
- 高 — 任意のデータの書き込み・変更・削除が可能。
- Availability
- なし — 可用性への影響なし。
影響を受けるソフトウェア
弱点分類 (CWE)
タイムライン
- 予約済み
- 公開日
緩和策と回避策翻訳中…
The primary mitigation for CVE-2026-42930 is to upgrade to F5 BIG-IP version 21.0.0.2 or later, which contains the fix. If immediate upgrade is not possible, consider implementing stricter role-based access controls within BIG-IP to limit the privileges of the 'Administrator' role. Review existing configurations to identify any potential misconfigurations that could exacerbate the impact of this vulnerability. Monitor BIG-IP logs for any suspicious activity related to administrator accounts. After upgrade, confirm the fix by verifying that Appliance mode restrictions are properly enforced for the 'Administrator' role.
修正方法翻訳中…
Actualice su sistema BIG-IP a una versión corregida. F5 ha publicado parches para abordar esta vulnerabilidad. Consulte la nota de seguridad K000160876 en el sitio web de F5 para obtener instrucciones detalladas sobre cómo aplicar las actualizaciones.
よくある質問翻訳中…
What is CVE-2026-42930 — Authentication Bypass in F5 BIG-IP?
CVE-2026-42930 is a HIGH severity vulnerability affecting F5 BIG-IP versions 16.1.0–21.0.0.2. It allows an authenticated administrator to bypass Appliance mode restrictions, potentially granting unauthorized access.
Am I affected by CVE-2026-42930 in F5 BIG-IP?
If you are running F5 BIG-IP in Appliance mode and are using versions 16.1.0 through 21.0.0.2, you are potentially affected by this vulnerability. Check your version immediately.
How do I fix CVE-2026-42930 in F5 BIG-IP?
Upgrade to F5 BIG-IP version 21.0.0.2 or later to resolve this vulnerability. If immediate upgrade isn't possible, implement stricter role-based access controls.
Is CVE-2026-42930 being actively exploited?
As of the current date, there are no confirmed reports of active exploitation of CVE-2026-42930 in the wild, but the potential for exploitation exists.
Where can I find the official F5 advisory for CVE-2026-42930?
Refer to the official F5 security advisory for CVE-2026-42930 on the F5 website: [https://www.f5.com/security/center/advisory/f5-security-advisory-42930](https://www.f5.com/security/center/advisory/f5-security-advisory-42930)
今すぐ試す — アカウント不要
Upload any manifest (composer.lock, package-lock.json, WordPress plugin list…) or paste your component list. You get a vulnerability report instantly. Uploading a file is just the start: with an account you get continuous monitoring, Slack/email alerts, multi-project and white-label reports.
依存関係ファイルをドラッグ＆ドロップ
composer.lock、package-lock.json、requirements.txt、Gemfile.lock、pubspec.lock、Dockerfile...