CVE-2026-119731

waiting for further signalsZero needs more public information before it can validate it.

GHSA-hcw8-82qq-9mcv ↗EUVD-2026-115362 ↗

no check availablenot proven exploitable
cve.orgpublic pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).kevAttacks confirmed in the real world.
Petpooja Munshi <= 2026-06-30
ETK-2026-3320Zero's internal tracking ID, independent of the CVE number., permanent identifier
3h 26msince last run
26mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = trigger signal
trigger signal (cve.org) +0hwaiting for further signals+4h06m
0
+2h
+6h
+8h
+10h
+12h

description

Munshi releases before 2026-06-30 do not adequately validate subscription payment webhook requests. A remote unauthenticated party could falsely mark a subscription as paid and obtain paid access if they can reference a relevant payment order.

mitigation

Upgrade Munshi to version 2026-06-30 or later. Also require validated payment-provider signatures and confirm payment status with the provider before activating subscriptions.

check
no
exploit
no
automationDeterministic: a check that runs on its own, the same request on every target. Contextual: an agentic technique that needs to be applied per target, for bugs that depend on contextual flows.
contextual
auth requiredWhether an attacker needs an account first, based on the CVSS vector's Privileges Required.
no
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
–
agent run time
26m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-11-02 18:54Z
Δ to public pocExploit code has been published by someone. Source signals can also carry a PoC (Proof of Concept).
–
Δ to kevAttacks confirmed in the real world.
–

outcome

Contextual, not validated: no deterministic check could cover this one, and no technique passed our review.

source signals

Public signals that triggered or updated the pipeline. These are inputs for the deltas above.

  1. 2026-11-02 18:54Z
    ghsa: trigger signal, started the run
  2. 2026-11-02 18:54Z

this entry in the feed

GET /api/v1/feed/CVE-2026-119731

{
  "etk_id": "ETK-2026-3320",
  "cve_id": "CVE-2026-119731",
  "display_id": "CVE-2026-119731",
  "ghsa_id": "GHSA-hcw8-82qq-9mcv",
  "euvd_id": "EUVD-2026-115362",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Unauthenticated payment webhook in Petpooja Munshi",
  "summary": "Munshi releases before 2026-06-30 do not adequately validate subscription payment webhook requests. A remote unauthenticated party could falsely mark a subscription as paid and obtain paid access if they can reference a relevant payment order.",
  "mitigation": "Upgrade Munshi to version 2026-06-30 or later. Also require validated payment-provider signatures and confirm payment status with the provider before activating subscriptions.",
  "vendor": "Petpooja",
  "product": "Munshi",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        ">= 0, <= 2026-06-30"
      ],
      "ecosystem": null,
      "fixed_versions": [],
      "package_name": "Munshi",
      "purl": null
    }
  ],
  "cwes": null,
  "cvss_score": 7.5,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N",
  "epss_score": null,
  "epss_percentile": null,
  "epss_asof": null,
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 25.819854516666666,
  "t0_at": "2026-11-02T18:54:28.988000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-11-02T18:54:28.988000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-11-02T18:54:28.988000+00:00",
      "url": "https://github.com/advisories/GHSA-hcw8-82qq-9mcv"
    }
  }
}

published 2026-11-02 22:34Z
last change 2026-11-03 00:30Z

Need the technical details behind an entry?

Every entry here shows what we attempted and when. The technical details, the generated exploit that fired it and the evidence behind the verdict are not public. Tell us about your use case and we’ll get back to you about extended API access.