ManageIQ / ManageIQ/manageiq-postgres_ha_admin
CVE-2026-54696 (Low) detected in json-2.18.0.gem
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 3
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
CVE-2026-54696 - Low Severity Vulnerability
Vulnerable Library - json-2.18.0.gem
This is a JSON implementation as a Ruby extension in C.
Library home page: https://rubygems.org/gems/json-2.18.0.gem
Path to dependency file: /Gemfile.lock
Path to vulnerable library: /vendor/cache/json-2.18.0.gem
Dependency Hierarchy:
- manageiq-style-1.5.9.gem (Root Library)
- rubocop-rails-2.29.1.gem
- rubocop-1.56.3.gem
- ❌ json-2.18.0.gem (Vulnerable Library)
- rubocop-1.56.3.gem
- rubocop-rails-2.29.1.gem
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
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
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with /Gemfile.lock and /vendor/cache/json-2.18.0.gem, then inspect the dependency chain through rubocop-rails and rubocop. Update the json dependency to 2.19.9 and verify the lockfile and cached gem resolve to that version so the reported CVE 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
- 72/100