PatchSiren

PatchSiren cyber security CVE debrief

CVE-2026-35046 TandoorRecipes CVE debrief

CVE-2026-35046 is a vulnerability in Tandoor Recipes, an application for managing recipes, planning meals, and building shopping lists. Prior to version 2.6.4, authenticated users can inject arbitrary <style> tags into recipe step instructions. The bleach.clean() sanitizer whitelists the <style> tag, allowing unsanitized CSS payloads to be persisted and served via the API. Clients consuming instructions_markdown from the API and rendering it as HTML without additional sanitization will execute attacker-controlled CSS, enabling UI redressing, phishing overlays, visual defacement, and CSS-based data exfiltration. This vulnerability is fixed in version 2.6.4.

Vendor
TandoorRecipes
Product
recipes
CVSS
MEDIUM 5.4
CISA KEV
Not listed in stored evidence
Original CVE published
2026-04-06
Original CVE updated
2026-10-24
Advisory published
2026-04-06
Advisory updated
2026-10-24

Who should care

Defenders responsible for Tandoor Recipes instances, particularly those with authenticated user access, should assess exposure and apply the fix. They should also verify instance exposure to authenticated users, assess the impact of potential CSS injection, and monitor for suspicious activity after applying the fix.

Why it matters

CVE-2026-35046 allows authenticated users to inject arbitrary CSS, enabling UI redressing, phishing overlays, and data exfiltration. Defenders should verify exposure, assess impact, and apply the fix in version 2.6.4.

  • UI redressing and phishing overlays
  • Visual defacement of recipe instructions
  • CSS-based data exfiltration from rendered recipe pages
  • Verification of Tandoor Recipes instance exposure to authenticated users

Technical summary

The bleach.clean() sanitizer in Tandoor Recipes whitelists the <style> tag, allowing unsanitized CSS payloads to be persisted and served via the API. Clients consuming instructions_markdown from the API and rendering it as HTML without additional sanitization will execute attacker-controlled CSS, potentially leading to UI redressing, phishing overlays, visual defacement, and CSS-based data exfiltration. Defenders should prioritize verifying exposure of Tandoor Recipes instances to authenticated users, assessing the impact of potential CSS injection, and applying the fix in version 2.6.4.

Defensive priority

Defenders should prioritize verifying exposure of Tandoor Recipes instances to authenticated users, assessing the impact of potential CSS injection, and applying the fix in version 2.6.4.

Recommended defensive actions

  • Verify Tandoor Recipes instances for exposure to authenticated users
  • Assess the impact of potential CSS injection
  • Apply the fix in version 2.6.4
  • Monitor for suspicious activity
  • Review compensating controls for exposed systems while remediation is scheduled and verified
  • Check relevant monitoring, detection, and logs for exposed assets that need extra review
  • Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD detail page provide information on the vulnerability, its impact, and the fix in version 2.6.4. Release notes and vendor advisories from TandoorRecipes provide additional context.

Sources and references

Verified primary and authoritative sources

  • CVE-2026-35046 CVE Program record

    Publisher, destination, and source semantics verified

    URL: https://www.cve.org/CVERecord?id=CVE-2026-35046

    CVE Program - Official CVE Program record with source-provided CVE metadata.

  • CVE-2026-35046 NVD vulnerability detail

    Publisher, destination, and source semantics verified

    URL: https://nvd.nist.gov/vuln/detail/CVE-2026-35046

    NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.

Supplemental references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.