CVE-2026-61795: CWE-697: Incorrect Comparison in projectcapsule capsule
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.
AI Analysis
Technical Summary
Capsule versions 0.13.0 to 0.13.6 contain a flaw in the hostnameRegexHandler.OnUpdate function where the new and old Tenant parameters are reversed, causing validation to be performed on the previous AllowedHostnames.Regex rather than the submitted one. This allows a cluster administrator to inadvertently store a malformed regex pattern. When subsequent Ingress resources are created or updated, the malformed regex is evaluated but errors are ignored, resulting in all hostnames being treated as unmatched. This effectively blocks Ingress operations for the affected tenant until the Tenant configuration is manually corrected. The vulnerability is resolved in Capsule version 0.13.7.
Potential Impact
The vulnerability does not impact confidentiality or integrity but causes a denial of service (availability impact) by blocking Ingress creation or updates for tenants with malformed AllowedHostnames.Regex patterns. This disruption persists until an administrator repairs the Tenant configuration. There are no known exploits in the wild.
Mitigation Recommendations
Upgrade Capsule to version 0.13.7 or later, where this issue is fixed. Until the upgrade, administrators should carefully validate AllowedHostnames.Regex patterns to avoid malformed entries and be prepared to manually repair Tenant configurations if Ingress operations are blocked.
CVE-2026-61795: CWE-697: Incorrect Comparison in projectcapsule capsule
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.
CVSS v3.1
Score 6.8medium
Affected software
projectcapsule
capsule
pkg:github/projectcapsule/capsuleRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
Capsule versions 0.13.0 to 0.13.6 contain a flaw in the hostnameRegexHandler.OnUpdate function where the new and old Tenant parameters are reversed, causing validation to be performed on the previous AllowedHostnames.Regex rather than the submitted one. This allows a cluster administrator to inadvertently store a malformed regex pattern. When subsequent Ingress resources are created or updated, the malformed regex is evaluated but errors are ignored, resulting in all hostnames being treated as unmatched. This effectively blocks Ingress operations for the affected tenant until the Tenant configuration is manually corrected. The vulnerability is resolved in Capsule version 0.13.7.
Potential Impact
The vulnerability does not impact confidentiality or integrity but causes a denial of service (availability impact) by blocking Ingress creation or updates for tenants with malformed AllowedHostnames.Regex patterns. This disruption persists until an administrator repairs the Tenant configuration. There are no known exploits in the wild.
Mitigation Recommendations
Upgrade Capsule to version 0.13.7 or later, where this issue is fixed. Until the upgrade, administrators should carefully validate AllowedHostnames.Regex patterns to avoid malformed entries and be prepared to manually repair Tenant configurations if Ingress operations are blocked.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-10T20:06:05.617Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aad6b0a55bf5e2cf541929d
Added to database: 09/18/2026, 16:47:06 UTC
Last enriched: 09/18/2026, 17:01:52 UTC
Last updated: 09/18/2026, 22:12:51 UTC
Views: 8
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.