VRPN through 07.36 Out-of-bounds Write via SENDER_DESCRIPTION/TYPE_DESCRIPTION length index
Affects VRPN through 07.36, where a remote client can crash the process after completing the version-cookie exchange. No fixed version is listed in the checked facts.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fix or patch referenced
- Who is exposed
- Not reported
Do first: Apply the patch listed under Evidence.
- Last modified
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 26/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
VRPN, a library used for virtual reality and motion-tracking devices, contains an out-of-bounds stack write that a remote attacker can trigger over the network without logging in, by sending a crafted sender or type description message after the connection handshake. The flaw can crash the affected process, so the most an attacker is shown to achieve is denial of service.
Read the original description
VRPN through 07.36 contains an out-of-bounds stack write vulnerability in vrpn_Endpoint::handle_sender_message() and handle_type_message() that allows unauthenticated remote peers to write outside a stack buffer via an unchecked length index. Attackers can connect, complete the version-cookie exchange, and send a SENDER_DESCRIPTION or TYPE_DESCRIPTION message with an out-of-range or negative index to crash the process.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · Unknown: Advisories don't say whether default setups are affected
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 71 if added to CISA KEV
- Would score about 66 if CISA's SSVC rates exploitation active
- Would score about 31 if advisories confirm default setups are exposed
What to do
Apply the patch listed under Evidence.
Timeline
- CVE published
- First seen by cve.now
Affected versions
- VRPN VRPN
through 07.36
Evidence 5
- Patch
- Patch
- Repository
- Repository
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-123200
Is CVE-2026-123200 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
A SENDER_DESCRIPTION or TYPE_DESCRIPTION message with an out-of-range or negative index causes an out-of-bounds write on the stack. The result is a crash of the VRPN process, which is a denial of service.Source: vulncheck.com
Which versions are affected by CVE-2026-123200?
VRPN: through 07.36.Source: cve.now feed data
Am I affected, and how do I check?
The checked facts list VRPN through version 07.36 as affected. Exposure requires a connection that completes the version-cookie exchange before the malicious message is sent, so a reader can compare the installed VRPN version against that range.Source: vulncheck.com
How do I fix CVE-2026-123200?
The checked facts do not name a fixed version, so no upgrade target can be given from them. Check the VRPN project's release notes or advisory for a version later than 07.36.Source: vulncheck.com