AWS Load Balancer Controller automatically detaches externally associated web ACL from Application Load Balancers

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

not scored

EPSS

No dated EPSS signal available.

As published by the source; long descriptions are shortened.

Summary The AWS Load Balancer Controller includes an optional, default-enabled feature that manages WAF WebACLs on Application Load Balancers (ALBs) on your behalf. In versions 2.8.1 and earlier, if the WebACL annotation [1] alb.ingress.kubernetes.io/wafv2-acl-arn or alb.ingress.kubernetes.io/waf-acl-id was absent on Ingresses, the controller would automatically disassociate any existing WebACL from the ALBs, including those associated by AWS Firewall Manager (FMS). Customers on impacted versions should upgrade to prevent this issue from occurring. Impact WebACLs attached to ALBs managed by the AWS Load Balancer Controller through methods other than Ingress annotations may be automatically removed, leaving the ALBs unprotected by WebACL. Impacted versions: [=2.0.0;<2.8.2] Patches We addressed this issue in version 2.8.2 [2] and recommend customers upgrade. Now, if the WebACL annotation is absent on Ingress objects, any existing WebACL on the ALB will remain intact instead of being…

Published by the source

24 Oct 2024, 19:04 UTC

Last modified by the source

24 Oct 2024, 19:04 UTC

Source last checked

26 Oct 2026, 15:05 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rjfv-pjvx-mjgv

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-rjfv-pjvx-mjgv

Advisory: AWS Load Balancer Controller automatically detaches externally associated web ACL from Application Load Balancers
IDs: GHSA-rjfv-pjvx-mjgv
Record: https://patchnext.com/advisories/ghsa-rjfv-pjvx-mjgv (revision 1, source checked 26 Oct 2026, 15:05 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: sigs.k8s.io/aws-load-balancer-controller 2.8.2. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go sigs.k8s.io/aws-load-balancer-controller: affected >= 2.0.0, < 2.8.2; fixed in 2.8.2

## Suggested inspection (read-only)
- Go sigs.k8s.io/aws-load-balancer-controller: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on sigs.k8s.io/aws-load-balancer-controller.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-rjfv-pjvx-mjgv (GitHub-reviewed advisory GHSA-rjfv-pjvx-mjgv lists affected ranges: Go sigs.k8s.io/aws-load-balancer-controller >=2.0.0 <2.8.2)

Commands are suggestions: review each one before running it.