CVE-2026-115810 TandoorRecipes CVE debrief

Who should care

Defenders and administrators of Tandoor Recipes instances, especially those with authenticated low-privileged users, should assess exposure and potential impact. This includes reviewing system configurations, verifying versions, and prioritizing remediation efforts to prevent potential SSRF attacks.

Why it matters

Defenders should care about CVE-2026-115810 because it allows authenticated low-privileged users to perform SSRF attacks, potentially exposing internal endpoints, performing port/service discovery, and exfiltrating internal responses. Verification of exposure, assessment of potential impact, and prioritization of remediation are crucial.

• Potential exposure of internal-only endpoints
• Possible port/service discovery by attackers
• Exfiltration of internal responses via stored recipe images
• Verification of vulnerable versions and remediation prioritization

Technical summary

The vulnerability is located in the Pestle importer, specifically in cookbook/integration/pestle.py, which bypasses the application's centralized requests-hardened SSRF filter. This allows authenticated low-privileged users to force the server to issue GET requests to arbitrary internal or external hosts by crafting a malicious image URL in a Pestle JSON import file. The technical impact includes potential exposure of internal-only endpoints, port/service discovery, and exfiltration of internal responses via stored recipe images.

Defensive priority

Defenders should prioritize verifying exposure and assessing potential impact, focusing on systems with authenticated low-privileged users.

Recommended defensive actions

• Verify Tandoor Recipes versions and identify instances that are not upgraded to 2.7.0
• Assess exposure of internal-only endpoints and perform port/service discovery
• Implement compensating controls to monitor and restrict requests to internal hosts
• Review and update incident response plans to address potential SSRF exploitation
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed

Evidence notes

The vulnerability is confirmed in Tandoor Recipes before 2.7.0, specifically in the Pestle importer within cookbook/integration/pestle.py. The application's centralized requests-hardened SSRF filter is bypassed, allowing for arbitrary GET requests. Evidence is based on the CVE record and source item details, with limitations on affected scope and severity. Defenders should verify exposure and assess potential impact.

Sources and 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.