{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-1234 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-1234 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-1234 is a vulnerability."},"fix_prompt":"Check this codebase for CVE-2025-1234 and fix it if it is affected.\n\nWhat it is: CVE-2025-1234 is a vulnerability. \nExploitation: There is no known exploitation of CVE-2025-1234 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-1234/ (Markdown: https://insights.sbomify.com/CVE-2025-1234/index.md)","id":"CVE-2025-1234","markdown":"https://insights.sbomify.com/CVE-2025-1234/index.md","name":"CVE-2025-1234","record":{"aliases":["GHSA-f8qm-c7jq-r9rf"],"analysis":null,"analysis_generated_by":null,"assigner":"GitLab","cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2026-02-14","github_poc":1,"max_poc_stars":1,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-02-14T17:51:05Z","kind":"github_poc","ref":"https://github.com/SimoesCTT/CVE-2025-1234-RSA-Key-Validation-Bypass","stars":1,"title":"A flaw in a popular RSA implementation allows attackers to bypass key validation by supplying a modulus that appears valid but is actually factorable — if you can factor it quickly."}],"tier":"poc_unverified"},"has_fix":null,"headline":"This CVE ID has been rejected or withdrawn by its CVE Numbering Authority.","id":"CVE-2025-1234","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":"WAGO: Switches affected by year 2k38 problem","id":"CVE-2025-1235"},"packages":[],"prev":{"headline":"Lafka Plugin \u003c= 7.1.0 - Missing Authorization to Authenticated (Subscriber+) Theme Option Update","id":"CVE-2025-1233"},"products":[],"published":null,"related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"REJECTED","updated":"2025-07-05","vendors":[]},"summary":null,"url":"https://insights.sbomify.com/CVE-2025-1234/"}