ManageIQ / ManageIQ/more_core_extensions

CVE-2026-54696 (Low) detected in json-2.19.4.gem

Open Beginner friendly
#161 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Mend: dependency security vulnerability
Dominant language
Ruby
Stars
5
Forks
21
PR merge metrics
No merged PRs in 30d

Description

## CVE-2026-54696 - Low Severity Vulnerability
Vulnerable Library - json-2.19.4.gem

This is a JSON implementation as a Ruby extension in C.


Library home page: https://rubygems.org/gems/json-2.19.4.gem


Path to dependency file: /Gemfile.lock


Path to vulnerable library: /vendor/cache/json-2.19.4.gem


Dependency Hierarchy:
- manageiq-style-1.6.1.gem (Root Library)
- rubocop-1.86.1.gem
- :x: **json-2.19.4.gem** (Vulnerable Library)

Found in base branch: master



Vulnerability Details



Ruby JSON is a JSON implementation for Ruby. Versions 2.9.0 through 2.19.8 are vulnerable to heap buffer overflow when the JSON generator is provided with an oversized streamed object. When streaming to an IO JSON.dump(obj, io) and JSON::State#generate(obj, io) can write past the internal JSON generator buffer when a streamed object contains an
attacker-controlled string near 16 KB. Exploitation would result in a reliable process crash/denial of service. This issue has been fixed in version 2.19.9.

Publish Date: 2026-06-30

URL: CVE-2026-54696



CVSS 3 Score Details (3.7)

Base Score Metrics:
- Exploitability Metrics:
- Attack Vector: Network
- Attack Complexity: High
- Privileges Required: None
- User Interaction: None
- Scope: Unchanged
- Impact Metrics:
- Confidentiality Impact: None
- Integrity Impact: None
- Availability Impact: Low


For more information on CVSS3 Scores, click here.


Suggested Fix

Type: Upgrade version


Origin: https://github.com/ruby/json/security/advisories/GHSA-x2f5-4prf-w687


Release Date: 2026-06-30


Fix Resolution: json - 2.19.9

***
Step up your Open Source Security Game with Mend [here](https://www.whitesourcesoftware.com/full_solution_bolt_github)

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with Gemfile.lock and the cached gem at vendor/cache/json-2.19.4.gem; trace the transitive dependency through rubocop. Update json to 2.19.9 or later, refresh the lockfile and vendor cache, then verify that the vulnerable 2.19.4 version is no longer present.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
security
Issue type
Bug
Difficulty
2/5
Estimated time
1-3 hours
Activity status
Quiet
Clarity
Clearly specified
Newbie friendliness
78/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.