What is GHSA-RJFV-PJVX-MJGV?

GHSA-RJFV-PJVX-MJGV is a low-severity security vulnerability in sigs.k8s.io/aws-load-balancer-controller (go), affecting versions >= 2.0.0, < 2.8.2. It is fixed in 2.8.2.

Which versions of sigs.k8s.io/aws-load-balancer-controller are affected by GHSA-RJFV-PJVX-MJGV?

sigs.k8s.io/aws-load-balancer-controller (go) versions >= 2.0.0, < 2.8.2 is affected.

Is there a fix for GHSA-RJFV-PJVX-MJGV?

Yes. GHSA-RJFV-PJVX-MJGV is fixed in 2.8.2. Upgrade to this version or later.

Is GHSA-RJFV-PJVX-MJGV exploitable, and should I be worried?

Whether GHSA-RJFV-PJVX-MJGV is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether GHSA-RJFV-PJVX-MJGV is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

How do I fix GHSA-RJFV-PJVX-MJGV?

Upgrade sigs.k8s.io/aws-load-balancer-controller to 2.8.2 or later.

GHSA-RJFV-PJVX-MJGV

Q: Which versions of sigs.k8s.io/aws-load-balancer-controller are affected by GHSA-RJFV-PJVX-MJGV?

sigs.k8s.io/aws-load-balancer-controller (go) versions >= 2.0.0, < 2.8.2 is affected.

Q: Is there a fix for GHSA-RJFV-PJVX-MJGV?

Yes. GHSA-RJFV-PJVX-MJGV is fixed in 2.8.2. Upgrade to this version or later.

Q: Is GHSA-RJFV-PJVX-MJGV exploitable, and should I be worried?

Whether GHSA-RJFV-PJVX-MJGV is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether GHSA-RJFV-PJVX-MJGV is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix GHSA-RJFV-PJVX-MJGV?

Upgrade sigs.k8s.io/aws-load-balancer-controller to 2.8.2 or later.

Summary

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

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.

Impacted versions: [>=2.0.0;<2.8.2]

Workarounds

If the previous behavior affected you, you can mitigate it by disabling the WebACL management feature using the --enable-waf and --enable-wafv2 command-line flags [3]

References

If you have any questions or comments about this advisory, we ask that you contact AWS/Amazon Security via our vulnerability reporting page [4] or directly via email to [email protected]. Please do not create a public GitHub issue.

[1] https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/guide/ingress/annotations/#addons

[2] https://github.com/kubernetes-sigs/aws-load-balancer-controller/releases/tag/v2.8.2

[3] https://kubernetes-sigs.github.io/aws-load-balancer-controller/latest/deploy/configurations/#waf-addons

[4] Vulnerability reporting page: https://aws.amazon.com/security/vulnerability-reporting

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.

Affected versions

sigs.k8s.io/aws-load-balancer-controller (>= 2.0.0, < 2.8.2)

Security releases

sigs.k8s.io/aws-load-balancer-controller → 2.8.2 (go)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

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 removed.

Frequently Asked Questions

What is GHSA-RJFV-PJVX-MJGV? GHSA-RJFV-PJVX-MJGV is a low-severity security vulnerability in sigs.k8s.io/aws-load-balancer-controller (go), affecting versions >= 2.0.0, < 2.8.2. It is fixed in 2.8.2.
Which versions of sigs.k8s.io/aws-load-balancer-controller are affected by GHSA-RJFV-PJVX-MJGV? sigs.k8s.io/aws-load-balancer-controller (go) versions >= 2.0.0, < 2.8.2 is affected.
Is there a fix for GHSA-RJFV-PJVX-MJGV? Yes. GHSA-RJFV-PJVX-MJGV is fixed in 2.8.2. Upgrade to this version or later.
Is GHSA-RJFV-PJVX-MJGV exploitable, and should I be worried? Whether GHSA-RJFV-PJVX-MJGV is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether GHSA-RJFV-PJVX-MJGV is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix GHSA-RJFV-PJVX-MJGV? Upgrade sigs.k8s.io/aws-load-balancer-controller to 2.8.2 or later.