{"answers":{"affected":"3 open source packages ship an affected version, including github.com/projectcapsule/capsule.","exploited":"There is no known exploitation of CVE-2026-61795 in the wild and no public exploit code.","fix":"Upgrade github.com/projectcapsule/capsule to 0.13.7 or later.","what":"CVE-2026-61795 is a medium-severity vulnerability in projectcapsule capsule, published on 18 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-61795 and fix it if it is affected.\n\nWhat it is: CVE-2026-61795 is a medium-severity vulnerability in projectcapsule capsule, published on 18 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-61795 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/projectcapsule/capsule (Go): affected from 0.13.0; fixed in 0.13.7\n- github.com/projectcapsule/capsule (Go): affected from 0.13.0; fixed in 0.13.7\n- github.com/projectcapsule/capsule (Go): affected from 0.13.0; fixed in 0.13.7\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-61795/ (Markdown: https://insights.sbomify.com/CVE-2026-61795/index.md)","id":"CVE-2026-61795","markdown":"https://insights.sbomify.com/CVE-2026-61795/index.md","name":"CVE-2026-61795","record":{"aliases":["GHSA-f94q-w3w8-cj67","GO-2026-6519"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes multi-tenancy framework","requires_auth":"high_privilege","summary":"A logic error in Capsule allows administrators to save invalid hostname regexes, causing subsequent Ingress operations to fail for affected tenants.","user_interaction":"not_required","vuln_class":"business_logic"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6.8,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-697","name":"Incorrect Comparison"}],"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.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Capsule: hostnameRegexHandler.OnUpdate validates stale (old) Tenant regex, allowing invalid AllowedHostnames regex to bypass webhook validation","id":"CVE-2026-61795","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"business_logic","year":"2026"},"n_packages":3,"n_references":4,"next":{"headline":"Wazuh cluster worker file sync allows arbitrary file write under /var/ossec (incomplete fix for CVE-2026-30893)","id":"CVE-2026-61800"},"packages":[{"ecosystem":"Go","fixed":["0.13.7"],"introduced":["0.13.0"],"last_affected":[],"package":"github.com/projectcapsule/capsule","purl":null,"source":"GHSA-f94q-w3w8-cj67"},{"ecosystem":"Go","fixed":["0.13.7"],"introduced":["0.13.0"],"last_affected":[],"package":"github.com/projectcapsule/capsule","purl":"pkg:golang/github.com/projectcapsule/capsule","source":"GHSA-f94q-w3w8-cj67"},{"ecosystem":"Go","fixed":["0.13.7"],"introduced":["0.13.0"],"last_affected":[],"package":"github.com/projectcapsule/capsule","purl":"pkg:golang/github.com/projectcapsule/capsule","source":"GO-2026-6519"}],"prev":{"headline":"Capsule: Malformed ForbiddenAnnotations.Regex can bypass Tenant validation and trigger namespace admission panic","id":"CVE-2026-61794"},"products":["capsule"],"published":"2026-09-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-09-21","vendors":["projectcapsule"]},"summary":"A logic error in Capsule allows administrators to save invalid hostname regexes, causing subsequent Ingress operations to fail for affected tenants.","url":"https://insights.sbomify.com/CVE-2026-61795/"}