{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-133001 in the wild and no public exploit code.","exposure":"","fix":"No fix has been published for CVE-2026-133001 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-133001 is a medium-severity vulnerability in flowintel, published on 19 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-133001 and fix it if it is affected.\n\nWhat it is: CVE-2026-133001 is a medium-severity vulnerability in flowintel, published on 19 Nov 2026. \nExploitation: There is no known exploitation of CVE-2026-133001 in the wild and no public exploit code.\n\nAffected product: flowintel. 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-133001/ (Markdown: https://insights.sbomify.com/CVE-2026-133001/index.md)","id":"CVE-2026-133001","markdown":"https://insights.sbomify.com/CVE-2026-133001/index.md","name":"CVE-2026-133001","record":{"aliases":["GHSA-8hmx-g4j7-9cc3"],"analysis":null,"analysis_generated_by":null,"assigner":"CIRCL","component":null,"cpe":[{"criteria":[{"cpe":"cpe:2.3:a:flowintel:flowintel:*:*:*:*:*:*:*:*","source":"cna","version_end_including":"4.0.0"}],"n_criteria":1,"name":"Flowintel","product":"flowintel","vendor":"flowintel"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"}],"description":"FlowIntel contains an authorization flaw in its duplicate alert ingestion logic. When a duplicate alert is received and its content is updated, the ownership and visibility scope fields (owner user and owner organization) were not refreshed to reflect the connector's current scope. As a result, an alert that was originally created under a broader visibility scope retained that broader scope even after the connector's scope was narrowed or changed.\n\nThis means that users or organizations that should no longer have visibility into a given alert could continue to access it, because the stale ownership fields were never updated during the duplicate-update path. The issue affected all duplicate updates, including those involving alerts in terminal review states and those recovered from uniqueness conflicts.\n\nSecurity impact:\n- Unauthorized disclosure of security alert content to users or organizations outside the intended visibility scope.\n- Stale access persists indefinitely until the alert is independently re-scoped or deleted.\n\nAffected version: \u003c4.1.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":"FlowIntel Alert Visibility Scope Not Refreshed on Duplicate Ingestion","id":"CVE-2026-133001","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"main_cpe":null,"main_fixed":[],"main_package":null,"n_packages":0,"n_references":1,"n_vendor_status":0,"next":{"headline":"Gimp: gimp: uninitialized stack disclosure in xcf tile loader","id":"CVE-2026-133007"},"nickname":null,"packages":[],"prev":{"headline":"In JetBrains TeamCity before 2026.2 mute and unmute operations via XML-RPC could be attributed to other users","id":"CVE-2026-132996"},"products":["flowintel"],"published":"2026-11-19","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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","text_fixes":[],"updated":"2026-11-19","vendor_status":[],"vendors":["flowintel"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-133001/"}