Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-61672 high CVSS 7.1

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

Summary

Vulnerability in github.com/projectcapsule/capsule (CVE-2026-61672). Data can be tampered with by attackers. Exploitable via forbiddenAnnotations. Mitigation: upgrade to 0.13.7 or later.

Original description

The description as published by the source.

Summary

Capsule lets a cluster administrator forbid specific metadata keys that tenant owners must not place on their own resources: Tenant.spec.namespaceOptions.forbiddenLabels / forbiddenAnnotations (namespaces), Tenant.spec.serviceOptions.forbiddenLabels / forbiddenAnnotations (Services), and the cluster-wide forbidden worker-node labels/annotations. These lists are an isolation control — they exist to stop a tenant owner from setting metadata that other controllers or admission plugins key on (Pod Security Admission labels, kubernetes.io/metadata.name, LoadBalancer/externalIP service annotations, scheduler annotations, vendor labels that grant network reach, etc.). The validating webhooks enforce them through api.ValidateForbidden, which calls ForbiddenListSpec.ExactMatch(key) for every key the tenant submits.

ExactMatch is broken. It sorts the denied list case-insensitively (sort.SliceStable with a strings.ToLower comparator) and then performs a byte-order binary search (sort.SearchStrings) over the result. sort.SearchStrings is only correct on a slice sorted in plain byte-ascending order. Whenever the denied list contains an entry whose case-insensitive position differs from its byte position — which happens any time the list mixes a capitalised key with lowercase keys, because ASCII uppercase letters (0x41–0x5A) sort before lowercase (0x61–0x7A) by byte but are interleaved by ToLower — the binary search lands on the wrong index…

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-61672 has been found in github.com/projectcapsule/capsule.
Attackers can target a specific entry point like forbiddenAnnotations over the network to misuse the product.
Data can be tampered with by attackers. CVSS score: 7.1/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-61672" on the vendor's site.

CVE-2026-61672 (github.com/projectcapsule/capsule) — CWE-697 / CVSS v3 7.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: forbiddenAnnotations / api.ValidateForbidden / ExactMatch / sort.SliceStable
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 forbiddenAnnotations.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/projectcapsule/capsule. Attack surface: forbiddenAnnotations / api.ValidateForbidden / ExactMatch / sort.SliceStable.

🔥 Severity

Severity: High (CVSS 7.1/10). Data can be tampered with by attackers.

🔧 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