Executive Summary

Amazon Web Services (AWS) has published an official security advisory documenting a high-severity privilege escalation vulnerability in the Amazon EKS Pod Identity Agent. Tracked under CVE-2026-54201, the vulnerability carries a CVSS v3.1 base score of 8.1 (High) and affects Kubernetes workloads running on Amazon Elastic Kubernetes Service (EKS).

EKS Pod Identity simplifies the association of AWS Identity and Access Management (IAM) roles with Kubernetes service accounts by running a node-local daemon that intercepts metadata requests from containerized applications. Under specific race conditions and header manipulation vectors, an unprivileged pod sharing a worker node could trick the daemon into returning temporary AWS security credentials belonging to other pods on that node.

Vulnerability Mechanics: Local Header Spoofing & TCP Connection Re-Use

The EKS Pod Identity Agent runs as a daemonset on each EKS worker node, listening on a link-local IPv4 address (169.254.170.23:80). When a container requests IAM credentials via the AWS SDK, the request passes through the agent, which validates the pod's service account token and requests temporary AWS credentials from the EKS backend service.

Researchers identified that HTTP keep-alive connection reuse between client containers and the node-local agent allowed an attacker to pipeline crafted HTTP requests. By injecting spoofed internal headers (x-aws-eks-pod-identity-token) on an existing socket before the agent's authentication context reset, an attacker could hijack credential streams destined for pods with highly permissive IAM roles (e.g. S3 administrators or RDS cluster managers).

# Checking EKS Pod Identity Add-on version
aws eks describe-addon   --cluster-name production-workloads   --addon-name eks-pod-identity-agent   --query "addon.addonVersion"
# Vulnerable version output: v1.2.0-eksbuild.1

Cloud Blast Radius & Cross-Tenant Exposure

In Kubernetes clusters hosting multi-tenant workloads or microservices with varying trust levels, this flaw significantly undermined node-level tenant isolation:

  • A compromised public-facing web microservice could extract IAM credentials assigned to an internal billing or data-processing service account running on the same EC2 node.
  • Extracted credentials carry the full IAM permissions assigned to the target role, allowing attackers to pivot into broader AWS services (DynamoDB, KMS, Secrets Manager) across the tenant's account.

Remediation & Hardening Actions

AWS has deployed protective hotfixes across all managed control plane endpoints and updated the open-source agent codebase. Cluster administrators must complete the following actions:

  1. Update EKS Pod Identity Add-On: Upgrade the cluster add-on to version v1.3.0 or higher across all managed clusters: 
    aws eks update-addon   --cluster-name production-workloads   --addon-name eks-pod-identity-agent   --addon-version v1.3.0-eksbuild.1   --resolve-conflicts OVERWRITE
  2. Implement Pod Node Anti-Affinity: Ensure that workloads requiring sensitive administrative IAM roles are isolated on dedicated node groups using Kubernetes taints and tolerations.
  3. Audit CloudTrail Telemetry: Review AWS CloudTrail logs for calls to AssumeRoleForPodIdentity originating from unexpected client IPs or unusual session patterns.