{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119733 exists.","exposure":"","fix":"No fix has been published for CVE-2026-119733 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-119733 is a high-severity vulnerability in Petpooja Munshi, published on 2 Nov 2026."},"fix_prompt":"Check this codebase for CVE-2026-119733 and fix it if it is affected.\n\nWhat it is: CVE-2026-119733 is a high-severity vulnerability in Petpooja Munshi, published on 2 Nov 2026. \nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-119733 exists.\n\nAffected product: Petpooja Munshi. 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-119733/ (Markdown: https://insights.sbomify.com/CVE-2026-119733/index.md)","id":"CVE-2026-119733","markdown":"https://insights.sbomify.com/CVE-2026-119733/index.md","name":"CVE-2026-119733","record":{"aliases":["GHSA-jrw2-g2pp-rv96"],"analysis":null,"analysis_generated_by":null,"assigner":"VulnCheck","cpe":[],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"}],"description":"Munshi (by Petpooja) before 2026-07-07 contained a missing authorization vulnerability in its company deletion workflow at DELETE /api/companies/{company_id}, where the application fails to enforce the dedicated company_delete permission or verify company ownership. An authenticated invited sub-user with mere access to a company can exploit this flaw to perform a hard delete of the company record, causing irreversible loss of associated business data including invoices, configurations, and chat sessions.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Munshi Missing Authorization in Company Deletion API","id":"CVE-2026-119733","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Munshi IDOR via Purchase Inquiry Thread Endpoint","id":"CVE-2026-119734"},"nickname":null,"packages":[],"prev":{"headline":"Munshi Broken Object Level Authorization via Invoice Deletion API","id":"CVE-2026-119732"},"products":["Munshi"],"published":"2026-11-02","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-11-02","vendors":["Petpooja"]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-119733/"}