CVE-2026-22549: BIG-IP Container Ingress Services vulnerability
Published Feb 4, 2026
·Updated
A vulnerability exists in F5 BIG-IP Container Ingress Services that may allow excessive permissions to read cluster secrets.
Affected Software
7 affected componentsFixes available
F5 BIG-IP Container Ingress Services
F5 BIG-IP Container Ingress Services for Kubernetes and OpenShift>=2.0.0<=2.20.1
2.20.22.20.1
F5 BIG-IP Container Ingress Services for Kubernetes and OpenShift>=1.0.0<=1.14.0
All of the following
Any of the following
F5 BIG-IP Container Ingress Services>=1.0.0<=1.14.0
F5 BIG-IP Container Ingress Services>=2.0.0<2.2.0.2
Any of the following
Kubernetes kubernetes
redhat Openshift
Event History
Feb 4, 2026
Advisory Published
via F5·02:22 PM
Data Sourced
via F5·02:22 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via MITRE·03:15 PM
Data Sourced
via MITRE·03:15 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:16 PM
DescriptionSeverityWeaknessAffected Software
Frequently Asked Questions
1
What is the severity of CVE-2026-22549?
The severity of CVE-2026-22549 is classified based on its potential impact on permissions for reading cluster secrets.
2
How do I fix CVE-2026-22549?
To fix CVE-2026-22549, upgrade to F5 BIG-IP Container Ingress Services versions 2.20.22.20.1 or higher.
3
What systems are affected by CVE-2026-22549?
CVE-2026-22549 affects F5 BIG-IP Container Ingress Services for Kubernetes and OpenShift.
4
What kind of permissions issue does CVE-2026-22549 present?
CVE-2026-22549 may allow excessive permissions that can lead to unauthorized access to cluster secrets.
5
Is there a recommended version to mitigate CVE-2026-22549?
Yes, F5 recommends upgrading to version 2.20.22.20.1 or higher to mitigate the risks of CVE-2026-22549.