{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-11569 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-11569 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-11569 is a vulnerability, published on 10 Oct 2025."},"fix_prompt":"Check this codebase for CVE-2025-11569 and fix it if it is affected.\n\nWhat it is: CVE-2025-11569 is a vulnerability, published on 10 Oct 2025. \nExploitation: There is no known exploitation of CVE-2025-11569 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-2025-11569/ (Markdown: https://insights.sbomify.com/CVE-2025-11569/index.md)","id":"CVE-2025-11569","markdown":"https://insights.sbomify.com/CVE-2025-11569/index.md","name":"CVE-2025-11569","record":{"aliases":[],"analysis":null,"analysis_generated_by":null,"assigner":"snyk","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This record was withdrawn by its CNA; further investigation revealed it was not a security 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":"This record was withdrawn by its CNA; further investigation revealed it was not a security issue.","id":"CVE-2025-11569","indexable":false,"kev":null,"kind":"cve_rejected","links":{"ecosystem":null,"product":null,"products":[],"type":null,"year":"2025"},"n_packages":0,"n_references":0,"next":{"headline":"drupal-pattern-lab/unified-twig-extensions is vulnerable to XXS","id":"CVE-2025-11570"},"packages":[],"prev":{"headline":"Luksmeta: data corruption when handling luks1 partitions with luksmeta","id":"CVE-2025-11568"},"products":[],"published":"2025-10-10","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":"2025-10-30","vendors":[]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-11569/"}