{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-9371 exists.","fix":"No fix has been published for CVE-2026-9371 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-9371 is a medium-severity missing authorization vulnerability in ItzCrazyKns Vane, published on 24 May 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-9371 and fix it if it is affected.\n\nWhat it is: CVE-2026-9371 is a medium-severity missing authorization vulnerability in ItzCrazyKns Vane, published on 24 May 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-9371 exists.\n\nAffected product: ItzCrazyKns Vane. 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-9371/ (Markdown: https://insights.sbomify.com/CVE-2026-9371/index.md)","id":"CVE-2026-9371","markdown":"https://insights.sbomify.com/CVE-2026-9371/index.md","name":"CVE-2026-9371","record":{"aliases":["GHSA-wp4r-2xxm-f94x"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Vane API","requires_auth":"none","summary":"Attackers can access the Vane API without authentication, potentially reading or modifying data, requiring a patch to implement proper authentication.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":6.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"},{"id":"CWE-287","name":"Improper Authentication"}],"description":"A security vulnerability has been detected in ItzCrazyKns Vane up to 1.12.1. Affected by this issue is some unknown functionality of the file route.ts of the component API. The manipulation leads to missing authentication. The attack may be initiated remotely. The attack's complexity is rated as high. The exploitation is known to be difficult. The exploit has been disclosed publicly and may be used. It appears that basic authentication is planned.","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":"ItzCrazyKns Vane API route.ts missing authentication","id":"CVE-2026-9371","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":7,"next":{"headline":"ItzCrazyKns Vane Model Provider API route.ts server-side request forgery","id":"CVE-2026-9372"},"packages":[],"prev":{"headline":"ulisesbocchio jasypt-spring-boot Password Hash SimpleGCMConfig.java getSecretKeySaltGenerator hash predictable salt","id":"CVE-2026-9370"},"products":["Vane"],"published":"2026-05-24","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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-05-26","vendors":["ItzCrazyKns"]},"summary":"Attackers can access the Vane API without authentication, potentially reading or modifying data, requiring a patch to implement proper authentication.","url":"https://insights.sbomify.com/CVE-2026-9371/"}