{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-21898 exists.","fix":"No fix has been published for CVE-2026-21898 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-21898 is a high-severity memory corruption vulnerability in nasa CryptoLib, published on 10 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-21898 and fix it if it is affected.\n\nWhat it is: CVE-2026-21898 is a high-severity memory corruption vulnerability in nasa CryptoLib, published on 10 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-21898 exists.\n\nAffected product: nasa CryptoLib. 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-2026-21898/ (Markdown: https://insights.sbomify.com/CVE-2026-21898/index.md)","id":"CVE-2026-21898","markdown":"https://insights.sbomify.com/CVE-2026-21898/index.md","name":"CVE-2026-21898","record":{"aliases":["GHSA-7ch6-2pmg-m853"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["denial_of_service","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Space Data Link Security Library","requires_auth":"none","summary":"An out-of-bounds read in CryptoLib allows attackers to cause denial of service or disclose sensitive memory contents when parsing AOS frames.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"cryptolib","vendor":"nasa"}],"cvss":{"score":8.2,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-125","name":"Out-of-bounds Read"}],"description":"CryptoLib provides a software-only solution using the CCSDS Space Data Link Security Protocol - Extended Procedures (SDLS-EP) to secure communications between a spacecraft running the core Flight System (cFS) and a ground station. Prior to version 1.4.3, the Crypto_AOS_ProcessSecurity function reads memory without valid bounds checking when parsing AOS frame hashes. This issue has been patched in version 1.4.3.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"CryptoLib Has Out-of-bounds Read in Crypto_AOS_ProcessSecurity","id":"CVE-2026-21898","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"CryptoLib has an out-of-bounds read and crash vulnerability when decoding an empty Base64url string","id":"CVE-2026-21899"},"packages":[],"prev":{"headline":"CryptoLib Has Out-of-Bounds Write in Crypto_Config_Add_Gvcid_Managed_Parameters","id":"CVE-2026-21897"},"products":["CryptoLib"],"published":"2026-01-10","related":[{"cvss_score":9.4,"headline":"CryptoLib Has Heap Overflow in Crypto_TM_ProcessSecurity due to Unchecked Secondary Header Length","id":"CVE-2025-30216","kev_date_added":null,"published":"2025-03-25"},{"cvss_score":9.3,"headline":"Heap Buffer Overflow via Incomplete Length Check in `Crypto_TC_ApplySecurity`","id":"CVE-2025-30356","kev_date_added":null,"published":"2025-04-01"},{"cvss_score":8.9,"headline":"CryptoLib's Crypto_TC_ApplySecurity() Has a Heap Buffer Overflow Vulnerability","id":"CVE-2025-29909","kev_date_added":null,"published":"2025-03-17"},{"cvss_score":8.9,"headline":"CryptoLib Has Heap Buffer Overflow in Crypto_AOS_ProcessSecurity Function","id":"CVE-2025-29911","kev_date_added":null,"published":"2025-03-17"},{"cvss_score":8.9,"headline":"CryptoLib Has Heap Buffer Overflow Due to Unsigned Integer Underflow in Crypto_TC_ProcessSecurity","id":"CVE-2025-29912","kev_date_added":null,"published":"2025-03-17"},{"cvss_score":8.9,"headline":"CryptoLib's Crypto_TC_Prep_AAD Has Buffer Overflow Due to Integer Underflow","id":"CVE-2025-29913","kev_date_added":null,"published":"2025-03-17"},{"cvss_score":8.8,"headline":"CryptoLib vulnerable to Stack Buffer Overflow in Crypto_Key_Update due to missing TLV length check","id":"CVE-2025-64096","kev_date_added":null,"published":"2025-10-30"}],"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":"yes","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-12","vendors":["nasa"]},"summary":"An out-of-bounds read in CryptoLib allows attackers to cause denial of service or disclose sensitive memory contents when parsing AOS frames.","url":"https://insights.sbomify.com/CVE-2026-21898/"}