{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-90910 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-90910 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-90910 is a critical missing authorization vulnerability in Apache Answer, published on 19 Oct 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-90910 and fix it if it is affected.\n\nWhat it is: CVE-2026-90910 is a critical missing authorization vulnerability in Apache Answer, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-90910 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-90910/ (Markdown: https://insights.sbomify.com/CVE-2026-90910/index.md)","id":"CVE-2026-90910","markdown":"https://insights.sbomify.com/CVE-2026-90910/index.md","name":"CVE-2026-90910","record":{"aliases":["GHSA-q532-rv5p-f5vr"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Answer Q\u0026A","requires_auth":"none","summary":"Attackers can bypass visibility controls to read or modify reaction metadata on restricted content in Apache Answer.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-306","name":"Missing Authentication for Critical Functionality"}],"description":"Missing authentication for critical function vulnerability in Apache Answer.\n\nThis issue affects Apache Answer: through 2.0.2.\n\nThe reaction API did not enforce content visibility controls, allowing unauthorized users to read reaction metadata from restricted content or add and remove their own reactions.\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: Reaction API authorization bypass for restricted content","id":"CVE-2026-90910","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Maximo AI Service Denial of Service","id":"CVE-2026-90911"},"packages":[],"prev":{"headline":"Missing authorization in Joomla! CMS","id":"CVE-2026-90907"},"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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-19","vendors":["Apache Software Foundation"]},"summary":"Attackers can bypass visibility controls to read or modify reaction metadata on restricted content in Apache Answer.","url":"https://insights.sbomify.com/CVE-2026-90910/"}