{"answers":{"affected":"1 open source package ship an affected version, including readstat.","exploited":"There is no known exploitation of OSV-2026-634 in the wild and no public exploit code.","fix":"No fix has been published for OSV-2026-634 yet. Limit exposure of the affected software until one is available.","what":"OSV-2026-634 is a memory corruption vulnerability in readstat, published on 27 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for OSV-2026-634 and fix it if it is affected.\n\nWhat it is: OSV-2026-634 is a memory corruption vulnerability in readstat, published on 27 Apr 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of OSV-2026-634 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- readstat (OSS-Fuzz): affected all versions; no fix listed\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/OSV-2026-634/ (Markdown: https://insights.sbomify.com/OSV-2026-634/index.md)","id":"OSV-2026-634","markdown":"https://insights.sbomify.com/OSV-2026-634/index.md","name":"OSV-2026-634","record":{"aliases":[],"analysis":{"component_type":"library","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SAS data library","requires_auth":"none","summary":"An index-out-of-bounds error in the SAS data parsing library can cause a crash when processing malicious files.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":null,"cpe":[],"cvss":{"score":null,"severity":null,"source":null,"vector":null,"version":null},"cwes":[],"description":"OSS-Fuzz report: https://bugs.chromium.org/p/oss-fuzz/issues/detail?id=506459940\n\n```\nCrash type: Index-out-of-bounds\nCrash state:\nsas7bdat_submit_columns_if_needed\nsas7bdat_parse_all_pages_pass2\nreadstat_parse_sas7bdat\n```","ecosystems":["OSS-Fuzz"],"exploits":{"exploitdb":null,"first_seen":null,"github_poc":null,"max_poc_stars":null,"metasploit":null,"nuclei":null,"refs":[],"tier":null},"has_fix":false,"headline":"Index-out-of-bounds in sas7bdat_submit_columns_if_needed","id":"OSV-2026-634","indexable":true,"kev":null,"kind":"advisory","links":{"ecosystem":"OSS-Fuzz","product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":1,"n_references":null,"packages":[{"ecosystem":"OSS-Fuzz","fixed":[],"introduced":[],"last_affected":[],"package":"readstat","purl":"pkg:generic/readstat","source":"OSV-2026-634"}],"products":null,"published":"2026-04-27","related":[],"sources":[{"class":"attribution","licence":"CC BY 4.0","name":"OSS-Fuzz","prefix":"OSV"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":null,"updated":null,"vendors":null},"summary":"An index-out-of-bounds error in the SAS data parsing library can cause a crash when processing malicious files.","url":"https://insights.sbomify.com/OSV-2026-634/"}