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

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

Summary

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

Original description

The description as published by the source.

Summary

A validation bug in internal/webhook/tenant/validation/forbidden_annotations_regex.go allows an invalid ForbiddenAnnotations.Regex value to bypass Tenant admission on update. The webhook compiles ForbiddenLabels.Regex for both labels and annotations, so a malformed annotations regex can be persisted. Once stored, namespace admission later evaluates the bad regex through pkg/api/forbidden_list.go, where regexp.MustCompile can panic and cause admission failure.

Details

In internal/webhook/tenant/validation/forbidden_annotations_regex.go, OnUpdate validates the new Tenant object, but the loop compiles tnt.Spec.NamespaceOptions.ForbiddenLabels.Regex for both labels and annotations. That means an invalid ForbiddenAnnotations.Regex is never validated if ForbiddenLabels.Regex is valid.

Relevant paths:

  • internal/webhook/tenant/validation/forbidden_annotations_regex.go
  • internal/webhook/namespace/validation/user_metadata.go
  • pkg/api/forbidden_list.go

Namespace admission later calls api.ValidateForbidden(...), and ForbiddenListSpec.RegexMatch() uses regexp.MustCompile(in.Regex). If the malformed regex is present in the Tenant spec, any namespace request that reaches this check can panic or fail hard, causing denial of service for namespace operations in the affected tenant.

PoC

  1. Update a Tenant so that:
    • spec.namespaceOptions.forbiddenLabels.regex is valid
    • spec.namespaceOptions.forbiddenAnnotations.regex is m…

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-61794 has been found in github.com/projectcapsule/capsule.
Attackers can target a specific entry point like ForbiddenAnnotations.Regex 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-61794" on the vendor's site.

CVE-2026-61794 (github.com/projectcapsule/capsule) — CWE-20 / CVSS v3 6.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: ForbiddenAnnotations.Regex / ForbiddenLabels.Regex / regexp.MustCompile / OnUpdate
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-20) exists in github.com/projectcapsule/capsule. Attackers reach the vulnerable code path via ForbiddenAnnotations.Regex.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/projectcapsule/capsule. Attack surface: ForbiddenAnnotations.Regex / ForbiddenLabels.Regex / regexp.MustCompile / OnUpdate.

🔥 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