CVE-2026-22549 Details
Description
A vulnerability exists in F5 BIG-IP Container Ingress Services that may allow excessive permissions to read cluster secrets. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
A vulnerability in F5 BIG-IP Container Ingress Services for Kubernetes and OpenShift, specifically in versions 2.0.0 through 2.20.1 and 1.0.0 through 1.14.0, may grant excessive permissions to read cluster secrets. This issue affects the control plane only, with no exposure on the data plane.
Users can upgrade to BIG-IP Container Ingress Services versions 2.20.2 or 1.14.1 to address this vulnerability. For version 2.20.1, Helm version 0.0.36 can be used to install the update. To mitigate the vulnerability without upgrading, permissions can be narrowed down to specific resources and namespaces as needed.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Feb 4, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://my.f5.com/manage/s/article/K000157960 | [email protected] | Vendor Advisory |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| NVD-CWE-noinfo | Insufficient Information to Classify Weakness | [email protected] |
| CWE-250 | Execution with Unnecessary Privileges | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| f5 big-ip container ingress services | >= 1.0.0, <= 1.14.0 >= 2.0.0, < 2.2.0.2 |
CPE
Remediation
| |
| kubernetes kubernetes | All versions |
CPE
Remediation
| |
| redhat openshift | All versions |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Feb 13, 2026 | Initial Analysis | [email protected] |
| Feb 4, 2026 | New CVE Received | [email protected] |