{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-56355 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-56355 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-56355 is a low-severity authentication bypass vulnerability in GNU Savane, published on 20 Jun 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-56355 and fix it if it is affected.\n\nWhat it is: CVE-2026-56355 is a low-severity authentication bypass vulnerability in GNU Savane, published on 20 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-56355 in the wild and no public exploit code.\n\nAffected product: GNU Savane. 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-56355/ (Markdown: https://insights.sbomify.com/CVE-2026-56355/index.md)","id":"CVE-2026-56355","markdown":"https://insights.sbomify.com/CVE-2026-56355/index.md","name":"CVE-2026-56355","record":{"aliases":["GHSA-g7v6-x8xj-fvjm"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"GNU Savane","requires_auth":"none","summary":"Attackers can bypass authorization controls in GNU Savane by exploiting the use of untrusted data in the authentication process.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":3.7,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-696","name":"Incorrect Behavior Order"}],"description":"GNU Savannah Administration Savane through 3.17 uses untrusted data as part of authorization.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Auth bypass in Savane","id":"CVE-2026-56355","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"n8n - Stored Cross-Site Scripting in Chat Trigger Node Custom CSS Field","id":"CVE-2026-56356"},"packages":[],"prev":{"headline":"n8n - Cross-Site Scripting and Open Redirect in Form Node","id":"CVE-2026-56354"},"products":["Savane"],"published":"2026-06-20","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":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-22","vendors":["GNU"]},"summary":"Attackers can bypass authorization controls in GNU Savane by exploiting the use of untrusted data in the authentication process.","url":"https://insights.sbomify.com/CVE-2026-56355/"}