Advisory record · GO-2024-3075

CVE-2024-7646 in github.com/kubernetes/ingress-nginx

CVSS 8.8 HighCriticalEPSS 0.27 · 98th percentile

Critical, because:

  • CVSS score 8.8 (7.0 or more) and EPSS 0.27 (0.1 or more): a high score and a real chance of exploitation in the next 30 days.

How we decide what’s critical

Published by OSV at 19 Aug 2024, 17:26 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/kubernetes/ingress-nginxGoall versionsNo fixed version yet
Identifiers
GO-2024-3075 · CVE-2024-7646
Weakness (CWE)
CWE-20
Tags
Published
19 Aug 2024
Updated
20 May 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Versions of github.com/kubernetes/ingress-nginx before v1.11.2 are affected by CVE-2024-7646, though the structured record lists no fixed version. The source gives few details on the attack conditions or impact. Upgrade to v1.11.2 or later.

Written 7 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
8.8 High 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H CNA (kubernetes)
  • CISA KEV Not listed.
  • EPSS 0.27, the 98th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 15:08 UTC First seen by agentprime
  2. 31 Oct 2026, 15:08 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.