{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33401 exists.","fix":"No fix has been published for CVE-2026-33401 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33401 is a high-severity server-side request forgery vulnerability in ellite Wallos, published on 24 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-33401 and fix it if it is affected.\n\nWhat it is: CVE-2026-33401 is a high-severity server-side request forgery vulnerability in ellite Wallos, published on 24 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-33401 exists.\n\nAffected product: ellite Wallos. 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-33401/ (Markdown: https://insights.sbomify.com/CVE-2026-33401/index.md)","id":"CVE-2026-33401","markdown":"https://insights.sbomify.com/CVE-2026-33401/index.md","name":"CVE-2026-33401","record":{"aliases":["GHSA-r82v-p8cg-rgx3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"Wallos subscription tracker","requires_auth":"low_privilege","summary":"Authenticated users can exploit SSRF in AI and notification endpoints to access internal network services and cloud metadata.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wallos","vendor":"wallosapp"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"Wallos is an open-source, self-hostable personal subscription tracker. Prior to version 4.7.0, the patch introduced in commit e8a513591 (CVE-2026-30840) added SSRF protection to notification test endpoints but left three additional attack surfaces unprotected: the AI Ollama host parameter, the AI recommendations endpoint, and the notification cron job. An authenticated user can reach internal network services, cloud metadata endpoints (AWS IMDSv1, GCP, Azure IMDS), or localhost-bound services by supplying a crafted URL to any of these endpoints. This issue has been patched in version 4.7.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":"Wallos: Incomplete fix for CVE-2026-30840 - SSRF in AI and notification endpoints bypass ssrf_helper.php","id":"CVE-2026-33401","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"SAK-52311: Sakai site-manage group titles can contain XSS content","id":"CVE-2026-33402"},"packages":[],"prev":{"headline":"Wallos: Stored cross-site scripting (XSS) vulnerability in the payment method rename endpoint","id":"CVE-2026-33400"},"products":["Wallos"],"published":"2026-03-24","related":[{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-55371","kev_date_added":null,"published":"2025-04-16"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-55372","kev_date_added":null,"published":"2025-04-16"},{"cvss_score":8.8,"headline":"Wallos: Server-Side Request Forgery (SSRF) in Notification Testers","id":"CVE-2026-30840","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":8.7,"headline":"Wallos: SSRF via url parameter leading to File Traversal","id":"CVE-2026-30828","kev_date_added":null,"published":"2026-03-07"},{"cvss_score":8.3,"headline":"Wallos: SSRF via HTTP Proxy Environment Variable","id":"CVE-2026-33407","kev_date_added":null,"published":"2026-03-24"},{"cvss_score":8.1,"headline":"SQL injection in n/a","id":"CVE-2024-29320","kev_date_added":null,"published":"2024-04-30"},{"cvss_score":7.7,"headline":"Wallos: SSRF Bypass - Incomplete Fix for CVE-2026-30839/30840","id":"CVE-2026-33399","kev_date_added":null,"published":"2026-03-24"}],"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":"partial"},"state":"PUBLISHED","updated":"2026-03-24","vendors":["ellite"]},"summary":"Authenticated users can exploit SSRF in AI and notification endpoints to access internal network services and cloud metadata.","url":"https://insights.sbomify.com/CVE-2026-33401/"}