{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-48755 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-48755 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-48755 is a low-severity denial of service vulnerability in blyssprivacy sdk, published on 24 May 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-48755 and fix it if it is affected.\n\nWhat it is: CVE-2025-48755 is a low-severity denial of service vulnerability in blyssprivacy sdk, published on 24 May 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-48755 in the wild and no public exploit code.\n\nAffected product: blyssprivacy sdk. 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-2025-48755/ (Markdown: https://insights.sbomify.com/CVE-2025-48755/index.md)","id":"CVE-2025-48755","markdown":"https://insights.sbomify.com/CVE-2025-48755/index.md","name":"CVE-2025-48755","record":{"aliases":["GHSA-4pfj-xhf6-v58f"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Rust SDK library","requires_auth":"none","summary":"A flaw in the spiral-rs Rust crate allows attempting allocation for zero-sized types, potentially causing a denial of service.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"spiral-rs","vendor":"blyssprivacy"}],"cvss":{"score":2.9,"severity":"low","source":"cna","vector":"CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-762","name":"Mismatched Memory Management Routines"}],"description":"In the spiral-rs crate 0.2.0 for Rust, allocation can be attempted for a ZST (zero-sized type).","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":"Denial of service in sdk","id":"CVE-2025-48755","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"SCSIR has a Potential Unsound Issue in WriteSameCommand","id":"CVE-2025-48756"},"packages":[],"prev":{"headline":"memory_pages division by zero","id":"CVE-2025-48754"},"products":["sdk"],"published":"2025-05-24","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-05-24","vendors":["blyssprivacy"]},"summary":"A flaw in the spiral-rs Rust crate allows attempting allocation for zero-sized types, potentially causing a denial of service.","url":"https://insights.sbomify.com/CVE-2025-48755/"}