Memory corruption via unclamped RTCM3 descriptor lengths
Published Jun 25, 2026 · Updated Jun 25, 2026
Out-of-bounds writes in RTKLIB 2.4.3 and earlier allow remote attackers to corrupt memory via crafted RTCM3 type-1033 streams. decode_type1033 passes five untrusted 8-bit lengths to strncpy and terminator writes targeting fixed 64-byte rtcm_t descriptor fields. Control of an NTRIP or serial correction stream is required; corruption can crash a consumer or alter adjacent rtcm_t state.
Summary
What happened
Out-of-bounds writes in RTKLIB 2.4.3 and earlier allow remote attackers to corrupt memory via crafted RTCM3 type-1033 streams. decode_type1033 passes five untrusted 8-bit lengths to strncpy and terminator writes targeting fixed 64-byte rtcm_t descriptor fields. Control of an NTRIP or serial correction stream is required; corruption can crash a consumer or alter adjacent rtcm_t state.
The record
- CVE
- CVE-2026-56786
- Published
- Jun 25, 2026
- Updated
- Jun 25, 2026
- Vendor
- Tomoji Takasu
- Product
- RTKLIB
- Classifications
- CWE-787, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 25, 2026CVE publishedPublication date reported by the CVE source.
- Jun 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.4.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- RTCM3 type-1033 oversized descriptor proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo