CVE-2026-61726

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

GHSA-wjf3-fq5w-7j7w ↗EUVD-2026-103144 ↗

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.
TandoorRecipes recipes <= 2.6.11
fixed in >2.6.11
CWE-284 Improper Access Control
ETK-2026-1811Zero's internal tracking ID, independent of the CVE number., permanent identifier
4d 19h 03msince last run
16mAI analysisAnalysis: how long the AI spent reversing this signal.
timeline
0 = cve.org publication
trigger signal (cve.org) +0hwaiting for further signals+2h07m
0
+4h
+6h
+8h
+10h
+12h

description

Tandoor Recipes before 2.6.12 does not consistently enforce private-recipe ownership or sharing rules for recipe-step API requests. An authenticated member with read and write API scope in the same Space may view or modify another member's private recipe instructions.

mitigation

Upgrade the recipes package to version 2.6.12 or later.

fixed in >2.6.11

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.
yes, low privileges
EPSSEstimate of the chance this CVE is exploited in the next 30 days. Refreshed daily.
0.23%13th percentile
agent run time
16m
cve.org record, t = 0The moment cve.org publishes the CVE in full.
2026-10-16 19:19Z
Δ 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: an exploit technique exists, but no deterministic check could cover this one.

source signals

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

  1. 2026-10-16 19:19Z
    cve_org: trigger signal, started the run

this entry in the feed

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

{
  "etk_id": "ETK-2026-1811",
  "cve_id": "CVE-2026-61726",
  "display_id": "CVE-2026-61726",
  "ghsa_id": "GHSA-wjf3-fq5w-7j7w",
  "euvd_id": "EUVD-2026-103144",
  "status": "published",
  "anchor_state": "anchored",
  "title": "Private recipe authorization bypass in Tandoor Recipes",
  "summary": "Tandoor Recipes before 2.6.12 does not consistently enforce private-recipe ownership or sharing rules for recipe-step API requests. An authenticated member with read and write API scope in the same Space may view or modify another member's private recipe instructions.",
  "mitigation": "Upgrade the recipes package to version 2.6.12 or later.",
  "vendor": "TandoorRecipes",
  "product": "recipes",
  "affected": [
    {
      "affected_notes": [],
      "affected_ranges": [
        "<= 2.6.11"
      ],
      "ecosystem": null,
      "fixed_versions": [
        ">2.6.11"
      ],
      "package_name": "TandoorRecipes/recipes",
      "purl": null
    }
  ],
  "cwes": [
    284
  ],
  "cvss_score": 8.1,
  "cvss_src": "cna_vendor",
  "cvss_vector": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N",
  "epss_score": 0.0023,
  "epss_percentile": 0.1304,
  "epss_asof": "2026-10-20",
  "automation": "contextual",
  "check": false,
  "check_confidence_basis": null,
  "exploit": false,
  "pipeline_minutes": 16.472978516666668,
  "t0_at": "2026-10-16T19:19:57.552000+00:00",
  "signals": {
    "trigger_signal": {
      "at": "2026-10-16T19:19:57.552000+00:00",
      "days": 0,
      "is_lower_bound": false,
      "measured_at": "2026-10-16T19:19:57.552000+00:00",
      "url": "https://www.cve.org/CVERecord?id=CVE-2026-61726"
    }
  }
}

published 2026-10-16 21:10Z
last change 2026-10-21 15:37Z

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.