{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32133 exists.","fix":"No fix has been published for CVE-2026-32133 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-32133 is a high-severity server-side request forgery vulnerability in Bubka 2FAuth, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-32133 and fix it if it is affected.\n\nWhat it is: CVE-2026-32133 is a high-severity server-side request forgery vulnerability in Bubka 2FAuth, published on 11 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32133 exists.\n\nAffected product: Bubka 2FAuth. 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-32133/ (Markdown: https://insights.sbomify.com/CVE-2026-32133/index.md)","id":"CVE-2026-32133","markdown":"https://insights.sbomify.com/CVE-2026-32133/index.md","name":"CVE-2026-32133","record":{"aliases":["GHSA-8qp3-x2mp-j6f8"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"2FAuth web app","requires_auth":"none","summary":"Authenticated users can exploit blind SSRF in 2FAuth to access internal networks and cloud metadata endpoints via the image parameter.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"2fauth","vendor":"2fauth"}],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:N/SC:H/SI:H/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"2FAuth is a web app to manage Two-Factor Authentication (2FA) accounts and generate their security codes. Prior to 6.1.0, a blind SSRF vulnerability exists in 2FAuth that allows authenticated users to make arbitrary HTTP requests from the server to internal networks and cloud metadata endpoints. The image parameter in OTP URL is not properly validated for internal / private IP addresses before making HTTP requests. While the previous fix added response validation to ensure only valid images are stored but HTTP request is still made to arbitrary URLs before this validation occurs. This vulnerability is fixed in 6.1.0.","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":"2FAuth has Blind SSRF in image parameter allows internal network access and more","id":"CVE-2026-32133","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"NanoMQ: NULL Pointer Dereference Crash in tcptran_pipe_peer During Session Restore","id":"CVE-2026-32134"},"packages":[],"prev":{"headline":"ZITADEL: Reactivation of Expired Passkey Registration Codes","id":"CVE-2026-32132"},"products":["2FAuth"],"published":"2026-03-11","related":[{"cvss_score":7.5,"headline":"2FAuth vulnerable to Server Side Request Forgery + URI validation bypass in 2fauth /api/v1/twofaccounts/preview","id":"CVE-2024-52598","kev_date_added":null,"published":"2024-11-20"},{"cvss_score":6.5,"headline":"Race condition in n/a","id":"CVE-2025-45731","kev_date_added":null,"published":"2025-07-24"},{"cvss_score":6.1,"headline":"2FAuth vulnerable to stored cross-site scripting via SVG upload and direct access render","id":"CVE-2024-52597","kev_date_added":null,"published":"2024-11-20"},{"cvss_score":6.1,"headline":"Cross-Site Scripting (XSS) at Account creation in 2FAuth","id":"CVE-2023-36816","kev_date_added":null,"published":"2023-07-03"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-12","vendors":["Bubka"]},"summary":"Authenticated users can exploit blind SSRF in 2FAuth to access internal networks and cloud metadata endpoints via the image parameter.","url":"https://insights.sbomify.com/CVE-2026-32133/"}