CVE-2026-54462

MEDIUMPre-NVD 6.56.5
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 6.5 from GitHub Security Advisory (severity: MODERATE) published 2026-10-27. The CNA's CVSS baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Elevated

Also known asEUVD-2026-111135 (ENISA EUVD) · GHSA-j8gc-gxpv-w8rg (GitHub Security Advisories) · GO-2026-6880 (OSV.dev)Source: ENISA EUVD

6.5EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 6.5Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Knative pkg provides common packages shared across Knative repositories. Prior to 0.0.0-20260531000007-52dbd5ece63f, the knative.dev/pkg/webhook admissionHandler in webhook/admission.go decodes an attacker-supplied AdmissionReview through json.NewDecoder(io.TeeReader(r.Body, &bodyBuffer)) under an http.HandlerFunc without an http.MaxBytesReader or equivalent body-size limit. A pod-network client can send one oversized POST to an admission webhook, causing the decoder and bodyBuffer to retain amplified copies of the request until the controller pod exhausts memory and is OOM-killed. Every downstream consumer using the shared webhook server inherits the vulnerable behavior, including Knative, Tekton, KEDA, Sigstore policy-controller, and Kpack. For consumers configured with failurePolicy=Fail, loss of the controller can interrupt admission; with failurePolicy=Ignore, the affected webhook is unavailable while other admissions continue. This issue is fixed in version 0.0.0-20260531000007-52dbd5ece63f.

CVSS v3
6.5
EG Score
6.5MEDIUMhigh confidence
EG Risk
45
EG Risk 45/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity65% × 45%
Impact severity (EG Severity): CVSS 6.5 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
32nd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (6.5): severity, escalated by confirmed exploitation. This CVE's 6.5 is its impact severity (EG Severity), not escalated.

EG Severity
6.5 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-02). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Track* at high (mission-essential systems).CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

October 27, 2026

Last Modified

November 2, 2026

Advisory Details (3)

Auto-updated Nov 2, 2026
🔬 Proof of concept available. Patch available. Sources: github, github_pr, github_commit.
GitHub commit

commit 52dbd5ece63f (knative/pkg)

Fix landed in knative/pkg commit 52dbd5ece63f — awaiting tagged release

https://github.com/knative/pkg/commit/52dbd5ece63fe6d2d340ecbebec160550f460818
GitHub pull request

[release-1.22] Limit the webhook request body size

Fix merged in knative/pkg PR #3363 on 2026-05-31 — awaiting tagged release

https://github.com/knative/pkg/pull/3363
GitHub advisoryMentions a patch (unverified)🟡 PoC Available

Unbounded admission webhook body in knative.dev/pkg/webhook/admission.go: json.NewDecoder(io.TeeReader(r.Body, ...)) reads attacker-supplied AdmissionReview body without http.MaxBytesReader; affects every downstream consumer (Knative, Tekton, KEDA, Sigstore policy-controller, …) with no API change required to fix at the library level (same shape as CVE-2026-24514 and GHSA-9539-c3xr-w9vm) · Advisory · knative/pkg · GitHub

https://github.com/knative/pkg/security/advisories/GHSA-2hw4-c9m4-f2fj

Vendor Advisories for CVE-2026-54462(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
knative.dev/pkg—
  • every version up to 0.0.0-20260531000007-52dbd5ece63f: fixed in 0.0.0-20260531000007-52dbd5ece63f
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 22× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

  1. 2026-11-13 16:53 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  2. 2026-11-12 16:34 UTCEPSS rescoreEPSS 0.4% · 32nd percentile
  3. 2026-11-11 16:40 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  4. 2026-11-10 16:44 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  5. 2026-11-09 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  6. 2026-11-08 16:40 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  7. 2026-11-07 16:39 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  8. 2026-11-06 16:38 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  9. 2026-11-05 16:38 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  10. 2026-11-04 16:35 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  11. 2026-11-03 16:48 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  12. 2026-11-02 20:26 UTCEchelonGraph re-scored
  13. 2026-11-02 20:26 UTCGHSA enrichmentGHSA-j8gc-gxpv-w8rg · GitHub severity MODERATE · GitHub CVSS 6.5
  14. 2026-11-02 19:33 UTCEchelonGraph re-scored
  15. 2026-11-02 19:33 UTCGHSA enrichmentGHSA-j8gc-gxpv-w8rg · GitHub severity MODERATE · GitHub CVSS 6.5
  16. 2026-11-02 16:45 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  17. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  18. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  19. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  20. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  21. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 31st percentile
  22. 2026-10-28 15:26 UTCEchelonGraph re-scored
  23. 2026-10-28 15:26 UTCGHSA enrichmentGHSA-j8gc-gxpv-w8rg · GitHub CVSS 6.5
  24. 2026-10-27 17:26 UTCEchelonGraph re-scored
  25. 2026-10-27 17:01 UTCENISA EUVD ID recordedEUVD-2026-111135 · Source: ENISA EUVD
Show 2 more
  1. 2026-10-27 16:27 UTCEchelonGraph re-scoredFirst assessed: 6.5 MEDIUM
  2. 2026-10-27 16:24 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-54462?
CVE-2026-54462 is a medium-severity vulnerability; its CVE record was published on October 27, 2026. Knative pkg provides common packages shared across Knative repositories. Prior to 0.0.0-20260531000007-52dbd5ece63f, the knative.dev/pkg/webhook admissionHandler in webhook/admission.go decodes an attacker-supplied AdmissionReview through json.NewDecoder(io.TeeReader(r.Body, &bodyBuffer)) under an…
When was the CVE record for CVE-2026-54462 published?
The CVE record for CVE-2026-54462 was published on October 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 2, 2026; the record at its source may have been updated since.
Is CVE-2026-54462 actively exploited?
CVE-2026-54462 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (32nd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-54462?
CVE-2026-54462 has a CVSS base score of 6.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-54462?
A fix for CVE-2026-54462 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-54462 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-54462

Explore →

Is Your Infrastructure Affected by CVE-2026-54462?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs