Signal is active with 1 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
Kubernetes API server in all versions allow an attacker who is able to create a ClusterIP service and set the spec.externalIPs field, to intercept traffic to that IP address. Additionally, an attacker who is able to patch the status (which is considered a privileged operation and should not typically be granted to users) of a LoadBalancer service can set the status.loadBalancer.ingress.ip to similar effect.
Priority
LOW
Exploitation
NONE
PoC
YES
Patch
AVAILABLE
Momentum
STABLE
If you run products in this scope, you should treat this CVE as relevant to your environment.
3 versions affected across 4 products
| Date | Total | Labels |
|---|
| 2026-02-16 | 1 | General1 |
| 2026-07-27 | 1 | Patch1 |
5/7 Watch this one: .spec.externalIPs is being phased out over several releases. It's tied to CVE-2020-8554, a man-in-the-middle risk. Not gone in 1.36, but start moving to LoadBalancer or Gateway API.
Post summary
The message highlights a man-in-the-middle risk from CVE‑2020‑8554 and advises users to stop using .spec.externalIPs and switch to LoadBalancer or Gateway API before version 1.36.
CVE-2020-8554 https://nvd.nist.gov/vuln/detail/cve-2020-8554
Post summary
The entry merely cites CVE-2020-8554 and links to its NVD page, providing no further detail or context.
4 of 4 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| App | kubernetes | kubernetes | - | - | - |
| App | oracle | communications_cloud_native_core_network_slice_selection_function | 1.2.1 | - | - |
| App | oracle | communications_cloud_native_core_policy | 1.15.0 | - | - |
| App | oracle | communications_cloud_native_core_service_communication_proxy | 1.14.0 | - | - |