Quick answers
- Is CVE-2026-56788 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-56788 being exploited in the wild.
- How severe is CVE-2026-56788?
- Medium severity, with a CVSS score of 4.4, published 25 June 2026.
- Which products and versions are affected?
- Tomoji Takasu RTKLIB through 2.4.3.
- Is there a fix for CVE-2026-56788?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-56788 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-56788?
- Check whether you run Tomoji Takasu RTKLIB at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
An out-of-bounds read exists in the `getcodepri` function within `src/rtkcmn.c`. When the software encounters an unrecognized RINEX observation code, the `code2obs` function returns an empty string and sets an index variable to zero. Subsequent logic performs a negative array index operation (`j-1`) and attempts to read one byte past the empty string constant. This results in a reliable crash (Denial of Service) and may allow the disclosure of adjacent global data. The vulnerability is triggered when a user processes a crafted RINEX file containing unknown observation types.
Affected products
- tomojitakasu RTKLIB through 2.4.3
Timeline
- 2026-06-09: disclosed: Issue reported on GitHub by FuzzingLabs
- 2026-06-25: advisory: NVD and VulnCheck published advisory details