Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-61795 medium CVSS 6.8

Vulnerability in github.com/projectcapsule/capsule (CVE-2026-61795)

Summary

Vulnerability in github.com/projectcapsule/capsule (CVE-2026-61795). Risk of unauthorized operations or information disclosure. Exploitable via hostnameRegexHandler.OnUpdate. Mitigation: upgrade to 0.13.7 or later.

Original description

The description as published by the source.

Summary

A parameter order bug in internal/webhook/tenant/validation/hostname_regex.go causes the hostnameRegexHandler.OnUpdate webhook to validate the old Tenant object's AllowedHostnames.Regex instead of the new one being submitted. This allows an invalid (malformed) regex to bypass admission validation and be persisted to etcd, causing a Denial of Service for all Ingress operations within the affected tenant.

Details

The TypedHandler[T] interface defines OnUpdate as:

// handlers.go
OnUpdate(c client.Client, reader client.Reader, obj T, old T, decoder admission.Decoder, recorder events.EventRecorder) Func
//                                               ^^^ NEW  ^^^ OLD

The dispatcher in handler.go:93 calls:

hndl.OnUpdate(c, reader, tnt, old, decoder, recorder)
//                        ^^^ NEW  ^^^ OLD

However, hostnameRegexHandler.OnUpdate in hostname_regex.go declares its parameters in reversed order:

// hostname_regex.go (BUGGY)
func (h *hostnameRegexHandler) OnUpdate(
    _ client.Client,
    _ client.Reader,
    old *capsulev1beta2.Tenant,   // ← receives NEW tenant (mislabeled as old)
    tnt *capsulev1beta2.Tenant,   // ← receives OLD tenant (mislabeled as tnt)
    ...
) handlers.Func {
    return func(...) *admission.Response {
        if err := h.validate(tnt, req); err != nil { // ← validates OLD, not NEW
            return err
        }
        return nil
    }
}

All 11 other handlers in th…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-61795 has been found in github.com/projectcapsule/capsule.
Attackers can target a specific entry point like hostnameRegexHandler.OnUpdate over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.8/10.
What to do: upgrade github.com/projectcapsule/capsule to 0.13.7 or later.
If unsure, ask your IT team or search "github.com/projectcapsule/capsule CVE-2026-61795" on the vendor's site.

CVE-2026-61795 (github.com/projectcapsule/capsule) — CWE-697 / CVSS v3 6.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: hostnameRegexHandler.OnUpdate / AllowedHostnames.Regex / OnUpdate / hostname_regex.go
Patched: 0.13.7 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-697) exists in github.com/projectcapsule/capsule. Attackers reach the vulnerable code path via hostnameRegexHandler.OnUpdate.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/projectcapsule/capsule. Attack surface: hostnameRegexHandler.OnUpdate / AllowedHostnames.Regex / OnUpdate / hostname_regex.go.

🔥 Severity

Severity: Medium (CVSS 6.8/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.13.7.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/projectcapsule/capsule' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/projectcapsule/capsule' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/projectcapsule/capsule を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade github.com/projectcapsule/capsule to 0.13.7

    ステージング環境で 0.13.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/projectcapsule/capsule
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.13.7"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details