{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56789 exists.","fix":"No fix has been published for CVE-2026-56789 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-56789 is a high-severity memory corruption vulnerability in tomojitakasu RTKLIB, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-56789 and fix it if it is affected.\n\nWhat it is: CVE-2026-56789 is a high-severity memory corruption vulnerability in tomojitakasu RTKLIB, published on 25 Jun 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-56789 exists.\n\nAffected product: tomojitakasu RTKLIB. 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-56789/ (Markdown: https://insights.sbomify.com/CVE-2026-56789/index.md)","id":"CVE-2026-56789","markdown":"https://insights.sbomify.com/CVE-2026-56789/index.md","name":"CVE-2026-56789","record":{"aliases":["DEBIAN-CVE-2026-56789","GHSA-3fqf-8h5x-pq8x","UBUNTU-CVE-2026-56789"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution","denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"GNSS positioning library","requires_auth":"none","summary":"Attackers can execute arbitrary code or crash applications by providing malicious RINEX files with excessive satellite counts to RTKLIB.","user_interaction":"required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulnCheck","cpe":[{"product":"rtklib","vendor":"rtklib"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-122","name":"Heap-based Buffer Overflow"}],"description":"RTKLIB through 2.4.3 contains a heap buffer overflow vulnerability in the readrnxobsb function in src/rinex.c that allows attackers to trigger memory corruption by failing to clamp satellite count values from RINEX epoch headers. Attackers can craft malicious RINEX files declaring more than 64 satellites per epoch to cause heap buffer overflow writes and out-of-bounds stack reads, crashing RTKLIB-based applications including rnx2rtkp and RTKPOST.","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":"RTKLIB 2.4.3 - Heap Buffer Overflow and Stack Read via Oversized RINEX Epoch Satellite Count","id":"CVE-2026-56789","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":"CANBoat - Off-by-One Global Buffer Overflow in searchForPgn()","id":"CVE-2026-56790"},"packages":[],"prev":{"headline":"RTKLIB 2.4.3 - Out-of-bounds Read via Negative Array Index in getcodepri","id":"CVE-2026-56788"},"products":["RTKLIB"],"published":"2026-06-25","related":[{"cvss_score":9.3,"headline":"RTKLIB 2.4.3 - Out-of-bounds Write in decode_type1033 via Crafted RTCM3 Message","id":"CVE-2026-56786","kev_date_added":null,"published":"2026-06-25"},{"cvss_score":6.9,"headline":"RTKLIB 2.4.3 - Off-by-One Out-of-Bounds Read in decode_ssr3 via RTCM3 SSR Message","id":"CVE-2026-56787","kev_date_added":null,"published":"2026-06-25"},{"cvss_score":4.8,"headline":"RTKLIB 2.4.3 - Out-of-bounds Read via Negative Array Index in getcodepri","id":"CVE-2026-56788","kev_date_added":null,"published":"2026-06-25"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-07-14","vendors":["tomojitakasu"]},"summary":"Attackers can execute arbitrary code or crash applications by providing malicious RINEX files with excessive satellite counts to RTKLIB.","url":"https://insights.sbomify.com/CVE-2026-56789/"}