{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67921 exists.","fix":"No fix has been published for CVE-2026-67921 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-67921 is a critical vulnerability in n/a, published on 18 Aug 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-67921 and fix it if it is affected.\n\nWhat it is: CVE-2026-67921 is a critical vulnerability in n/a, published on 18 Aug 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-67921 exists.\n\nAffected product: n/a. 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-67921/ (Markdown: https://insights.sbomify.com/CVE-2026-67921/index.md)","id":"CVE-2026-67921","markdown":"https://insights.sbomify.com/CVE-2026-67921/index.md","name":"CVE-2026-67921","record":{"aliases":["GHSA-5x82-gw26-c8r3"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Halo CMS","requires_auth":"none","summary":"A CSRF vulnerability in Halo CMS allows remote attackers to execute arbitrary code via specific configuration components.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":9.3,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross-Site Request Forgery (CSRF) vulnerability exists in Halo CMS versions up to 2.25.4 via the CorsConfigurer.java and the CsrfConfigurer.java components. This allows a remote attacker to execute arbitrary code.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-08-10","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-08-10T08:50:09Z","kind":"github_poc","ref":"https://github.com/unpredictable21/halo-cors-csrf-CVE-2026-67921","stars":0,"title":null}],"tier":"weaponised"},"has_fix":false,"headline":"Cross-site request forgery in n/a","id":"CVE-2026-67921","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2026-67925"},"packages":[],"prev":{"headline":"Path traversal in n/a","id":"CVE-2026-67920"},"products":["n/a"],"published":"2026-08-18","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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-08-20","vendors":["n/a"]},"summary":"A CSRF vulnerability in Halo CMS allows remote attackers to execute arbitrary code via specific configuration components.","url":"https://insights.sbomify.com/CVE-2026-67921/"}