{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-33417 exists.","fix":"No fix has been published for CVE-2026-33417 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-33417 is a medium-severity 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-33417 and fix it if it is affected.\n\nWhat it is: CVE-2026-33417 is a medium-severity 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-33417 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-33417/ (Markdown: https://insights.sbomify.com/CVE-2026-33417/index.md)","id":"CVE-2026-33417","markdown":"https://insights.sbomify.com/CVE-2026-33417/index.md","name":"CVE-2026-33417","record":{"aliases":["GHSA-p3fv-m43r-3fhf"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Subscription tracker","requires_auth":"none","summary":"Attackers can hijack accounts using intercepted password reset tokens that never expire, affecting Wallos users.","user_interaction":"not_required","vuln_class":"security_feature_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"wallos","vendor":"wallosapp"}],"cvss":{"score":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-613","name":"DEPRECATED: Insufficient Session Expiration"}],"description":"Wallos is an open-source, self-hostable personal subscription tracker. Prior to version 4.7.2, password reset tokens in Wallos never expire. The password_resets table includes a created_at timestamp column, but the token validation logic never checks it. A password reset token remains valid indefinitely until it is used, allowing an attacker who intercepts a reset link at any point to use it days, weeks, or months later. This issue has been patched in version 4.7.2.","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: Password Reset Tokens Never Expire","id":"CVE-2026-33417","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"security_feature_bypass","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"@dicebear/converter ensureSize() Vulnerable to SVG Dimension Capping Bypass via XML Comment Injection","id":"CVE-2026-33418"},"packages":[],"prev":{"headline":"LIBPNG has use-after-free via pointer aliasing in `png_set_tRNS` and `png_set_PLTE`","id":"CVE-2026-33416"},"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":"Attackers can hijack accounts using intercepted password reset tokens that never expire, affecting Wallos users.","url":"https://insights.sbomify.com/CVE-2026-33417/"}