{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-119663 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-119663 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119663 is a medium-severity vulnerability in wannabespace tamery, published on 30 Oct 2026."},"fix_prompt":"Check this codebase for CVE-2026-119663 and fix it if it is affected.\n\nWhat it is: CVE-2026-119663 is a medium-severity vulnerability in wannabespace tamery, published on 30 Oct 2026. \nExploitation: There is no known exploitation of CVE-2026-119663 in the wild and no public exploit code.\n\nAffected product: wannabespace tamery. 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-119663/ (Markdown: https://insights.sbomify.com/CVE-2026-119663/index.md)","id":"CVE-2026-119663","markdown":"https://insights.sbomify.com/CVE-2026-119663/index.md","name":"CVE-2026-119663","record":{"aliases":["GHSA-mf38-vc74-jfg4"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"Tamery (formerly Conar) 0.32.0 before 0.99.0 contains a broken authorization vulnerability in the cloud sync API connectionsResources.create handler that allows authenticated users to attach resources to other users' connections. Attackers owning one connection can include a victim's connectionId in a batch request to insert attacker-named resource rows listed by the victim's client.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Tamery (Conar) 0.32.0 before 0.99.0 Broken Authorization via connectionsResources.create","id":"CVE-2026-119663","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":6,"next":{"headline":"Tamery (Conar) 0.26.1 before 0.99.0 Authorization Bypass via chatsMessages.update","id":"CVE-2026-119664"},"nickname":null,"packages":[],"prev":{"headline":"Songloft 2.9.0 before 2.13.6 Hardcoded Admin Credentials in Embedded Backend","id":"CVE-2026-119662"},"products":["tamery"],"published":"2026-10-30","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-11-04","vendors":["wannabespace"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-119663/"}