{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-94489 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-94489 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-94489 is a vulnerability, published on 21 Sep 2026."},"fix_prompt":"Check this codebase for CVE-2026-94489 and fix it if it is affected.\n\nWhat it is: CVE-2026-94489 is a vulnerability, published on 21 Sep 2026. \nExploitation: There is no known exploitation of CVE-2026-94489 in the wild and no public exploit code.\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-94489/ (Markdown: https://insights.sbomify.com/CVE-2026-94489/index.md)","id":"CVE-2026-94489","markdown":"https://insights.sbomify.com/CVE-2026-94489/index.md","name":"CVE-2026-94489","record":{"aliases":["GHSA-6wqw-4v48-3xjc"],"analysis":null,"analysis_generated_by":null,"assigner":"VulDB","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"** REJECT ** DO NOT USE THIS CANDIDATE NUMBER. ConsultIDs: none. Reason: This candidate was withdrawn by its CNA. Further investigation showed that it was not a security issue. Notes: The exact code first shipped in 1.6.0, does not exist in the cited 1.0.0, and in every version where it exists the claimed missing protection is already implemented.","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":"** REJECT ** DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2026-94489","indexable":false,"kev":null,"kind":"cve_rejected","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2026"},"n_packages":0,"n_references":0,"next":{"headline":"** REJECT ** DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2026-94490"},"packages":[],"prev":{"headline":"Cross-site scripting in Telegram Desktop","id":"CVE-2026-94488"},"products":[],"published":"2026-09-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"REJECTED","updated":"2026-10-13","vendors":[]},"summary":null,"url":"https://insights.sbomify.com/CVE-2026-94489/"}