CVE-2026-33152
Tandoor Recipes ≤ 2.6.0
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2026-33152 is a critical-severity Improper Restriction of Excessive Authentication Attempts (CWE-307) vulnerability in Tandoor Recipes. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked at the 41th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to AC-7 (Unsuccessful Logon Attempts) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-33152 is a high-severity vulnerability (CVSS 9.1, CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N) affecting Tandoor Recipes, an open-source application for managing recipes, planning meals, and building shopping lists, in versions prior to 2.6.0. The issue stems from the configuration of Django REST Framework, which includes BasicAuthentication as a default authentication backend without rate limiting on API endpoints. While the AllAuth rate limiting (ACCOUNT_RATE_LIMITS: login: 5/m/ip) protects the HTML-based login at /accounts/login/, it does not apply to API endpoints that accept authenticated requests via Authorization: Basic headers. This enables unlimited password guessing attempts with no account lockout, classified under CWE-307 (Improper Restriction of Excessive Authentication Attempts).
Any remote attacker without privileges can exploit this vulnerability by targeting API endpoints with high-speed brute-force attacks using known usernames and Authorization: Basic headers. Successful exploitation allows account takeover, potentially granting full access to user data, recipes, meal plans, and shopping lists, with high impacts on confidentiality and integrity.
The vulnerability is patched in Tandoor Recipes version 2.6.0, as detailed in the project's release notes and security advisory. Security practitioners should upgrade to 2.6.0 or later and review custom configurations for similar misconfigurations in Django REST Framework deployments. Relevant resources include the GitHub release at https://github.com/TandoorRecipes/recipes/releases/tag/2.6.0 and the advisory at https://github.com/TandoorRecipes/recipes/security/advisories/GHSA-7m7c-jjqc-r522.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-16315
Vulnerability Data
Tandoor Recipes is an application for managing recipes, planning meals, and building shopping lists. In versions prior to 2.6.0, Tandoor Recipes configures Django REST Framework with BasicAuthentication as one of the default authentication backends. The AllAuth rate limiting configuration (ACCOUNT_RATE_LIMITS:…
more
login: 5/m/ip) only applies to the HTML-based login endpoint at /accounts/login/. Any API endpoint that accepts authenticated requests can be targeted via Authorization: Basic headers with zero rate limiting, zero account lockout, and unlimited attempts. An attacker can perform high-speed password guessing against any known username. Version 2.6.0 patches the issue.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 2 hardening rules · 1 OS baseline
—
Mitigating Controls (NIST 800-53 r5) AI
AC-7 directly enforces limits on consecutive failed logons, structurally blocking brute-force exploitation of the weakness.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Authentication enforcement directly includes lockout, throttling, and MFA policies that prevent brute-force attempts.
Behavioral monitoring of authentication activity can detect excessive failed attempts after they occur.
Generating auth logs enables later detection or forensics but does not itself restrict attempts.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
CAPTCHA, account lock-out after repeated failures, and alerts on excessive attempts directly stop automated brute-force guessing of credentials.
Hardening callouts derived
Configuration rules from DISA STIG baselines that bear on weaknesses of the type cited by this CVE. Each rule is shown with the relationship its mapping actually records, against the CWE it was authored against. Derived via CVE→CWE over `controls_xwalks` (authoritative rows only; rows rated `none` are excluded).
RHEL 7 (2 rules)
- V-204427 The Red Hat Enterprise Linux operating system must be configured to lock accounts for a minimum of 15 minutes after three unsuccessful logon attempts within a 15-minute timeframe. prevents CWE-307
- V-204428 The Red Hat Enterprise Linux operating system must lock the associated account after three unsuccessful root logon attempts are made within a 15-minute period. prevents CWE-307