{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56296 exists.","fix":"No fix has been published for CVE-2026-56296 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-56296 is a medium-severity vulnerability in Cap-go capgo, published on 11 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-56296 and fix it if it is affected.\n\nWhat it is: CVE-2026-56296 is a medium-severity vulnerability in Cap-go capgo, published on 11 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56296 exists.\n\nAffected product: Cap-go capgo. No package-level version data is available, so check the vendor advisory linked from the reference page.\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-56296/ (Markdown: https://insights.sbomify.com/CVE-2026-56296/index.md)","id":"CVE-2026-56296","markdown":"https://insights.sbomify.com/CVE-2026-56296/index.md","name":"CVE-2026-56296","record":{"aliases":["GHSA-fcmv-mqrc-fr3c","GHSA-fmm3-3qcg-85j6"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Cap-go update server","requires_auth":"none","summary":"Unauthenticated attackers can enumerate valid application IDs by observing distinct error messages from the transfer_app RPC endpoint.","user_interaction":"not_required","vuln_class":"information_disclosure"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[],"cvss":{"score":6.9,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-203","name":"Observable Discrepancy"}],"description":"Cap-go before 12.128.2 contains an information disclosure vulnerability in the public.transfer_app RPC function that returns distinct error messages for existing versus non-existing app IDs. Unauthenticated attackers can enumerate valid app IDs by observing error message differences when calling transfer_app with only the publishable API key.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Cap-go - App Existence Oracle via Unauthenticated transfer_app RPC","id":"CVE-2026-56296","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"information_disclosure","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"FreeRDP - Use-After-Free via Race Condition in DRDYNVC Channel Callback","id":"CVE-2026-56297"},"packages":[],"prev":{"headline":"Capgo - Policy Enforcement Bypass in Webhook Management Endpoints via Non-Expiring API Keys","id":"CVE-2026-56295"},"products":["capgo"],"published":"2026-07-11","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-13","vendors":["Cap-go"]},"summary":"Unauthenticated attackers can enumerate valid application IDs by observing distinct error messages from the transfer_app RPC endpoint.","url":"https://insights.sbomify.com/CVE-2026-56296/"}