CVE-2026-61795: projectcapsule capsule · Incorrect Comparison
Affects projectcapsule capsuleSource CVE Database V5
Not known to be exploited · CVSS 6.8 Medium : upgrade to 0.13.7 when convenient.
Data as of 2 Nov 2026, 22:58 UTC
- EPSS
- 0.5% chance of exploitation in 30 days – higher than 48% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.13.7
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Sep 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.
What to do
Upgrade capsule and projectcapsule/capsule to 0.13.7.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| projectcapsulecapsule | Affected
| Fixed in
|
GitHubprojectcapsule/capsulepkg:github/projectcapsule/capsuleOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Upgrade Capsule to version 0.13.7 or later, where this issue is fixed. Until then, administrators should carefully validate AllowedHostnames.Regex values to avoid malformed patterns. No other mitigations are specified.
Description
Capsule is a multi-tenancy and policy-based framework for Kubernetes. From 0.13.0 until 0.13.7, hostnameRegexHandler.OnUpdate in internal/webhook/tenant/validation/hostname_regex.go reverses the new and old Tenant parameters and validates the previous AllowedHostnames.Regex instead of the submitted value. A cluster administrator can therefore store a malformed AllowedHostnames.Regex after the webhook accepts the update based on stale valid state. Subsequent Ingress creation or update reaches validate_hostnames.go, which evaluates the malformed pattern, ignores the regular-expression error, and treats every hostname as unmatched, blocking Ingress operations for the affected tenant until an administrator repairs the Tenant configuration. This issue is fixed in version 0.13.7.
References
- github.com/projectcapsule/capsule/security/advisories/GHSA-f94q-w3w8-cj67 (opens in a new tab)
- github.com/projectcapsule/capsule/pull/1983 (opens in a new tab)
- github.com/projectcapsule/capsule/commit/8d89d6865df6f41c7faa22fc9e807a57b01bfd0e (opens in a new tab)
- github.com/projectcapsule/capsule/releases/tag/v0.13.7 (opens in a new tab)