{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33407 exists.","fix":"No fix has been published for CVE-2026-33407 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33407 is a high-severity server-side request forgery vulnerability in ellite Wallos, published on 24 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-33407 and fix it if it is affected.\n\nWhat it is: CVE-2026-33407 is a high-severity server-side request forgery vulnerability in ellite Wallos, published on 24 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-33407 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-33407/ (Markdown: https://insights.sbomify.com/CVE-2026-33407/index.md)","id":"CVE-2026-33407","markdown":"https://insights.sbomify.com/CVE-2026-33407/index.md","name":"CVE-2026-33407","record":{"aliases":["GHSA-hhjq-82f8-m6rc"],"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":"none","summary":"Attackers can trigger server-side requests to arbitrary domains via proxy environment variables in Wallos, potentially accessing internal resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wallos","vendor":"wallosapp"}],"cvss":{"score":8.3,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-922","name":"Insecure Storage of Sensitive Information"},{"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, Wallos endpoints/logos/search.php accepts HTTP_PROXY and HTTPS_PROXY environment variables without validation, enabling SSRF via proxy hijacking. The server performs DNS resolution on user-supplied search terms, which can be controlled by attackers to trigger outbound requests to arbitrary domains. 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: SSRF via HTTP Proxy Environment Variable","id":"CVE-2026-33407","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Discourse has Improper Authorization in \"Post Edits\" Report For Moderators","id":"CVE-2026-33408"},"packages":[],"prev":{"headline":"Pi-hole has a Stored HTML attribute injection","id":"CVE-2026-33406"},"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.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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-26","vendors":["ellite"]},"summary":"Attackers can trigger server-side requests to arbitrary domains via proxy environment variables in Wallos, potentially accessing internal resources.","url":"https://insights.sbomify.com/CVE-2026-33407/"}