Skip to main content
VulnerabilityPublished

CVE-2026-28503: TandoorRecipes recipes · Insecure Direct Object Reference

Affects TandoorRecipes recipesSource CVE Database V5

0

Public exploit available · CVSS 5.5 Medium : upgrade to 2.6.0 as a priority.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score
5.5Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.6.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 26 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade recipes and tandoorrecipes/recipes to 2.6.0.

Affected software

ProductAffectedFixed in
TandoorRecipesrecipesAffected
  • <2.6.0
Fixed in
  • 2.6.0
GitHubtandoorrecipes/recipespkg:github/tandoorrecipes/recipesOther threatsAffected
  • <2.6.0
Fixed in
  • 2.6.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade Tandoor Recipes to version 2.6.0 or later, where this authorization bypass vulnerability has been fixed. No other mitigations are specified or required once the official patch is applied.

Description

CVE-2026-28503 is an authorization bypass vulnerability in Tandoor Recipes versions prior to 2.6.0. The flaw exists in the SyncViewSet.query_synced_folder() function, which fetches Sync objects without properly restricting access by space. This allows an admin user in one space to trigger sync operations and view sync logs belonging to another space. The issue is fixed in version 2.6.0.

References

Community reviews

Loading reviews…