---
id: "CVE-2026-119732"
kind: "vulnerability"
aliases: ["CVE-2026-119732"]
title: "Munshi (Petpooja) lets invited sub-users delete the tenant owner's invoices"
severity: "high"
cvss: 7.1
epss: null
exploited: false
status: "open"
category: "other"
products: [{"name": "Munshi", "fixed": [], "affected": "<= 2026-07-28", "ecosystem": "vendor"}]
ecosystems: []
tags: ["accounting", "authorization", "munshi", "other", "petpooja", "restaurant-billing", "saas"]
not_affected_if: ["no-sub-users", "owner-only-accounts"]
published_at: "2026-11-02T19:18:01+00:00"
first_seen_at: "2026-11-02T19:24:39+00:00"
updated_at: "2026-11-02T19:27:41+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-119732", "first_seen_at": "2026-11-02T19:24:39+00:00"}, {"source": "analyst", "url": null, "first_seen_at": "2026-11-02T19:27:41+00:00"}]
---

# Munshi (Petpooja) lets invited sub-users delete the tenant owner's invoices

Munshi by Petpooja, a hosted invoice/accounting product, lets an authenticated sub-user delete invoices owned by the tenant owner through DELETE /api/invoice/{invoice_id} and POST /api/invoices/bulk-delete. VulnCheck says the endpoints verify only tenant membership, not ownership or permission. Credit: Vyom Nagpal.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- vendor:Munshi affected <= 2026-07-28 fixed ?

## How to check

- Confirm whether your organisation uses Munshi by Petpooja (gomunshi.ai) and whether any invited sub-users exist in your tenant.
- If so, ask Petpooja (munshisupport@petpooja.com) whether the invoice-delete authorization fix is deployed to your tenant; the sources give only the 2026-07-28 cutoff and no version.
- Until confirmed, remove sub-user access you do not need and keep exports of your invoices.
- Also check the related company-delete flaw (DELETE /api/companies/{company_id}), which the researcher reports as fixed.

## Timeline

- 2026-11-02T19:24:39+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-119732
- 2026-11-02T19:27:41+00:00 analyst — VulnCheck advisory read: affected 'Munshi <= 2026-07-28', no fixed version/vendor advisory found. Triage's 'restaurant billing' looks wrong: Munshi is an AI accounting agent for Tally (gomunshi.ai); title corrected, tags adjusted. Sibling company-delete flaw per researcher blog, fixed, CVE unassigned. Nothing verified: no vendor primary source. No exploitation or PoC seen; no social search done.

## Documents

- [advisory] Third-party advisory: www.vulncheck.com https://www.vulncheck.com/advisories/munshi-broken-object-level-authorization-via-invoice-deletion-api
- [describes] Munshi product page (AI agent for Tally) https://gomunshi.ai/
- [mentions] A Sub-User Could Delete a Company in Munshi (researcher write-up, sibling issue) https://medium.com/@TheWildEye/a-sub-user-could-delete-a-company-in-munshi-94bf92476e5c

## From the sources

Munshi (by Petpooja) before 2026-07-28 contained a broken object level authorization vulnerability that allows authenticated sub-users to delete invoices belonging to the tenant owner by exploiting the DELETE /api/invoice/{invoice_id} and POST /api/invoices/bulk-delete endpoints, which only verify tenant membership without enforcing object-level ownership or permission checks. Attackers can invoke single or bulk deletion requests with arbitrary invoice identifiers to delete invoices they do not own, resulting in unauthorized data loss.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_