PatchTheCVErtklib vulnerabilities
Recent CVEs affecting rtklib products. 4 tracked.
rtklib has 4 tracked vulnerabilities, 1 critical. A fixed release or vendor patch exists for 4. Most recent: 2026-06-25. Highest priority: CVE-2026-56786 (score 61/100).
- CVE-2026-56786 CRITICAL 9.8 UPGRADE RTKLIB through 2.4.3 contains an out-of-bounds write vulnerability in decode_type1033 function that fails to c
- CVE-2026-56787 MEDIUM 6.5 UPGRADE RTKLIB through 2.4.3 contains an off-by-one out-of-bounds read vulnerability in the decode_ssr3 function at sr
- CVE-2026-56789 MEDIUM 6.5 UPGRADE RTKLIB through 2.4.3 contains a heap buffer overflow vulnerability in the readrnxobsb function in src/rinex.c
- CVE-2026-56788 MEDIUM 4.4 UPGRADE RTKLIB through 2.4.3 contains an out-of-bounds read vulnerability in getcodepri function when processing unrec
FAQ
How do I fix rtklib vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is rtklib being exploited right now?
None of the tracked rtklib CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which rtklib CVE should I patch first?
CVE-2026-56786 currently ranks highest (61/100): RTKLIB through 2.4.3 contains an out-of-bounds write vulnerability in decode_type1033 function that fails to c.