{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-85055 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-85055 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-85055 is a high-severity missing authorization vulnerability in twentyhq twenty, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-85055 and fix it if it is affected.\n\nWhat it is: CVE-2026-85055 is a high-severity missing authorization vulnerability in twentyhq twenty, published on 22 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-85055 in the wild and no public exploit code.\n\nAffected product: twentyhq twenty. 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-85055/ (Markdown: https://insights.sbomify.com/CVE-2026-85055/index.md)","id":"CVE-2026-85055","markdown":"https://insights.sbomify.com/CVE-2026-85055/index.md","name":"CVE-2026-85055","record":{"aliases":["GHSA-v93q-4jcx-7p9m"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Twenty CRM","requires_auth":"low_privilege","summary":"Attackers can bypass field-level read restrictions in Twenty CRM by using filter predicates to infer denied field values via boolean oracles.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-285","name":"Improper Authorization"},{"id":"CWE-200","name":"Exposure of Sensitive Information to an Unauthorized Actor"}],"description":"Twenty is an open-source CRM (customer relationship management) platform. Prior to 2.22.0, field-level read permission is enforced on selected output fields but not on GraphQL or REST filter predicates. A workspace member or API key with permission to read an object but not a particular field can reference that denied field in direct filters, relation filters, or persisted view filters. The resulting totalCount and row presence reveal whether guesses match the real column, forming a boolean/count oracle that can reconstruct denied field values for records exposed by the principal's row-level policy. This issue is fixed in version 2.22.0.","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":"Twenty: Field-level read bypass","id":"CVE-2026-85055","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"ZITADEL: MFA bypass via session reuse in Login V2","id":"CVE-2026-85056"},"packages":[],"prev":{"headline":"Code injection in Chrome","id":"CVE-2026-85053"},"products":["twenty"],"published":"2026-09-22","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-09-23","vendors":["twentyhq"]},"summary":"Attackers can bypass field-level read restrictions in Twenty CRM by using filter predicates to infer denied field values via boolean oracles.","url":"https://insights.sbomify.com/CVE-2026-85055/"}