{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32729 exists.","fix":"No fix has been published for CVE-2026-32729 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32729 is a high-severity vulnerability in runtipi, published on 13 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-32729 and fix it if it is affected.\n\nWhat it is: CVE-2026-32729 is a high-severity vulnerability in runtipi, published on 13 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32729 exists.\n\nAffected product: runtipi. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-32729/ (Markdown: https://insights.sbomify.com/CVE-2026-32729/index.md)","id":"CVE-2026-32729","markdown":"https://insights.sbomify.com/CVE-2026-32729/index.md","name":"CVE-2026-32729","record":{"aliases":["GHSA-v6gf-frxm-567w"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Homeserver orchestrator","requires_auth":"low_privilege","summary":"Attackers can bypass two-factor authentication by brute-forcing TOTP codes due to missing rate limiting, leading to account takeover.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"runtipi","vendor":"runtipi"}],"cvss":{"score":8.1,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-799","name":"Improper Control of Interaction Frequency"},{"id":"CWE-307","name":"Improper Restriction of Excessive Authentication Attempts"}],"description":"Runtipi is a personal homeserver orchestrator. Prior to 4.8.1, The Runtipi /api/auth/verify-totp endpoint does not enforce any rate limiting, attempt counting, or account lockout mechanism. An attacker who has obtained a user's valid credentials (via phishing, credential stuffing, or data breach) can brute-force the 6-digit TOTP code to completely bypass two-factor authentication. The TOTP verification session persists for 24 hours (default cache TTL), providing an excessive window during which the full 1,000,000-code keyspace (000000–999999) can be exhausted. At practical request rates (~500 req/s), the attack completes in approximately 33 minutes in the worst case. This vulnerability is fixed in 4.8.1.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"Runtipi has a TOTP two-factor authentication bypass via unrestricted brute-force on `/api/auth/verify-totp`","id":"CVE-2026-32729","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"ApostropheCMS MFA/TOTP Bypass via Incorrect MongoDB Query in Bearer Token Middleware","id":"CVE-2026-32730"},"packages":[],"prev":{"headline":"Parse Server has a stored XSS filter bypass via Content-Type MIME parameter and missing XML extension blocklist entries","id":"CVE-2026-32728"},"products":["runtipi"],"published":"2026-03-13","related":[{"cvss_score":8.1,"headline":"Runtipi is Vulnerable to Authenticated Arbitrary Remote Code Execution","id":"CVE-2026-24129","kev_date_added":null,"published":"2026-01-22"},{"cvss_score":7.7,"headline":"Runtipi unauthenticated /api/auth/reset-password allows operator account takeover during active reset window","id":"CVE-2026-31881","kev_date_added":null,"published":"2026-03-11"},{"cvss_score":7.6,"headline":"Runtipi vulnerable to unauthenticated docker-compose.yml Overwrite via Path Traversal","id":"CVE-2026-25116","kev_date_added":null,"published":"2026-01-29"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-03-16","vendors":["runtipi"]},"summary":"Attackers can bypass two-factor authentication by brute-forcing TOTP codes due to missing rate limiting, leading to account takeover.","url":"https://insights.sbomify.com/CVE-2026-32729/"}