{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-49433 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-49433 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-49433 is a low-severity vulnerability in api.deepai.org, published on 1 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-49433 and fix it if it is affected.\n\nWhat it is: CVE-2026-49433 is a low-severity vulnerability in api.deepai.org, published on 1 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-49433 in the wild and no public exploit code.\n\nAffected product: api.deepai.org. 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-49433/ (Markdown: https://insights.sbomify.com/CVE-2026-49433/index.md)","id":"CVE-2026-49433","markdown":"https://insights.sbomify.com/CVE-2026-49433/index.md","name":"CVE-2026-49433","record":{"aliases":["GHSA-h9m8-r5ff-p645"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"DeepAI API","requires_auth":"none","summary":"Attackers can change user email addresses via CSRF, leading to account takeover on the DeepAI API.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisa-cg","cpe":[],"cvss":{"score":2.3,"severity":"low","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The DeepAI endpoint 'https://api.deepai.org/change_user_email' accepts POST requests without any CSRF protection. If an attacker can trick a logged-in user into clicking a malicious link, the attacker can change the user's email address and take over their account. Fixed on 2026-05-20.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"DeepAI api.deepai.org/change_user_email CSRF","id":"CVE-2026-49433","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Code injection in Apache ActiveMQ","id":"CVE-2026-49434"},"packages":[],"prev":{"headline":"Apache ActiveMQ, Apache ActiveMQ All, Apache ActiveMQ Stomp: STOMP negative content-length enables denial of service","id":"CVE-2026-49432"},"products":["api.deepai.org"],"published":"2026-06-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-01","vendors":["DeepAI"]},"summary":"Attackers can change user email addresses via CSRF, leading to account takeover on the DeepAI API.","url":"https://insights.sbomify.com/CVE-2026-49433/"}