{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-3551 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-3551 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-3551 is a vulnerability, published on 14 Apr 2025."},"fix_prompt":"Check this codebase for CVE-2025-3551 and fix it if it is affected.\n\nWhat it is: CVE-2025-3551 is a vulnerability, published on 14 Apr 2025. \nExploitation: There is no known exploitation of CVE-2025-3551 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-3551/ (Markdown: https://insights.sbomify.com/CVE-2025-3551/index.md)","id":"CVE-2025-3551","markdown":"https://insights.sbomify.com/CVE-2025-3551/index.md","name":"CVE-2025-3551","record":{"aliases":["GHSA-x9m2-445c-rwph"],"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 vendor was not able to verify the existence of the original vulnerability report and the researcher was not able to provide further proof.","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-2025-3551","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":"** REJECT ** DO NOT USE THIS CANDIDATE NUMBER.","id":"CVE-2025-3552"},"packages":[],"prev":{"headline":"wowjoy 浙江湖州华卓信息科技有限公司 Internet Doctor Workstation System detail improper authorization","id":"CVE-2025-3550"},"products":[],"published":"2025-04-14","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-05-05","vendors":[]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-3551/"}