{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-67249 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-67249 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-67249 is a medium-severity authentication bypass vulnerability in Apache Answer, published on 19 Oct 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-67249 and fix it if it is affected.\n\nWhat it is: CVE-2026-67249 is a medium-severity authentication bypass vulnerability in Apache Answer, published on 19 Oct 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-67249 in the wild and no public exploit code.\n\nAffected product: Apache Answer. 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-67249/ (Markdown: https://insights.sbomify.com/CVE-2026-67249/index.md)","id":"CVE-2026-67249","markdown":"https://insights.sbomify.com/CVE-2026-67249/index.md","name":"CVE-2026-67249","record":{"aliases":["GHSA-v85w-3rf6-qvhj"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Answer","requires_auth":"none","summary":"Attackers can hijack user accounts by reusing verification codes across different email workflows due to missing purpose enforcement.","user_interaction":"required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-863","name":"Incorrect Authorization"}],"description":"A vulnerability in Apache Answer.\n\nThis issue affects Apache Answer: through 2.0.2.\n\nA verification code issued for one email-based workflow could be accepted by another sensitive workflow because the code purpose was not properly enforced.\n\nUsers are recommended to upgrade to version 2.0.3, which fixes the issue.","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":"Apache Answer: Email Code Purpose Confusion May Allow Account Takeover","id":"CVE-2026-67249","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Apache Airflow: DAG-author remote code execution on the Scheduler via awaiting_input next_kwargs deserialization","id":"CVE-2026-67260"},"packages":[],"prev":{"headline":"A stack-based buffer overflow vulnerability was found in the File Explorer on the ADM","id":"CVE-2026-67248"},"products":["Apache Answer"],"published":"2026-10-19","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-10-26","vendors":["Apache Software Foundation"]},"summary":"Attackers can hijack user accounts by reusing verification codes across different email workflows due to missing purpose enforcement.","url":"https://insights.sbomify.com/CVE-2026-67249/"}