CVE-2026-71847: Ruby JSON: JSON::ResumableParser#partial_value dereferences a freed input buffer and crashes on truncated duplicate-key streams
Summary Ruby's JSON native C extension clears the consumed JSON::ResumableParser input buffer but leaves state.start, state.cursor, and state.end pointing into released storage. When partialvalue reconstructs an incomplete object containing duplicate keys, the duplicate-key warning path calls cursorposition, which dereferences those stale pointers.
Published Aug 7, 2026
Affected packages
json
- Ecosystem
- RubyGems
- Affected
- >= 2.20.0, <= 2.21.1
- Fixed in
- 2.21.2
- Check
bundle info json
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
Summary
Ruby's JSON native C extension clears the consumed JSON::ResumableParser input buffer but leaves state.start, state.cursor, and state.end pointing into released storage.
When partial_value reconstructs an incomplete object containing duplicate keys, the duplicate-key warning path calls cursor_position, which dereferences those stale pointers. This results in a heap-use-after-free and can terminate the Ruby process.
An attacker who can supply JSON stream data to an application using JSON::ResumableParser may cause process termination when the application calls partial_value on incomplete attacker-controlled input containing duplicate object keys.
The issue was reproduced in the native C extension from the official RubyGems releases:
- JSON 2.20.0
- JSON 2.21.0
- JSON 2.21.1
The attached evidence demonstrates:
- an AddressSanitizer-confirmed heap-use-after-free;
- a native
SIGSEGVusing the official JSON 2.21.1 RubyGem; - an end-to-end loopback TCP attacker/victim reproduction;
- four differential controls;
- successful execution after applying a tested patch control.
This was originally reported privately through Ruby's HackerOne program as report #3867755. A Ruby maintainer independently confirmed reproduction of the ASan failure and requested that further coordination continue through this private advisory.
No code execution or information disclosure is claimed.
Details
The affected source is:
ext/json/ext/parser/parser.cThe vulnerable sequence in JSON 2.21.1 is:
cResumableParser_parsereaches the end of the current input buffer.- It calls
json_str_clear(parser->buffer). - It sets
parser->buffer = Qfalse. - The parser-state pointers into the released buffer are not reset.
partial_valuemakes a shallow copy of the parser state.- Reconstructing an incomplete object containing duplicate keys reaches the duplicate-key warning path.
cursor_positionwalks through the stale input pointers and reads released memory.
Relevant source locations:
- Buffer release: https://github.com/ruby/json/blob/fd61def38b9bb859fee7eec8e7d3143600e5b347/ext/json/ext/parser/parser.c#L2562-L2569
- Parser-state copy: https://github.com/ruby/json/blob/fd61def38b9bb859fee7eec8e7d3143600e5b347/ext/json/ext/parser/parser.c#L2647-L2654
- Stale-pointer read in
cursor_position: https://github.com/ruby/json/blob/fd61def38b9bb859fee7eec8e7d3143600e5b347/ext/json/ext/parser/parser.c#L590-L628
- Duplicate-key handling path: https://github.com/ruby/json/blob/fd61def38b9bb859fee7eec8e7d3143600e5b347/ext/json/ext/parser/parser.c#L1196-L1255
When input is supplied to the resumable parser, the parser state stores direct pointers into the backing Ruby string:
RSTRING_GETMEM(parser->buffer, start, len);
parser->state.start = start;
parser->state.end = start + len;
parser->state.cursor = parser->state.start + offset;After the current buffer has been consumed, cResumableParser_parse clears the string and removes the parser's reference to it:
if (eos(&parser->state)) {
json_str_clear(parser->buffer);
parser->buffer = Qfalse;
}This path does not invalidate or replace:
parser->state.start
parser->state.cursor
parser->state.endJSON::ResumableParser#partial_value subsequently makes a shallow copy of the parser structure:
JSON_ResumableParser *original_parser = cResumableParser_get(self);
JSON_ResumableParser parser = *original_parser;When the partial object contains duplicate keys, reconstruction follows this call path:
cResumableParser_partial_value_body
-> json_decode_object
-> json_on_duplicate_key
-> emit_duplicate_key_warning
-> emit_parse_warning
-> cursor_positioncursor_position then reads through pointers that may refer to released storage.
AddressSanitizer reports:
ERROR: AddressSanitizer: heap-use-after-free
cursor_position at parser.c:604
freed by cResumableParser_parse at parser.c:2567The reproducer follows the normal resumable-parser API sequence:
parser << chunk
parser.parse
parser << next_chunk
parser.parse
parser.partial_valueThe issue does not require:
- an application-defined callback;
- explicit garbage collection;
- parser reentrancy;
- custom parser options;
- an attacker-supplied Ruby object;
- manual modification of native parser state.
The release-build crash reproduced on JSON 2.20.0, 2.21.0, and 2.21.1.
This report covers the native C-extension implementation. The separate Java-platform implementation was not tested and is not claimed to be affected.
PoC
The complete evidence bundle is attached as:
ruby-json-resumable-partial-value-uaf-evidence-20260716.zipSHA-256:
07bf8d47b115e45d6145d0447ab6c1c0255e4a7e9b2fb55c3c9a0e24406134acRequirements
- Linux
- Ruby with development headers
- C compiler
make- RubyGems
Release-build, network, and differential reproduction
Extract the attachment:
unzip ruby-json-resumable-partial-value-uaf-evidence-20260716.zip
cd ruby-json-resumable-partial-value-uaf-evidence-20260716Run the official JSON 2.21.1 release-build proof, loopback network proof, and differential controls:
./run_exact_2211.shExpected primary results:
release_exit=139
network_victim_exit=139
network_result=PASS
result=PASSThe following four differential controls must also report result=PASS:
unique_key
duplicate_allowed
no_partial
complete_documentThe release-build crash stack includes:
cursor_position
emit_parse_warning
emit_duplicate_key_warning
json_decode_object
cResumableParser_partial_value_bodyAddressSanitizer reproduction
Run:
./run_asan.shExpected vulnerable result:
asan_vulnerable_exit=134
ERROR: AddressSanitizer: heap-use-after-free
cursor_position at parser.c:604
freed by cResumableParser_parse at parser.c:2567Expected patched-control result:
asan_patched_exit=0
asan_result=PASSAffected-version matrix
The release-build crash was reproduced three times for each of the following official RubyGems releases:
json 2.20.0
json 2.21.0
json 2.21.1Additional evidence is included in:
artifacts/exact-2211-e2e.txt
artifacts/asan-and-patched-control.txt
artifacts/version-matrix.txt
artifacts/source-and-release-verification.txt
source-slices.txt
prior-art.md
patch-control.diffImpact
This is a use-after-free that can result in native Ruby process termination.
An attacker must be able to supply JSON stream data to an application that:
- uses
JSON::ResumableParser; - processes attacker-controlled streaming input;
- calls
partial_valueafter parsing an incomplete document containing duplicate object keys.
In network-facing deployments meeting these conditions, an attacker can cause process termination and denial of service.
The release-build crash was reproduced consistently in the tested Linux environment. The AddressSanitizer result confirms the underlying heap-use-after-free independently of normal allocator behavior.
The demonstrated impact is:
Denial of service through native process terminationNo confidentiality impact, integrity impact, arbitrary code execution, or information disclosure is claimed.
Suggested remediation
Before clearing or releasing the resumable parser's input buffer, invalidate or replace every parser-state pointer that refers to the buffer's backing storage.
Delayed code paths such as duplicate-key warning generation must not calculate cursor positions using pointers after the corresponding buffer has been released.
The attached patch-control.diff demonstrates one tested control and is provided for validation rather than as a required final implementation.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
