CVE-2026-61794

MEDIUMPre-NVD 6.86.8
EchelonGraph scoreMEDIUM confidence

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

This medium-severity CVE scores 6.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6% (48th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 4.9 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-09-18) is not newer than that change (2026-09-24), so it does not.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, GitHub Security Advisory, a secondary CVSS source
Trending — 4 sources updated this weekElevated

Also known asEUVD-2026-83055 (ENISA EUVD) · GHSA-gxjc-74v5-3vx3 (GitHub Security Advisories) · GO-2026-6521 (OSV.dev)Source: ENISA EUVD

6.8EG
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.6%CVSS: 6.8Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

Capsule is a multi-tenancy and policy-based framework for Kubernetes. From 0.13.0 until 0.13.7, the Tenant update validation in internal/webhook/tenant/validation/forbidden_annotations_regex.go compiles ForbiddenLabels.Regex for both the labels and annotations checks instead of validating ForbiddenAnnotations.Regex. An administrator who can update a Tenant can therefore persist a malformed ForbiddenAnnotations.Regex while leaving the labels expression valid. Namespace creation or update later passes the stored expression through pkg/api/forbidden_list.go, where regexp.MustCompile can panic during forbidden metadata validation and deny namespace operations for the affected tenant. This issue is fixed in version 0.13.7.

CVSS v3
6.8
EG Score
6.8MEDIUMmedium confidence
EG Risk
47
EG Risk 47/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)
Severity68% × 45%
Impact severity (EG Severity): CVSS 6.8 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.6%
EPSS %ILE
48th
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.8): severity, escalated by confirmed exploitation. This CVE's 6.8 is its impact severity (EG Severity), not escalated.

EG Severity
6.8 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.6% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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

September 18, 2026

Last Modified

September 24, 2026

Advisory Details (4)

Auto-updated Sep 18, 2026
Patch available. Sources: github, github_pr, github_commit, github_release.
GitHub release Patch Available

v0.13.7

Patch available: projectcapsule/capsule v0.13.7

https://github.com/projectcapsule/capsule/releases/tag/v0.13.7
GitHub commit

commit 8d89d6865df6 (projectcapsule/capsule)

Fix landed in projectcapsule/capsule commit 8d89d6865df6 — awaiting tagged release

https://github.com/projectcapsule/capsule/commit/8d89d6865df6f41c7faa22fc9e807a57b01bfd0e
GitHub pull request

fix(sec): corrects validation for regex objects (hostname and forbidden

Fix merged in projectcapsule/capsule PR #1983 on 2026-06-24 — awaiting tagged release

https://github.com/projectcapsule/capsule/pull/1983
GitHub advisoryMentions a patch (unverified)

Malformed ForbiddenAnnotations.Regex can bypass Tenant validation and trigger namespace admission panic · Advisory · projectcapsule/capsule · GitHub

https://github.com/projectcapsule/capsule/security/advisories/GHSA-gxjc-74v5-3vx3

Vendor Advisories for CVE-2026-61794(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
gogithub.com/projectcapsule/capsule @ 0.13.7 (fixes >= 0.13.0, < 0.13.7)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFix by version rangeDependents
github.com/projectcapsule/capsule—
  • 0.13.0 up to 0.13.7: fixed in 0.13.7
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 47× 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 it from the CNA feed. 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). Most recent first.

  1. 2026-11-01 16:35 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  2. 2026-11-01 07:41 UTCGHSA enrichmentGHSA-gxjc-74v5-3vx3 · GitHub severity MODERATE · GitHub CVSS 4.9
  3. 2026-11-01 07:41 UTCEG score recompute
  4. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  6. 2026-10-30 09:25 UTCOSV refresh
  7. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.6% · 48th percentile
  8. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  9. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  10. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  11. 2026-10-25 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  12. 2026-10-25 14:14 UTCEG score recompute
  13. 2026-10-24 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  14. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  15. 2026-10-22 19:56 UTCEG score recompute
  16. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  17. 2026-10-21 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  18. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  19. 2026-10-19 16:32 UTCEPSS rescoreEPSS 0.6% · 47th percentile
  20. 2026-10-18 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  21. 2026-10-18 03:25 UTCEG score recompute
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  23. 2026-10-16 16:43 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  24. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  25. 2026-10-14 16:33 UTCEPSS rescoreEPSS 0.6% · 46th percentile
Show 46 more
  1. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  2. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  3. 2026-10-12 15:50 UTCEG score recompute
  4. 2026-10-11 19:34 UTCEG score recompute
  5. 2026-10-11 16:49 UTCEG score recompute
  6. 2026-10-11 14:11 UTCEG score recompute
  7. 2026-10-11 13:49 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  8. 2026-10-10 23:14 UTCEG score recompute
  9. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  10. 2026-10-09 21:44 UTCEG score recompute
  11. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  12. 2026-10-08 20:14 UTCEG score recompute
  13. 2026-10-08 17:13 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  14. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  15. 2026-10-07 18:01 UTCEG score recompute
  16. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  17. 2026-10-06 14:28 UTCEG score recompute
  18. 2026-10-05 17:43 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  19. 2026-10-05 12:59 UTCEG score recompute
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  21. 2026-10-04 11:29 UTCEG score recompute
  22. 2026-10-03 14:26 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  23. 2026-10-03 09:59 UTCEG score recompute
  24. 2026-10-02 17:56 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  25. 2026-10-02 08:14 UTCEG score recompute
  26. 2026-10-01 19:50 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  27. 2026-10-01 06:40 UTCEG score recompute
  28. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  29. 2026-09-30 05:11 UTCEG score recompute
  30. 2026-09-29 03:41 UTCEG score recompute
  31. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  32. 2026-09-28 02:10 UTCEG score recompute
  33. 2026-09-27 00:37 UTCEG score recompute
  34. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  35. 2026-09-24 18:19 UTCEG score recompute
  36. 2026-09-23 17:54 UTCEPSS rescoreEPSS 0.3% · 26th percentile
  37. 2026-09-23 16:49 UTCEG score recompute
  38. 2026-09-22 15:20 UTCEG score recompute
  39. 2026-09-22 15:01 UTCEG score recompute
  40. 2026-09-21 21:54 UTCEG score recompute
  41. 2026-09-20 20:25 UTCEG score recompute
  42. 2026-09-20 20:16 UTCEPSS rescoreEPSS 0.3% · 25th percentile
  43. 2026-09-19 18:55 UTCEG score recompute
  44. 2026-09-18 17:26 UTCEG score recompute
  45. 2026-09-18 16:29 UTCEG score recomputeFirst assessed: 6.8 MEDIUM
  46. 2026-09-18 16:29 UTCMITRE cvelistV5first tracked

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-61794?
CVE-2026-61794 is a medium-severity vulnerability; its CVE record was published on September 18, 2026. Capsule is a multi-tenancy and policy-based framework for Kubernetes. From 0.13.0 until 0.13.7, the Tenant update validation in internal/webhook/tenant/validation/forbidden_annotations_regex.go compiles ForbiddenLabels.Regex for both the labels and annotations checks instead of validating…
When was the CVE record for CVE-2026-61794 published?
The CVE record for CVE-2026-61794 was published on September 18, 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 September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-61794 actively exploited?
CVE-2026-61794 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.6% probability of exploitation in the next 30 days (48th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-61794?
CVE-2026-61794 has a CVSS base score of 6.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-61794?
A fix for CVE-2026-61794 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-61794 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-61794

Explore →

Is Your Infrastructure Affected by CVE-2026-61794?

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

Book a Demo →Browse All CVEs